If you've spent any time this year trying to pin down the difference between Salesforce Nonprofit Cloud and NPSP, you've probably hit two articles that flatly contradict each other. One says NPSP is being discontinued. The next says it isn't. One calls Nonprofit Cloud an upgrade. Another says migration is a full rebuild. One tells you every nonprofit needs to move. Another says most don't.
The confusion is fair. Salesforce changed both the products and their names inside the nonprofit corner of the Salesforce ecosystem over the past two years, and most of what's published hasn't caught up. Two changes matter most. In October 2025, Salesforce renamed Nonprofit Cloud to Agentforce Nonprofit. In December 2025, NPSP stopped being a preconfigured option in new production orgs, so nonprofits setting up the Salesforce platform for the first time now start on Nonprofit Cloud instead of NPSP. NPSP itself is still fully supported and still available to existing users. It has not been discontinued, and Salesforce has announced no retirement date.
This article gives you a current, honest comparison of NPSP and Nonprofit Cloud: what each is, how their data models differ, what each does well, and who each one fits in 2026. It ends with a framework you can use to decide. We're MagicFuse, an official Salesforce partner that has implemented both platforms for nonprofit organizations, so what follows comes from delivery experience, not just documentation.
Key Takeaways
- Nonprofit Cloud (NPC) was renamed Agentforce Nonprofit in October 2025. NPSP keeps its name. Both appear in Salesforce documentation.
- NPSP is a suite of managed packages installed on top of Sales Cloud. Nonprofit Cloud is a native industry cloud built into Salesforce's core platform. That architectural gap is the real difference.
- The data models are incompatible. NPSP uses Household Accounts and tracks gifts on the Opportunity object. Nonprofit Cloud uses Person Accounts, models groups through Party Relationship Groups, and tracks gifts with dedicated Gift Commitment and Gift Transaction objects.
- NPSP has been feature-frozen since March 2023 and is no longer preconfigured for new orgs as of December 2025. It remains fully supported, with no retirement announced.
- Moving from NPSP to Nonprofit Cloud is a re-implementation, not an upgrade. Because Person Accounts and NPSP can't coexist in one org, migration often means a new org.
- The right choice depends on your organization's goals. A first-time setup, connected program and case work, AI plans, and constituent portals point toward NPC. A stable NPSP org with straightforward fundraising often has no reason to move.
What Are Salesforce Nonprofit Cloud and NPSP?
Both are Salesforce solutions for nonprofits, and both run on the same underlying Salesforce platform. Beyond that, they're built in fundamentally different ways. Understanding what each one actually is makes every later comparison easier to read.
What is NPSP (Nonprofit Success Pack)?
The Nonprofit Success Pack is a suite of six managed packages that install on top of standard Sales Cloud licenses. It started life as the Nonprofit Starter Pack, was later renamed the Salesforce Nonprofit Success Pack, and was shaped over many years by a community of 47,000+ nonprofits. There is no such thing as an "NPSP license." You install the packages from the AppExchange, for free, onto Salesforce licenses you already pay for, then configure them.
Under the hood, NPSP uses a Household Account data model: individual people are Contacts linked to Household Account records that group family members together. Donations run through the Opportunity object, with six record types covering donations, grants, major gifts, in-kind gifts, matching gifts, and memberships. It's proven, well-documented, and surrounded by a deep set of third-party applications built specifically for it.
Two facts define NPSP's status in 2026. It stopped receiving new features in March 2023, so it's stable but frozen. And since December 2025 it's no longer preconfigured in new production orgs. Existing users keep full support, and because NPSP is open source, orgs could keep installing it even in the unlikely event Salesforce ever stepped back.
What is Salesforce Nonprofit Cloud (Agentforce Nonprofit)?
Salesforce Nonprofit Cloud (often shortened to Salesforce NPC), renamed Agentforce Nonprofit in October 2025, is a native industry cloud. It wasn't layered on top of the platform as a package. It was built into Salesforce's core platform using the Salesforce Industries model, the same foundation behind Financial Services Cloud, Health Cloud, and Education Cloud (the industry clouds used by banks, health systems, and educational institutions). That shared foundation lets nonprofit customers reuse components proven at scale in other Salesforce industry clouds.
Nonprofit Cloud tracks people as Person Accounts rather than Contacts under Household Accounts, and its capabilities ship as native modules: Fundraising, Programs, Case Management, and Outcome Management, plus Grantmaking as a separate product. These nonprofit-specific features are part of the platform, not an add-on, which is what makes NPC a more comprehensive solution for organizations that need program delivery and fundraising in one place.
How Do NPSP and Nonprofit Cloud Differ in Architecture and Data Model?
The architecture and data model are where the key differences between the two platforms actually live, and they're the single most important thing to understand. This is what makes migration a re-implementation rather than an upgrade. Most comparison articles skim over it. Get it right and the rest follows.
Why the data model is the key difference
Here is where the two platforms genuinely diverge. NPSP groups people through Household Accounts and records every gift as an Opportunity. Nonprofit Cloud tracks each person as a Person Account, models family and group ties through Party Relationship Groups (the same relationship construct Financial Services Cloud uses for households), and splits gifts across dedicated objects.
The two approaches can't share an org. Person Accounts and NPSP are mutually exclusive: you can't enable Person Accounts where NPSP is installed, and you can't install NPSP where Person Accounts are already on. That single constraint shapes every migration decision later in this article.
What Nonprofit Cloud's native tools add
Because NPC is built on the Salesforce Industries model, it brings a set of advanced tools that were never available in NPSP. OmniStudio powers guided intake flows and dynamic assessments with clicks instead of code. The Data Processing Engine handles complex rollups and background calculations. The Business Rules Engine automates decisions such as eligibility using expression sets and decision tables. The Actionable Relationship Center gives a single 360-degree view of how a constituent's relationships, gifts, and program history connect, across donors and beneficiaries alike.
On top of that sits Data Cloud and Agentforce, which bring advanced analytics, data insights, and AI agents to the nonprofit data model. None of this exists in NPSP, and it's the clearest example of why Nonprofit Cloud offers a more customizable solution with room for advanced features and customizable workflows as an organization grows.
What Can Each Platform Do for Fundraising, Programs, and Donors?
Architecture aside, here's the practical view a fundraising or operations lead actually needs. This is what the Salesforce NPSP features cover, what the Salesforce Nonprofit Cloud features add, and where each one has real limits.
How does each platform handle donor management and fundraising?
Both platforms give you real fundraising tools. For everyday donor management, NPSP does the core work well: recurring donations, soft credits, tribute gifts, and campaign reporting all run on the Opportunity model, and Household rollups keep visible at the family level. It's a solid base for managing donations and steady donor relationships.
Nonprofit Cloud's fundraising model is more granular. Gift Commitments track what a donor has pledged, Gift Transactions record what actually arrived, and Outreach Source Codes tie gifts back to specific outreach efforts for cleaner campaign management and donation tracking. Actionable Lists help fundraisers work a major-gift portfolio, and pairing NPC with Marketing Cloud adds the marketing tools for segmented donor engagement at scale. The extra precision is real. Whether it changes how your team works is the question that decides if it's worth the added complexity.
How does each platform handle programs, cases, and outcomes?
This is where the gap widens. In NPSP, program work lives in the Program Management Module and case work in a separate case management package. Both function, but they sit next to your fundraising data rather than inside one connected system.
Nonprofit Cloud brings Programs, Case Management, and Outcome Management together natively. You can enroll a participant, deliver a benefit, track a case, and report indicator results against program goals without stitching packages together. For organizations running complex programs that have to connect service delivery to funder outcome reporting, that native integration is the strongest single argument for NPC.
What about portals, volunteers, and integrations?
If a constituent-facing portal is on your roadmap, Nonprofit Cloud's native Experience Cloud compatibility lets donor, volunteer, and partner portals expose NPC objects directly, with proper sharing and access control. NPSP can do portals too, but it needs configuration workarounds to get there.
Neither platform processes payments on its own, so both rely on third-party systems such as Stripe, GoCardless, or Classy. Dedicated volunteer management also usually involves additional tooling or a portal on either platform. If that's central to your work, see our guide to Salesforce volunteer management for how nonprofits handle it in practice.
When Is NPSP Still the Right Choice?
Most comparisons push you toward Nonprofit Cloud. That isn't always the right advice. Here are five situations where staying on NPSP is the sound call, and where the best practice is to get more from the org you already have.
- Your NPSP org works and your team uses it. If your implementation is stable, your data is clean, staff rely on it, and your funder reporting holds up, migration is a large disruption for unclear gain. NPSP is fully supported and will keep running. The cost of moving has to outweigh what NPC adds, and for many nonprofit customers today it doesn't.
- Your fundraising needs are straightforward. If your core work is donor management, recurring gifts, grant tracking, and campaign reporting, NPSP handles all of it. Nonprofit Cloud's gift model is more precise, but also more complex. Added precision that doesn't change how your team works won't justify a re-implementation.
- Your budget isn't ready for a re-implementation. Moving from NPSP to NPC is a full data-model remap, automation rebuild, and integration reconnect. It is not a small project. If budget and internal capacity aren't there, staying put and optimizing what you have is the more responsible path.
- Your partner knows NPSP but hasn't delivered NPC. Nonprofit Cloud needs specific technical expertise. A partner who knows NPSP well but claims NPC capability without a real track record is a risk. Maintaining and improving your existing platform with them is lower risk than a first-time migration.
- You're a small organization with limited technical capacity. NPC's complexity (Person Accounts, native architecture, OmniStudio, several integrated modules) is genuinely harder to run than NPSP's basic functionality. A small team with one part-time admin is better served by a well-configured NPSP org they can manage than a half-finished NPC org they can't.
When Does Moving to a Nonprofit Cloud Make Sense?
The other side is just as real. Here are five situations where Nonprofit Cloud earns the move.
- You're implementing Salesforce for the first time in 2026. Eligible nonprofits receive Agentforce Nonprofit licenses through the Power of Us program, not NPSP. Starting on NPC means starting on the data model that will receive every future feature. Starting on NPSP now means starting on a feature-frozen platform. For a first-time Salesforce setup, NPC is the right starting point unless you have a specific reason to choose otherwise.
- You run complex programs alongside fundraising and need them connected. If you deliver programs, track beneficiaries, manage case files, and have to connect program delivery to funder outcome reporting, NPC's integrated architecture does this far better than NPSP plus PMM ever could.
- You want AI and advanced analytics tied to your nonprofit data. Salesforce's nonprofit AI (Agentforce agents, Data Cloud, and Einstein features) is built on NPC's native data model. NPSP's managed-package architecture can't support these the same way. If you want AI-driven donor insights, automated case routing, or predictive program analytics, you need to be on NPC.
- You need a donor or volunteer portal wired properly into your CRM. NPC's native Experience Cloud compatibility means portals can expose NPC objects directly, with the access control and advanced security features external-facing data demands. NPSP needs workarounds for the same result.
- Your NPSP org has years of technical debt. If you're carrying duplicate records, fragmented integrations, and customizations that break when touched, migration is a chance to rebuild on clean architecture with expanded functionality. The project is expensive, but it also forces a data cleanup, an access-model redesign, and an integration audit. Where the cost of maintaining a broken org keeps climbing, migration can be the lower-cost path over the long run.
How Should You Decide Between Nonprofit Cloud and NPSP?
If you've read the two sections above, you already have the context. Answer these four questions honestly and the choice usually becomes clear.
What does migrating from NPSP to Nonprofit Cloud actually involve?
Because the data models differ, data migration from NPSP to Nonprofit Cloud is a re-implementation, not a simple export and import. Household records map to Person Accounts, Opportunities remap to Gift Commitments and Gift Transactions, and every automation and integration built on NPSP's package field names has to be rebuilt against NPC's objects. Since Person Accounts and NPSP can't share an org, a migration often runs in a new org. Timelines vary with system complexity and data quality, and Nonprofit Cloud's standardized structure makes data mapping cleaner once the plan is set. Two things reliably separate a smooth move from a painful one: technical expertise on the build, and training for the team, because adoption is where migrations succeed or stall.
How Does MagicFuse Approach the NPSP vs Nonprofit Cloud Decision?
- We've built on both platforms. NPSP implementations for mission-driven nonprofits, and Nonprofit Cloud implementations for animal-welfare, humanitarian, and civic organizations across the UK, Poland, and Switzerland. We know both data models in delivery, not just on paper.
- We recommend based on your situation, not on which platform is more profitable to implement. If NPSP is the right call for your org right now, we'll say so.
- We're an official Salesforce PDO, independently certified to build on the platform, with 270+ certifications across the team, including NPC and NPSP specialists.
- We scope before we contract. Every engagement starts with a structured discovery phase: written scope, data-model design, and cost, before any implementation work begins. A faith-based mission nonprofit came to us with donor and fundraising data scattered across several sources and no structured way to manage it. We implemented Sales Cloud with NPSP, centralized the data, set up fund tracking and automation, and imported thousands of records cleanly. NPSP was the right choice: the needs were clear, the team was small, and a full NPC build would have been over-engineered for what they needed.
An animal-welfare nonprofit had fundraising, communications, and campaign data fragmented across systems that never talked to each other, including millions of records that had never been deduplicated. We implemented Nonprofit Cloud and Marketing Cloud: complex data-model design, migration and deduplication at scale, Stripe and direct-debit integrations, and unified operations. Here NPC was right: the organization's scale, integration complexity, and Marketing Cloud needs made the native architecture the only viable long-term path.
FAQs
- Is NPSP being discontinued?
No. NPSP is fully supported and still available to existing users. It has been feature-frozen since March 2023, and since December 2025 it's no longer set up automatically in new production orgs, but Salesforce has announced no retirement date. NPSP is also open source, so orgs could keep installing it even in that unlikely event.
- Is Nonprofit Cloud an upgrade to NPSP?
No. It's a different product with a different data model and architecture. You don't upgrade from one to the other, you re-implement. Treating it as an upgrade sets the wrong expectation for the work involved.
- What is Agentforce Nonprofit, and how does it relate to Nonprofit Cloud?
Agentforce Nonprofit is the current name for Nonprofit Cloud, renamed in October 2025. Separately, "Agentforce 360 for Nonprofits" is umbrella branding for Salesforce's whole nonprofit lineup, which still includes NPSP. So Agentforce Nonprofit is the integrated platform, NPSP is the managed-package suite, and the umbrella name covers both.
- Can I run NPSP and Nonprofit Cloud in the same Salesforce org?
No. Nonprofit Cloud relies on Person Accounts, and Person Accounts can't be enabled in an org that already has NPSP installed, or the reverse. That's a core reason migrations often move to a new org.
- Is Salesforce free for nonprofits?
Not entirely. Eligible nonprofits receive a free grant through the Power of Us program: 10 Agentforce Nonprofit Enterprise Edition licenses, or 10 Sales and Service Cloud Enterprise Edition licenses. Beyond that grant, additional licenses and products are paid, so neither platform is truly free at scale.
- How do Salesforce Nonprofit Cloud pricing and NPSP pricing compare?
NPSP is free to install, so your cost is the standard Salesforce licenses it runs on. Nonprofit Cloud pricing runs through the Power of Us grant plus paid Enterprise Edition licenses above it. For a full breakdown of what each actually costs, see our Salesforce for nonprofits cost guide.
- How much does it cost to migrate from NPSP to Nonprofit Cloud?
It depends on your data quality, the number and complexity of your integrations, and how much custom automation you've built. A migration is a data-model remap, an automation rebuild, and an integration reconnect, so scope varies widely. The honest answer comes from a discovery phase, not a price list.
- Do new nonprofits still get NPSP through the Power of Us program?
Not by default. New organizations have the choice, but they're no longer steered to NPSP. Orgs implementing through Power of Us now start on Nonprofit Cloud architecture.
- Should we migrate from NPSP to Nonprofit Cloud?
Only if your situation calls for it. If your NPSP org is stable and your fundraising is straightforward, staying put is often the responsible choice. If you're starting fresh, running connected programs, planning AI or constituent portals, or maintaining an NPSP org buried in technical debt, NPC is likely worth the move. The four questions above are the fastest way to tell.
