Still running NPSP on Sales Cloud? You are in very good company.
Thousands of nonprofits built their Salesforce on it, and for many of them it still does the job.
But here is the question worth asking this year. If you were choosing your Salesforce setup today, would you choose the same one?
The NPSP vs Nonprofit Cloud decision is not about chasing the newest product. It is about whether the setup you designed years ago still fits how your organisation raises money, runs programs and reports to funders. Salesforce for nonprofits has changed a lot since most NPSP orgs went live, and the gap between “it still works” and “it still fits” gets wider every year. The same is true for Salesforce for charities in the UK.
This guide gives you the full picture we could not fit into a LinkedIn post. You will see what actually differs between the two products, the five questions to answer before any migration, and an honest view of when staying on NPSP is the smarter call.
What is the difference between NPSP and Nonprofit Cloud?
NPSP, the Nonprofit Success Pack, is a set of managed packages installed on top of Sales Cloud that adds donations, households, recurring giving and relationships to a standard CRM. Nonprofit Cloud is Salesforce's newer product for nonprofits, built directly into the core platform with its own native data model for fundraising, programs and outcomes. Salesforce now markets it as Agentforce Nonprofit, with AI agents built in, and you will see both names in Salesforce materials.
The difference sounds technical, but it shapes everything else. NPSP adapts a sales tool for nonprofit work, so many nonprofit concepts live in custom objects, package settings and fields that were added over time. Nonprofit Cloud starts from nonprofit concepts. Gifts, commitments, designations, programs, beneficiaries and outcomes are part of the platform itself, and new features from Salesforce arrive there first.
Salesforce continues to support NPSP, so nobody is being forced to move tomorrow. At TrueSolv we see the choice as a strategic one. It is about where your organisation wants to be in five years, and not about an urgent technical deadline.
| Area | NPSP on Sales Cloud | Nonprofit Cloud |
|---|---|---|
| Foundation | Managed packages on Sales Cloud | Native to the Salesforce core platform |
| Constituent model | Household Accounts with Contacts | Person Accounts with household groups |
| Fundraising | Opportunities used as donations | Native gift transactions, commitments and designations |
| Programs and outcomes | Separate package or custom build | Built in program, case and outcome management |
| Product roadmap | Mature and stable feature set | Where new nonprofit and AI features arrive |
| Best fit | Standard fundraising that already works well | Fundraising plus programs, outcomes and plans for AI |
Why “it still works” is not the same as “it still fits”
Most NPSP orgs did not become complicated overnight. They grew one request at a time.
A new grant needed a new field. A program team needed a tracker, so someone built a custom object. Finance wanted gift aid or receipting handled differently, so a flow appeared, then a second one to fix the first. Years later the org still runs, but only two people really understand why, and one of them is a consultant who left in 2022.
None of this is a failure. It is what happens to every CRM that serves a growing organisation. The risk is that the cost of those workarounds is invisible, because it is paid in staff hours, slow reports and nervous moments before every Salesforce release, not in a single invoice.
That is why we suggest starting with questions, not with a migration plan.
Five questions to answer before you migrate
1. What are you paying for today?
Start with the licenses you actually use. Many NPSP organisations pay for Sales Cloud users who log in once a month, keep add on products nobody opened this year or run separate tools for things Salesforce could already do.
List every paid line connected to your CRM. That means licenses, add ons, integration tools, the email platform, the forms tool and support contracts. Then put the internal time spent keeping it all running next to it. That number, not the license price alone, is the real cost of your current setup, and it is the baseline any move has to beat.
2. Which customizations and workarounds are you maintaining?
Open Setup and count the custom objects, flows, Apex classes and installed packages. Then ask a harder question about each one. Does it exist because the business needed something unique, or because NPSP did not have a native answer when it was built?
The second group is where Nonprofit Cloud can simplify things the most. Program tracking, case management and structured gift commitments are typical examples. The first group, your truly unique processes, will need to be rebuilt in any new setup, and that is where most of the migration effort sits.
3. What would actually improve with Nonprofit Cloud?
Be specific and be honest. “It is newer” is not an improvement. “Our program team could stop using a spreadsheet next to Salesforce” is.
Good reasons we hear from nonprofits include a single view of donors, volunteers and beneficiaries, outcome reporting that funders keep asking for, fewer custom objects to maintain, and access to the AI and automation features Salesforce is building on the new platform. If you cannot name at least two concrete improvements for real teams, that is already an answer.
4. What would migration cost in money, data and disruption?
Moving from NPSP to Nonprofit Cloud is not an upgrade button. In most cases it means a new implementation and a full data migration, because the two products use different data models.
The money is only one part. Your data has to be mapped from households and opportunities into the new model, cleaned and tested, and every integration has to be reconnected. Your team needs training, reports and dashboards need to be rebuilt, and there will be a period where people need extra support. Plan for a busy quarter, not a busy weekend, and avoid your peak fundraising season.
A trustworthy estimate covers all of it. That means discovery, data migration, rebuilding the processes that really matter, integrations, testing, training and a few weeks of support after go live. If a quote only mentions configuration, ask what is missing.
For the license side of the budget, see our guide to Salesforce Nonprofit Cloud pricing.
5. Would switching genuinely leave you better off?
Put the answers side by side. On one side is the yearly cost of your current setup, including workarounds and staff time. On the other is the one time cost of migration plus the yearly cost of running Nonprofit Cloud, minus the time and tools it saves.
If the second side wins within two or three years and real teams get real improvements, moving is worth serious planning. If the numbers are close, a cleanup of your current NPSP org may give you most of the benefit for a fraction of the effort. ️
Stay on NPSP or move to Nonprofit Cloud?
Staying is often the smart decision, and we say so when we see it. A move, on the other hand, deserves serious planning when the signs on the right apply.
Stay on NPSP
Then invest in a health check and a cleanup
- Your org is relatively clean and the team is happy with it
- Your processes are standard fundraising without complex programs or outcome tracking
- You have a major campaign, audit or leadership change coming in the next six months
- The budget for a proper migration is not there yet
Plan a move
Then start with an assessment, not a quote
- Program, case or outcome data lives outside Salesforce in spreadsheets or other tools
- The org has so many customizations that every change feels risky
- Funders ask for impact reporting you struggle to produce
- You want to use the new AI and automation features Salesforce is building for nonprofits
- You are already planning a big change, such as a merger, a new CRM owner or a new fundraising model
If you stay, a Salesforce health check and a cleanup of unused fields, flows and reports will make NPSP faster and safer for years. If you move, see what a well planned nonprofit build delivers in how a UK charity cut its funder reports from three days to an afternoon.
What a good NPSP to Nonprofit Cloud migration looks like
- Assessment. Map what you have, what you pay for and what the business really needs.
- Design. Decide how households, gifts, programs and outcomes will look in the new model, and what you will leave behind.
- Build and integrate. Configure Nonprofit Cloud, rebuild the processes that matter and reconnect integrations.
- Data migration and testing. Clean, migrate and test the data in several rounds, with real users checking real records.
- Go live and support. Train the team, launch outside peak season and keep support close for the first weeks.
The assessment is the part most organisations skip, and it is the part that decides whether the rest goes smoothly.
Frequently asked questions
Is Salesforce retiring NPSP?
Salesforce continues to support NPSP and has not announced an end date. New features for nonprofits are focused on Nonprofit Cloud, so the gap between the two products will keep growing over time.
Can I upgrade from NPSP to Nonprofit Cloud in place?
No. The two products use different data models, so moving usually means a new implementation and a data migration rather than an upgrade inside the same setup.
How long does an NPSP to Nonprofit Cloud migration take?
It depends on data volume, customizations and integrations. Small organisations with clean data can move in a few months, and larger ones with many programs and integrations should plan for longer.
Do the donated Power of Us licenses apply to Nonprofit Cloud?
Yes. Eligible nonprofits in the US and UK receive 10 donated Enterprise Edition licenses through the Power of Us program and can choose the Agentforce Nonprofit bundle. New Power of Us orgs no longer start on NPSP. Check the current terms for your country on the Salesforce nonprofit site before you plan your budget.
The right question is not “when do we migrate”
The best NPSP to Nonprofit Cloud decisions we have seen started with an honest look at the current org, not with a migration quote. Sometimes the answer was a full move. Sometimes it was a cleanup and a plan to revisit the question in a year. Both were the right answer for that organisation.
If you are running NPSP today and are not sure which way to go, we will help you compare your current setup with Nonprofit Cloud before you spend anything on a migration. There is no “you need to migrate” pitch, just a practical look at what you have, what you pay for and what would actually change.
Book a free NPSP vs Nonprofit Cloud review
Pick a time that suits you and we will walk through your org together.
Follow TrueSolv on LinkedIn for more practical guides for nonprofits on Salesforce.
