NPSP or Nonprofit Cloud · the decision
Told your charity must leave NPSP?
Salesforce still supports it.
No, a charity on NPSP does not have to move to Nonprofit Cloud today: Salesforce says NPSP will continue to be supported and has published no end date. When you do move, its own guide treats the work as a new implementation in a new org, not an upgrade. Below: when staying is the right call, when moving pays, and what the move involves.
Reviewed 1 November 2026.
The status
Is Salesforce retiring NPSP?
Not on any date it has published. Salesforce’s managed packages page, read on 31 October 2026, says NPSP is used by thousands of organisations and will continue to be supported, and recommends Nonprofit Cloud for new customers. No Salesforce page I could find gives an end of sale or end of life date.
Pages that say NPSP is being switched off cite no Salesforce source for it. Here is what Salesforce itself has published, in order.
- 01
14 March 2023: the new Nonprofit Cloud
Salesforce announced the new product and, in the same post, said it would keep offering and supporting its existing nonprofit offerings, NPSP among them.
- 02
22 February 2024: the first migration guide
Version 1 of the NPSP migration guide, according to the document history in version 2.
- 03
2 December 2025: a new name
Nonprofit Cloud became Agentforce Nonprofit. The objects did not change, and most consultants, this site included, still call it Nonprofit Cloud.
- 04
1 June 2026: migration guide, version 2
The current guide, and the source for everything in the next section.
- 05
31 October 2026: still supported
The managed packages page says NPSP will continue to be supported and recommends Nonprofit Cloud for new customers. It gives no end of sale or end of life date.
The size of the job
Is moving from NPSP to Nonprofit Cloud an upgrade?
No. Salesforce’s migration guide says the move “more closely resembles a reimplementation than a traditional software upgrade”. It strongly recommends a new org, says the two products cannot actively coexist in one, and makes Person Accounts mandatory. Budget it as a new build with a data migration attached.
Six differences from the Agentforce Nonprofit Migration Guide, version 2 of 1 June 2026, decide most of the cost.
- 01
A new org, not a switch
The guide strongly recommends a new org and says the two products cannot actively coexist in one. Nonprofit Cloud can be provisioned into an NPSP org and left switched off, but features activated by accident before the move is complete cannot be reverted.
- 02
Every contact becomes a Person Account
The guide calls this mandatory. NPSP ties every contact to a household account by default; Nonprofit Cloud needs no household at all, and where one is wanted it is a Party Relationship Group rather than a special kind of account.
- 03
One opportunity becomes up to three objects
NPSP keeps most gifts on Opportunity, with payments as child records. In Nonprofit Cloud most past giving becomes Gift Transactions, recurring donations become Gift Commitments with schedules, and opportunities are kept only for gifts still being cultivated. The guide calls it translation, not conversion.
- 04
Funds are the easy part
General Accounting Units map one to one onto Gift Designations, and allocations onto default and transaction designations. The guide finds no design difference in this area.
- 05
Some things do not come across
Engagement Plans, Levels, the Recurring Donation Change Log and data import batches are outside the guide. Gift summary fields are not migrated either, because Nonprofit Cloud calculates its own.
- 06
Every app and automation is checked again
The guide asks for an audit of every installed app and integration for compatibility, and leaves rebuilding your own automation to you and your implementation partner.
The decision
When does staying on NPSP make sense?
When NPSP runs your fundraising, your reports are trusted and you need nothing it cannot do. Moving then buys a new data model and a rebuild, not new results. Moving pays when you need programmes and outcomes beside fundraising, want the agents Salesforce announced for Agentforce Nonprofit, or are rebuilding anyway.
| NPSP runs your fundraising and the reports are trustedNothing on Salesforce’s pages sets a date. A working system with a team that knows it is an asset, not a debt. | Stay |
| You need programmes, cases or outcomes beside fundraisingThe guide says fundraising, programme and case management and outcome management come under one licence in Nonprofit Cloud, where NPSP split them across packages. | Move pays |
| You want the new nonprofit agentsThe four agents Salesforce announced on 2 December 2025, from prospect research to donor support, are sold as an add on to Agentforce Nonprofit. | Move pays |
| Your apps or integrations are not confirmed on Nonprofit CloudPayment processors, Gift Aid tools, mailing integrations. Until each one is confirmed, the move cannot be planned. | Stay for now |
| NPSP is customised beyond what anyone can explainYou are rebuilding either way. Measure what it does first, then decide where to rebuild it. | Measure first |
| You are starting freshSalesforce recommends Nonprofit Cloud for new customers. | Nonprofit Cloud |
The destination
Five things waiting on the other side.
I have not moved an NPSP org. I built fundraising on Nonprofit Cloud for a UK charity whose money lived in spreadsheets. That build runs on the same objects and the same platform rules that any NPSP migration lands in. These five were not obvious from the documentation, and each belongs in a migration budget.
- 01
Payments arrive with no programme split
Outside Gift Entry, a payment inherits nothing from its commitment: tested on both steps, each returned zero designations. Every load and every integration needs its own writer, described in the article on the missing split.
- 02
The donor summary panel stays empty
Donor giving summaries are filled by Data Processing Engine, so the template has to be copied and the copy activated before the panel shows anything. Check which year it counts in: that org’s fiscal year ran January to December, while the charity reports April to March.
- 03
Draft promises count as this year’s money
A draft commitment with a schedule shows its full value in the native current year total. Every report on those totals has to filter on status, or the forecast includes money nobody has promised.
- 04
A programme row needs both amount and percent
A Gift Transaction Designation refuses one without the other, allows one row per payment and programme, and refuses any row once the percentages reach 100. None of the three rules is in the object reference; each was found by hitting it.
- 05
Gift Aid is not built in
A UK charity that claims Gift Aid through an NPSP app needs an equivalent on the other side. What HMRC requires and what Salesforce lacks is a separate article.
One more lesson from that build: four different API checks agreed that the donor summary template did not exist, and one look at the Setup page showed it did. On Nonprofit Cloud, look at the screen before concluding something is missing. The full build is in the charity case study, and the three packages are on the Nonprofit Cloud page.
Asked often enough to answer here
Questions
- Q
Can we add Nonprofit Cloud to our NPSP org and switch over later?
Technically yes, and Salesforce advises against it. Its migration guide calls that route high risk: Nonprofit Cloud features activated by accident before the move is complete cannot be reverted, and removing NPSP afterwards can leave parts of the package behind. It strongly recommends a new org.
- Q
Will our reports and dashboards come across?
Not as they are. They read NPSP objects such as Opportunity and Payment, which split into Gift Commitments, Gift Transactions and Opportunities in Nonprofit Cloud. The guide also leaves gift summary fields out of the mapping, because Nonprofit Cloud calculates its own donor giving summaries.
- Q
What should we do this year if we stay?
Write down what NPSP does for you that a new org would have to do again: rollups, allocations, Gift Aid, receipts and every integration. That list is the scope of any future move, and it is the same inventory the guide’s audit chapters ask for.
Migration from one system, NPSP included, with the totals reconciled to the penny before anyone uses it, is part of Fundraising complete: €8,450 for 130 hours. If you are staying on NPSP, nothing here needs buying.
Serhii Skrypnyk · Senior Salesforce Administrator · 7 Salesforce certifications · on the platform since 2018. Reviewed 1 November 2026.
Read next
The question that usually comes after this one.
- 01
Is Salesforce Free for Nonprofits in 2026?
Power of Us gives eligible charities 10 Nonprofit Cloud Core licences free. What they cover, what Agentforce Nonprofit costs, and what a charity still pays for.
- 02
Nonprofit Cloud Migration From Spreadsheets
Move a charity’s donations from spreadsheets into Nonprofit Cloud and prove three totals match your own workbook to the penny before anyone trusts a dashboard.
- 03
Case: Community charity, United Kingdom
Three colour coded spreadsheets became one fundraising system, with every payment split across programmes and committee scoring inside Salesforce.