Somewhere in your inbox there is probably an email telling your nonprofit that Salesforce is shutting down the Nonprofit Success Pack and you need to migrate before a deadline. That deadline does not exist. Salesforce has not published an end-of-life date for NPSP, has not announced an end of sale for organizations already running it, and continues to support it. What did change is quieter and, for budgeting purposes, more important: NPSP stopped receiving new features when Nonprofit Cloud launched in March 2023, and in December 2025 the Power of Us program stopped handing new applicants ten free NPSP licenses by default. Your platform is frozen, not retired — and those are two very different problems with two very different price tags. This is the decision framework we walk nonprofit clients through when they ask us whether to move, stay, or leave Salesforce entirely.
Key Takeaways
- There is no announced NPSP deadline. Any vendor selling you an urgent migration against a date is selling you a date they invented. NPSP remains supported with no published end-of-life or end-of-sale.
- Innovation has stopped, though. Salesforce launched Nonprofit Cloud in March 2023 and has shipped new nonprofit capability there since — AI agents, Data Cloud connectivity, modern automation. None of it lands in NPSP.
- December 2025 was the real signal. Power of Us now issues new applicants ten Agentforce Nonprofit licenses (or ten Sales and Service Cloud Enterprise licenses) instead of ten free NPSP licenses. NPSP is a set of managed packages, not a license type, so it can still be installed manually — it just isn’t the default path anymore.
- This is a re-implementation, not an upgrade. NPSP tracks gifts as Opportunities against Household Accounts. Nonprofit Cloud uses Person Accounts, Party Relationship Groups, and dedicated GiftCommitment and GiftTransaction objects (API v59.0+). Nothing maps one-to-one.
- Price the license change, not just the project. Published Nonprofit Cloud editions run $70, $125, and $285 per user per month billed annually, with ten donated Power of Us licenses on top. Many NPSP orgs were sitting on donated Sales Cloud licenses and have never modeled a per-seat line item.
- Staying is a legitimate strategy — if it’s a decision. The failure mode isn’t choosing NPSP. It’s drifting on NPSP for three more years with no plan and no budget line.
What Actually Changed — and What Didn’t
Four verifiable things have happened, and they get conflated constantly in the consulting market.
March 2023: Salesforce launched Nonprofit Cloud, a native industry-cloud product built on standard platform objects. From that point forward, NPSP — a suite of managed packages installed on top of Sales or Service Cloud — received no new features. Cloud for Good, a long-time Salesforce nonprofit partner, dates the formal “end of innovation” announcement for NPSP to 2024.
October 2025: Nonprofit Cloud was renamed Agentforce Nonprofit. Expect to see both names in the wild for a while — Salesforce’s own nonprofit pricing page still lists editions as “Nonprofit Cloud,” while the newsroom and partner material use “Agentforce Nonprofit,” and “Agentforce 360 for Nonprofits” appears as umbrella branding. Same product underneath.
December 2, 2025: Salesforce announced Agentforce Nonprofit with four purpose-built agents: Prospect Research and Participant Management generally available at announcement, Volunteer Capacity & Coverage in beta with GA targeted for early 2026, and Donor Support slated for beta in spring and GA in summer. Pacific Clinics CEO Kathy McCarthy is quoted saying agents “empower our team to spend more time listening, connecting, and providing personal support.”
December 2025: The Power of Us program swapped its default offer. The “10 free NPSP licenses” option was removed; eligible nonprofits now receive ten donated Agentforce Nonprofit licenses, or ten Sales and Service Cloud Enterprise Edition licenses.
What has not happened: no end-of-life date, no end-of-sale, no forced cutover. If you are running NPSP today, your licenses remain valid and your org remains supported.
Why “Migration” Is the Wrong Word
The single most expensive misunderstanding in this space is treating the move as a version upgrade. It isn’t. The two products do not share a data model, which means there is no push-button path and no tool that simply “converts” your org.
| Concept | NPSP | Nonprofit Cloud / Agentforce Nonprofit |
|---|---|---|
| Constituent record | Contact with Household Account | Person Account |
| Household / group modeling | Household Accounts, Affiliations | Party Relationship Groups and relationships |
| Donation record | Opportunity (plus Recurring Donation) | GiftTransaction (completed payment) |
| Pledge / recurring commitment | Recurring Donation, Opportunity schedules | GiftCommitment with GiftCommitmentSchedule |
| Restrictions / allocations | GAU Allocations | Gift Designation objects |
| Build layer | Managed packages on Sales/Service Cloud | Native standard objects on core platform |
| Automation | Flow, legacy Process Builder, package logic | Flow, Business Rules Engine, OmniStudio |
Salesforce’s own developer documentation makes the separation concrete: GiftTransaction represents a completed transaction from a gift, is available in API version 59.0 and later, and surfaces only when the Fundraising Access license is enabled and the Fundraising User permission is assigned. Around it sits a family of objects — GiftCommitment, GiftCommitmentSchedule, Gift Designation, Gift Soft Credit, Gift Refund, GiftTribute, GiftAgreement, GiftStewardship, Donor Gift Summary. A single NPSP Opportunity row can legitimately become three or four records on the other side.
That is why the pattern we see fail most often is the lift-and-shift: someone exports Opportunities, imports them as Opportunities into the new org because the object still exists, and quietly abandons the entire fundraising data model they are paying for. Soft credits, pledge schedules, and designation reporting are usually where it surfaces — about four months after go-live, during the first year-end appeal.
Salesforce publishes a Nonprofit Cloud Migration Guide alongside Implementation and Fundraising guides, and is explicit that they are “intended for experienced Salesforce admins and consultants.” Partner tooling exists to compress the work — Cloud for Good’s Stratus for org-to-org data and metadata migration, and Conemis transition cloud, which pre-packages NPSP-to-Agentforce-Nonprofit transformation logic. Useful, but they accelerate a re-implementation; they don’t replace one.
The Cost Drivers That Don’t Show Up in the Proposal
Most migration quotes cover configuration and data. The surprises live elsewhere.
- Per-seat license math. Published Nonprofit Cloud editions: Sales & Service Core at $70, Advanced at $125, and Sales Max / Service Max at $285 per user per month, billed annually, with ten donated Power of Us licenses and discounts on additional seats. A 30-person org that has quietly run on donated and discounted Sales Cloud seats for eight years needs to model the eleventh seat onward before approving anything.
- The integration perimeter. Payment processing, online donation forms, event platforms, email, accounting sync, wealth screening. Every one of these connects to NPSP objects. Most will need reconfiguration or a new connector version, and a few vendors support one platform better than the other.
- Reports, dashboards, and the board packet. Multi-year giving comparisons, LYBUNT/SYBUNT lists, and restricted-fund reporting all get rebuilt against a different schema. Budget for this explicitly; it is the deliverable your executive director actually judges the project on.
- Parallel running and the year-end calendar. No nonprofit should cut over in November or December. That constraint alone can push a project two quarters.
- Retraining. Gift entry screens look different. Development staff who have entered Opportunities for a decade will enter Gift Transactions instead.
Done well, the upside is real. Salesforce Ben cites an international nonprofit that completed a six-month transition and came out with a 40% reduction in household duplication and fifteen automations consolidated into four reusable flows. Note that those are data-quality and process wins — they come from redesigning, not from copying.
A Four-Question Decision Framework
- Is a frozen platform actually blocking you right now? Not theoretically — name the capability. “We need AI-assisted prospect research,” “we need volunteer shift matching,” “we need Data Cloud for a unified constituent profile.” If you cannot name one, your 2026 priority is probably data hygiene, not a platform project.
- How heavily customized is your NPSP org? Count custom objects, Apex triggers, managed packages, and integrations. A lightly customized org with clean data is a three-to-five-month project. An org with 40 custom objects and a decade of accreted Apex is a re-implementation with a discovery phase, and pretending otherwise is how these projects blow up.
- Can you fund the license delta for three years, not one? Build a three-year total cost model that includes seats beyond the donated ten, integration rebuilds, and the consulting line. If year two breaks the budget, you need a phased plan or a different platform.
- Do you have an internal owner? Not a committee — one person with authority to make data-model decisions. Migrations stall on unanswered questions about soft credits and household rules far more often than on technology.
If You Decide to Stay on NPSP
Staying is defensible. Drifting is not. Four things to do anyway:
- Write down the decision and a review date. One page, board-visible, revisited annually. “We evaluated in 2026 and chose to remain on NPSP through FY2028” is governance. Silence is risk.
- Fix the data now. Deduplicate households, normalize campaign and designation structures, and retire dead fields. Every hour here is an hour you don’t pay for twice during a future migration.
- Stop deepening the customization. Build new requirements with Flow and standard features rather than new Apex layered on package objects. Treat the org as something you will eventually leave.
- Verify your backup and recovery position independently. “Supported” is not “recoverable.” Know who restores your donor history if someone runs a bad data load.
The Question Nobody at Salesforce Will Ask You
If you are re-implementing anyway, the honest question is whether you are re-implementing on the right platform. A frozen NPSP org is the one moment you have real leverage to evaluate the market without sunk-cost bias.
For small shops where the Salesforce admin burden never got absorbed, Zoho is worth a look: Zoho for Nonprofits issues eligible organizations $5,000 in wallet credits valid for five years, with Zoho covering half the cost of each purchase. Direct applications are accepted from the US, Canada, the UK, Australia, New Zealand, and India, with other regions routed through TechSoup validation, and verification runs seven to ten business days. Read the exclusions — Zoho Voice, Zoho Sign API, Zoho Domains, ManageEngine products, premium support, and marketplace extensions are not covered.
That said: if you have fifteen staff in Salesforce, an integrated events platform, and three years of institutional knowledge in your org, leaving the ecosystem to avoid a re-implementation usually just buys you a different re-implementation with less experienced help. Evaluate honestly, then commit.
CRM Experts Online’s Perspective
We implement and repair CRM systems across Salesforce, HubSpot, Zoho, NetSuite, SugarCRM, and SuiteCRM, and the nonprofit NPSP situation is a textbook case of a pattern we see in every vertical: a vendor stops investing in a product without retiring it, the market fills the silence with a fake deadline, and buyers make a six-figure decision under manufactured urgency.
Our position with nonprofit clients is straightforward. First, we refuse to sell urgency that Salesforce hasn’t declared — if your NPSP org is clean, your reporting works, and nothing on your roadmap requires the new fundraising model or agents, your 2026 budget is better spent on data quality and adoption than on a platform swap. Second, when the move is justified, we scope it as a re-implementation from the first conversation, because a proposal priced as a data migration is a proposal that will be re-priced in month three. Third, we insist on mapping the fundraising model before anyone touches a sandbox: how pledges, soft credits, designations, and recurring gifts will live across GiftCommitment and GiftTransaction, written down and signed off by the development director — not the admin. That document is the project. Everything else is execution.
And we treat the integration perimeter as a first-class workstream, not a punch-list item. The donation form, the payment processor, and the accounting sync are what the organization actually runs on. A beautiful new org that can’t take a gift on Giving Tuesday is a failed project regardless of how clean the data model is.
FAQ
Is Salesforce shutting down NPSP? No. Salesforce has not announced an end-of-life or end-of-sale date for NPSP, and it remains supported for organizations already using it. It has not received new features since Nonprofit Cloud launched in March 2023.
Can a new nonprofit still get NPSP? Not as the default. Since December 2025, Power of Us issues ten Agentforce Nonprofit licenses or ten Sales and Service Cloud Enterprise licenses instead of ten free NPSP licenses. Because NPSP is a set of managed packages rather than a license type, it can still be installed on Sales Cloud licenses — but you would be starting new on a product that receives no new features.
What is Agentforce Nonprofit versus Nonprofit Cloud? The same product. Nonprofit Cloud was renamed Agentforce Nonprofit in October 2025, and you will still see “Nonprofit Cloud” on Salesforce’s pricing and documentation pages.
How long does an NPSP migration take? For a lightly customized org with clean data, plan three to five months. Heavily customized orgs with significant Apex, many integrations, or messy household data run six months or more. Salesforce Ben cites a six-month international nonprofit transition as a representative example.
Will we keep our full donation history? Yes, if the project is scoped properly — but history is transformed, not copied. Opportunities become Gift Transactions and Gift Commitments, and the mapping rules for soft credits, pledges, and designations are decisions you make, not defaults you inherit.
What does it cost per user after the donated licenses? Salesforce’s published nonprofit editions are $70 (Sales & Service Core), $125 (Advanced), and $285 (Sales Max or Service Max) per user per month billed annually, with discounts on licenses beyond the donated ten. Confirm your actual quote — nonprofit discounting varies.
Are the nonprofit AI agents available now? Partly. As of the December 2, 2025 announcement, Prospect Research and Participant Management were generally available; Volunteer Capacity & Coverage was in beta with GA targeted for early 2026, and Donor Support was scheduled for beta in spring and GA in summer. Verify current status before budgeting against any one agent.
Can we run NPSP and Nonprofit Cloud side by side? Not sensibly in the same org — the data models conflict. Migrations are typically org-to-org, which is exactly why tooling like Cloud for Good’s Stratus and Conemis transition cloud exists.
What’s the worst mistake nonprofits make here? Importing gift history as Opportunities in the new org because the object still exists. It looks like a successful migration for about four months, then fails at year-end reporting.
Conclusion
Salesforce hasn’t set an NPSP deadline, but it has made its roadmap unmistakable: every new nonprofit capability — the fundraising data model, Data Cloud connectivity, the agents announced in December 2025 — is being built on Agentforce Nonprofit. The right response isn’t panic and it isn’t paralysis. It’s a written decision with a review date, a three-year cost model, and a fundraising data model mapped before anyone opens a sandbox.
If you’re running NPSP and want an honest read on whether to move, stay, or re-evaluate the platform entirely, schedule a consultation with CRM Experts Online. We’ll assess your org’s customization depth, integration perimeter, and data quality, and give you a scoped answer — including the answer “stay put and fix your data,” when that’s the right one.
Further Reading
- Salesforce Introduces Agentforce Nonprofit with New AI Agents (December 2, 2025)
- Salesforce Help: Nonprofit Cloud Migration and Implementation Guides
- Salesforce Developer Docs: GiftTransaction object reference
- Salesforce Nonprofit Cloud pricing and editions
- Cloud for Good: Evolving the Power of Us — From NPSP to Agentforce Nonprofit
- Salesforce Ben: The State of Salesforce Nonprofit Offerings in 2026
- Salesforce Ben: NPSP to Nonprofit Cloud Migration
- Zoho for Nonprofits program details

CRM & ERP Enterprise Technology Expert and Entrepreneurial Executive with 20+ years of leading CRM, ERP, Customer Experience, and Block-chain initiatives and projects across internal and customer facing technologies. Proven success in closing large deals in Pre Sales customer facing engagements and deploying enterprise wide CRM & Customer Experience solutions internationally and domestically.