NPSP vs Nonprofit Cloud: What Is the Difference?
The Nonprofit Success Pack (NPSP) is a free, open-source package built on top of Salesforce that handles donor management, gift tracking, and household structures for nonprofits. Nonprofit Cloud is Salesforce's native product line that replaces NPSP with built-in fundraising, program management, and case management features that run directly on the Salesforce platform without a separate package. The core difference: NPSP is an add-on maintained by the community. Nonprofit Cloud is a Salesforce product maintained by Salesforce. Organizations currently on NPSP will need to plan a migration, as Salesforce is investing its development resources in Nonprofit Cloud, not NPSP.
Is Salesforce retiring NPSP?
Salesforce has not announced a hard end-of-life date for NPSP as of April 2026. NPSP remains available and functional. What has changed is where Salesforce is directing its engineering and feature development. New fundraising features, AI capabilities (Agentforce for Nonprofits), and platform innovations are being built for Nonprofit Cloud, not NPSP. The practical effect: NPSP will continue working, but it will fall further behind as Salesforce adds capabilities that only exist in Nonprofit Cloud.
This is the pattern Salesforce follows with every product transition. They don't shut off the old product overnight. They stop investing in it and let the feature gap grow until migration becomes the obvious choice.
What does NPSP include that Nonprofit Cloud does not?
NPSP includes several features that nonprofit teams rely on daily:
Household Account model. NPSP groups individual contacts into household accounts, tracking donations at both the individual and household level. Nonprofit Cloud uses a person account model, which handles this differently.
Recurring Donations. NPSP has its own recurring donation object with rollup calculations, payment tracking, and installment schedules. Nonprofit Cloud's fundraising module handles recurring gifts differently, with its own data model.
Customizable Rollups (CRLP). NPSP's rollup engine calculates total giving, largest gift, consecutive years of giving, and other donor metrics. Nonprofit Cloud uses Salesforce's standard rollup summaries and custom reporting.
Batch Gift Entry. NPSP includes a batch data entry screen for processing checks, event proceeds, and offline gifts. Nonprofit Cloud does not have a direct equivalent at the same level of maturity.
What does Nonprofit Cloud include that NPSP does not?
Nonprofit Cloud adds capabilities that NPSP never had:
Program Management Module (PMM). Track programs, services, participants, and outcomes. This is built into Nonprofit Cloud. NPSP organizations had to build custom objects or use third-party apps for program tracking.
Case Management. Built-in case management for human services organizations. Intake forms, service plans, referrals, and outcome tracking.
Fundraising built on standard Salesforce objects. Nonprofit Cloud's fundraising sits on standard Opportunities and Accounts rather than custom NPSP objects. This means better compatibility with Salesforce's reporting, AI, and automation features.
Agentforce integration. Salesforce's AI features (Einstein, Agentforce) are designed to work with standard Salesforce objects. Nonprofit Cloud's data model aligns with these tools. NPSP's custom objects (like npe03__Recurring_Donation__c) are not natively supported by AI features.
Ongoing Salesforce investment. New features, performance improvements, and security updates will be built for Nonprofit Cloud. NPSP receives maintenance updates but not new capabilities.
When should an organization migrate from NPSP to Nonprofit Cloud?
Migration makes sense when one or more of these conditions is true:
You are starting a new Salesforce implementation. If you are setting up Salesforce for the first time, start with Nonprofit Cloud. There is no reason to implement NPSP in 2026 unless you have a specific technical requirement that Nonprofit Cloud does not yet cover.
You need program management. If your organization tracks programs, participants, and outcomes, Nonprofit Cloud's PMM module eliminates the need to build custom objects or buy third-party apps.
You want to use Salesforce AI features. Einstein and Agentforce work best with standard Salesforce objects. Nonprofit Cloud's data model is compatible. NPSP's custom objects require workarounds.
Your NPSP customizations have become unmanageable. If your org has dozens of custom Flows, Process Builders, and Apex triggers built on top of NPSP's data model, a migration to Nonprofit Cloud can simplify the architecture.
Your Salesforce contract is up for renewal. Renewal is a natural checkpoint to evaluate whether NPSP is still the right fit. Salesforce may offer migration incentives during renewal negotiations.
What does an NPSP to Nonprofit Cloud migration involve?
A migration is not a simple upgrade. NPSP and Nonprofit Cloud use different data models. The work involves:
Data mapping. Every NPSP object (Opportunities with Record Types, Recurring Donations, Allocations, GAU, Households) needs to be mapped to its Nonprofit Cloud equivalent. Some mappings are straightforward. Others require data transformation.
Historical data migration. Donation history, recurring gift schedules, and campaign data need to move from NPSP objects to Nonprofit Cloud objects while preserving relationships and totals.
Automation rebuild. Any Flows, Process Builders, or Apex triggers built on NPSP objects will break. They need to be rebuilt against Nonprofit Cloud's data model.
Integration updates. If external systems (payment processors, marketing tools, accounting software) connect to NPSP objects, those integrations need to be reconfigured.
User training. Staff who learned NPSP's screens, terminology, and workflows need to learn the Nonprofit Cloud equivalents. The concepts are similar but the navigation and field names are different.
Testing. End-to-end testing of donation processing, recurring gift calculations, reporting accuracy, and integration data flow.
Timeline: 6-12 weeks for a typical nonprofit migration, depending on data volume and customization complexity.
How much does the migration cost?
Migration costs depend on three factors: how much data you have, how many custom automations need rebuilding, and how many integrations need updating. A small nonprofit with clean data, few customizations, and no integrations might migrate for $10,000-$15,000. A mid-size organization with 100,000+ records, 20+ Flows, and 3-4 integrations is looking at $25,000-$50,000. Complex migrations with heavy Apex customization can exceed $50,000.
The biggest cost driver is data cleanup. If your NPSP data has duplicates, inconsistent formats, and orphaned records, you are paying to clean that up before migrating it. Clean data migrates faster and cheaper.
Should I wait to migrate?
Waiting is a valid strategy if your NPSP instance is stable and meeting your needs. There is no urgency if you are not planning to use AI features, you don't need program management, and your customizations are manageable.
The risk of waiting too long: as more nonprofits migrate, the pool of consultants with NPSP expertise shrinks. The consultants who know both NPSP and Nonprofit Cloud are the ones you want for a migration, and their availability will decrease over time.
The pragmatic approach: start planning now, migrate when your contract renews or when you have a business trigger (new program launch, data quality audit, staffing change) that creates a natural project window.
Jeremy Carmona is a 13x certified Salesforce Architect with the Nonprofit Cloud Consultant certification and 14 years of nonprofit Salesforce experience starting at Environmental Defense Fund. Take the free AI Readiness Scorecard at clearconciseconsulting.com/scorecard.