How to Transition from NPSP to Nonprofit Cloud: A Step-by-Step Migration Guide
Moving from the Nonprofit Success Pack to Nonprofit Cloud, now called Agentforce Nonprofit, is a reimplementation in a new org, not an upgrade. This guide covers whether and when to move, how households, gifts and campaigns map to the new data model, the load order Salesforce recommends, and a step-by-step plan from audit to go-live.
Key Takeaways
- Nonprofit Cloud, renamed Agentforce Nonprofit in December 2025, is built into the core Salesforce platform. NPSP is a set of managed packages. They use different data models.
- Salesforce says the move "more closely resembles a reimplementation than a traditional software upgrade" and strongly recommends a new org. The two products cannot actively coexist in one org.
- Every Contact becomes a Person Account. Households become business accounts with a Party Relationship Group. Opportunities and payments split into Gift Commitments, Gift Transactions and, for gifts still being cultivated, Opportunities.
- Some NPSP objects have no destination: Engagement Plans, Levels and Customizable Rollups are archived or rebuilt, not migrated.
- NPSP is still supported, so you can plan the move. Start with a business and technical audit, then map, build, load in dependency order, test and train by role.
An NPSP to Nonprofit Cloud migration moves your donors, households, gifts and programs from the Nonprofit Success Pack (NPSP) managed packages onto Salesforce's newer, platform-native nonprofit product. The product is now officially called Agentforce Nonprofit (formerly Nonprofit Cloud). This guide uses "Nonprofit Cloud" because Salesforce's own documentation still does.
This guide is for executive directors, development and operations leaders, and Salesforce admins at growing and mid-market companies in the nonprofit sector, from single-program charities to multi-site and enterprise organizations. It replaces our 2025 version of this article. Product facts now link to Salesforce's own documentation and migration guide. We corrected the data-model mapping and removed figures and examples we could not source.
What Does It Take to Transition from NPSP to Nonprofit Cloud?
Treat it as a new implementation with a data migration, not a package upgrade. Provision a new Nonprofit Cloud org, audit how your NPSP org is really used, map each NPSP object to its new home, rebuild automation and integrations, then load data in dependency order and test it before cutover. Gift history is usually the hardest and longest part.
| Phase | What happens | Output |
|---|---|---|
| 1. Decide | Confirm the case for moving and the timing, given NPSP is still supported | A go/no-go decision and a target window |
| 2. Audit | Review business processes, data, automation, integrations, third-party packages and licences | An inventory, with each item marked keep, adapt or redesign |
| 3. Map and design | Decide the account model, households, campaigns, gift structure and what to archive | An object and field mapping, plus design decisions |
| 4. Build | Provision and configure the new org, permission sets, automation and integrations | A configured Nonprofit Cloud org |
| 5. Migrate | Clean, de-duplicate and load data in the recommended order, with trial runs in a sandbox | Reconciled record counts and totals |
| 6. Launch | User acceptance testing, role-based training, cutover and hypercare | A live org that staff trust |
What Is Nonprofit Cloud, and How Is It Different from NPSP?
Nonprofit Cloud is Salesforce's nonprofit product built into the core platform. NPSP is a set of free, open-source managed packages installed on top of Salesforce. Salesforce launched the new Nonprofit Cloud in 2023 and describes it as "structured completely differently from NPSP". Fundraising, programs, case management and outcomes now share one data model under one licence.
Salesforce announced the new direction in March 2023: build nonprofit features into the core of Salesforce instead of layering applications on top. In December 2025 it renamed the product Agentforce Nonprofit, with prebuilt AI agents. Help articles, the product page and the official guides still say "Nonprofit Cloud" and abbreviate the new name as AFNP. Search for both names when you research.
| NPSP | Nonprofit Cloud (Agentforce Nonprofit) | |
|---|---|---|
| Delivery | Managed packages on Enterprise Edition, open source | Built into the platform, switched on by licences and settings |
| Individuals | Contacts, each tied to an account (a Household Account by default) | Person Accounts, required |
| Households | Household Account model | Business account plus a Party Relationship Group of type Household |
| Gifts | Opportunities, Payments, Recurring Donations | Gift Commitments, Gift Transactions, and Opportunities for major gifts and grants |
| Funds | General Accounting Units and Allocations | Gift Designations |
| Programs | Separate Program Management Module package | Native Program Management, Case Management and Outcome Management |
| Volunteers and grants | Separate packages (Volunteers for Salesforce, Outbound Funds) | Native Volunteer Management; Grantmaking for funders |
| Rollups | NPSP Customizable Rollups | Data Processing Engine definitions (Donor Gift Summary) |
For a feature-by-feature view of the two products, see our NPSP vs Nonprofit Cloud comparison. Salesforce lists everything in the product on its What's Included in Nonprofit Cloud page.
Do You Have to Leave NPSP, and When Should You Move?
No. NPSP is still supported, so there is no deadline forcing a rushed move. But Salesforce now puts new nonprofit products into Agentforce Nonprofit, and NPSP is no longer offered pre-configured in new production orgs. Move when your needs match what only the new product offers, or when your NPSP org needs a rebuild anyway.
The facts, from Salesforce: its managed packages page says NPSP "is used by thousands of organizations and will continue to be supported". Trailhead notes that as of December 2025, NPSP is no longer offered as a preconfigured package in production orgs, and that new products from Salesforce for Nonprofits are part of Agentforce Nonprofit. We found no official end-of-life date for NPSP, so treat any date you see quoted with caution.
Plan the move now if you need native program, case or outcome management; you run several nonprofit packages that you want on one data model; you want the prebuilt Agentforce agents; your NPSP org is heavily customised and due a rebuild; or you are about to make a big investment in NPSP customisation.
Wait and optimise NPSP if your fundraising runs well on it, you have no admin capacity for a reimplementation, a key third-party app does not yet support Nonprofit Cloud, or a major campaign or year-end giving season falls in the window.
If you decide to stay for now, an org that is clean and documented makes the later move much cheaper. Our NPSP implementation services cover that work.
Can You Upgrade NPSP in Place?
Not safely. Salesforce strongly recommends implementing Nonprofit Cloud in a new org. Its migration guide says NPSP and Agentforce Nonprofit "cannot actively coexist within an org". Features switched on by accident before migration finishes cannot be reverted, and uninstalling NPSP afterwards is error-prone. A new org starts clean and keeps the old one available for reference.
Salesforce publishes the guide, the field-level mapping spreadsheets and the implementation guides on one Help page, Nonprofit Cloud Migration and Implementation Guides. It describes them as written for experienced Salesforce admins and consultants. The current Agentforce Nonprofit Migration Guide (version 2.0, June 2026) makes three points that shape every plan:
- It is a reimplementation. The move "more closely resembles a reimplementation than a traditional software upgrade". The guide gives a framework for decisions, not a field-by-field manual.
- Person Accounts are mandatory. Every existing Contact must become a Person Account. In Salesforce, Person Accounts can't be disabled once enabled, and NPSP does not support them. This is one more reason not to switch them on in your live NPSP org.
- The guide covers NPSP only. The Program Management Module, Nonprofit Cloud Case Management, Volunteers for Salesforce and Outbound Funds each have their own mapping spreadsheet.
Power of Us customers start by contacting the Power of Us desk for their region to provision the new org. Under the Power of Us Program, eligible nonprofits can receive 10 donated Enterprise Edition licences and choose Agentforce Nonprofit as their donation product. Confirm your eligibility and editions with Salesforce.
How Does NPSP Data Map to the Nonprofit Cloud Data Model?
People move to Person Accounts, relationships move to standard relationship objects, and gifts split three ways. One-time gifts and installments become Gift Transactions. Pledges and recurring donations become Gift Commitments. Only major gifts and grants still being worked stay as Opportunities. Funds become Gift Designations. The table follows Salesforce's official mapping.
| NPSP object | Nonprofit Cloud destination | Watch out for |
|---|---|---|
| Contact | Person Account | Mandatory for every individual |
| Household Account | Business account with a Party Relationship Group (type Household) | Migrate only true households with more than one member |
| Organization Account | Business account | Account Account Relationship is new and can link organizations |
| Affiliation | Account Contact Relationship, or Constituent Role | Only one Account Contact Relationship per person and organization |
| Relationship | Contact Contact Relationship, typed by Party Role Relationship | Load the Party Role Relationship types first |
| Address | Contact Point Address (with Contact Point Email and Phone) | Address features are more limited than NPSP's today |
| Opportunity (closed gift) | Gift Transaction | Most historical giving lands here |
| Opportunity (open major gift or grant) | Opportunity | Reserved for gifts that need active cultivation |
| Recurring Donation | Gift Commitment plus Gift Commitment Schedule | Each payment becomes a Gift Transaction |
| Payment | Gift Transaction; negative payments become Gift Refunds | Refunds are a separate object |
| General Accounting Unit | Gift Designation (one to one) | Load before gifts |
| GAU Allocation | Gift Transaction Designation or Gift Default Designation | Up to 50 designations per gift transaction |
| Soft credits (three sources) | Gift Soft Credit | Attaches at the Gift Transaction level only |
| Tribute fields | Gift Tribute | A transaction doesn't inherit its commitment's tributes |
| Campaign hierarchy | Top-level Campaign plus Outreach Source Codes | Child campaigns become source codes |
| Tasks, Events, Emails | Same objects | Load last |
Programs follow a separate mapping. Program Management Module records map as Program to Program, Program Engagement to Program Enrollment, Service to Benefit, Service Session to Benefit Session, and Service Delivery to Benefit Disbursement or Benefit Assignment. Volunteers for Salesforce jobs, shifts and hours map to Job Position, Job Position Shift and Job Position Assignment. The full object list is on Salesforce's Nonprofit Cloud data model objects page.
Which NPSP Conversions Need the Most Care?
Gifts, households, campaigns and anything with no direct destination. Salesforce's guide calls gift migration "one of the most complex and time consuming portions" of any migration. Households and campaigns need design decisions before they are moved. Engagement Plans, Levels and rollups don't map at all, so they have to be archived or rebuilt.
What Is the Step-by-Step Plan for an NPSP to Nonprofit Cloud Migration?
Eight steps, from audit to hypercare. Audit first, so the design reflects how teams really work, not how NPSP was set up years ago. Map and decide before you build, and run full trial loads in a sandbox before the production load. Each step below follows the phases in Salesforce's migration guide.
Our Nonprofit Cloud implementation service follows the same order: audit the NPSP org, map every field before migration, build, migrate gift and case history, then train by role.
In What Order Should You Load NPSP Data into Nonprofit Cloud?
Parents before children, people before gifts, activities last. Salesforce's guide sets a sequence: users and relationship types, then accounts and Person Accounts, then relationships and addresses, then campaigns and designations, then gifts, then tasks and events. Loading out of order breaks lookups and forces rework.
Users and relationship types
Load users, including inactive ones, and enable Create Audit Fields if you need to keep the original "Created by" history. Then load Party Role Relationship records, which define relationship types.
Accounts, Person Accounts and groups
Household accounts, organization accounts, Person Accounts, then Party Relationship Groups and their memberships. Salesforce explains the new model in its Person Accounts and Party Relationship Groups article.
Relationships and contact points
Account Contact Relationships, Contact Contact Relationships, then Contact Point Address, Email and Phone.
Campaigns, source codes and designations
Top-level Campaigns, Outreach Source Codes, then Gift Designations, so every gift has somewhere to point.
Commitments, transactions and their children
Gift Commitments and schedules, Opportunities, Gift Transactions, refunds, soft credits, tributes and designations.
Tasks and events
Activities map one to one and load last, once every record they relate to exists.
The tools are standard Salesforce ones. The guide is software-agnostic, so any ETL tool works. Salesforce's data migration best practices recommend loading in dependency order, testing a single record first, upserting on external IDs and validating with record counts and spot checks. Data Loader handles bulk loads through Bulk API 2.0. For loading techniques, see our guide to efficient ways to load data into Salesforce.
What Do You Gain from Nonprofit Cloud?
One data model for fundraising, programs, cases and outcomes, under one licence, with Salesforce's new nonprofit features built on top. With NPSP, the same ground needs several packages. The gains are real, but they come from configuring the new modules around your work, not from the migration itself.
Fundraising
Gift Entry, Gift Commitments and Transactions, designations, soft credits and tributes, organised into four apps from fundraising operations to strategy.
Programs and cases
Native Program Management for programs, benefits, disbursements and attendance, plus case referral intake, care plans and assessments.
Outcome Management
Impact strategies, indicator definitions and indicator results connect services delivered to the results you promised funders.
Volunteer Management
Job positions, shifts, assignments and hours, with an Experience Cloud portal, in place of the separate Volunteers for Salesforce package. See Volunteer Management.
Relationship view
Actionable Relationship Center shows households, organizations and connections as an interactive graph, built on standard relationship objects.
Agentforce agents
Salesforce lists Nonprofit Cloud agents for philanthropic research, volunteer management, participant management and donor support. They require Nonprofit Cloud and Einstein for Nonprofits licences.
Grantmaking is offered separately for organizations that award funds, with a grantee portal template. Reporting runs on standard reports plus Tableau and CRM Analytics. If you are weighing where these modules fit your operation, our Salesforce for nonprofits page shows how we connect donors, programs, grants and finance.
How Do You Know You Are Ready to Go Live?
When the numbers reconcile, the key scenarios pass and every role can do its daily work in the new org. Compare record counts and gift totals by year, fund and campaign against NPSP. Have each team run its own test cases. Confirm that every integration writes to the new objects before you switch it over.
- Reconciliation: record counts per object, and total giving by year, designation and campaign, match the NPSP source or every difference is explained.
- Gift scenarios: one-time gift, recurring gift, pledge payment, refund, soft credit, tribute and a split designation all behave as designed.
- Rollups: Data Processing Engine definitions have run and donor giving summaries match the old rollups for a sample of donors.
- Integrations: donation forms, payment processing, email marketing and accounting are tested end to end in the sandbox.
- Access: every user has the right permission set licences and groups, and nobody holds admin rights they don't need.
- Training: gift officers, program staff, finance and volunteer coordinators have each been trained on their own workflow.
- Fallback: the NPSP org stays read-only, and a full backup is stored, until hypercare ends.
Data quality decides most of these checks. In a published NPSP case study, Twopir cleaned and de-duplicated every source file before each import run and added validation rules. The project reports a 100% data import success rate, with zero failed records after cleanup. That project was an NPSP rebuild, not a Nonprofit Cloud migration, but the discipline is the same. For integrations, our Classy integration case study shows the kind of donation sync that has to be repointed when gift objects change.
Should You Migrate In-House or With a Salesforce Partner?
In-house can work for a small, lightly customised org with an experienced admin who has time. Salesforce wrote its guides for experienced admins and consultants. A partner pays off when gift history is large or complex, several nonprofit packages are installed, integrations must be rebuilt, or nobody fully understands the current org.
In-house fits if you have a certified admin with migration experience, a modest gift history, few custom objects and integrations, and NPSP is the only nonprofit package installed.
Bring in a partner if you run PMM, Volunteers for Salesforce or Outbound Funds as well, have years of recurring gifts and soft credits, depend on payment or accounting integrations, or the original implementer has left.
Twopir Consulting has worked with 500+ clients since 2014. We implement, rescue, optimize, and integrate complex CRM and revenue systems, including Nonprofit Cloud implementations and NPSP migrations for mission-driven organizations.
The Bottom Line
Moving from NPSP to Nonprofit Cloud is a reimplementation on a new data model, in a new org. NPSP is still supported, so decide on your own timetable. Once you commit, audit first, settle the design decisions, load in dependency order, and prove the numbers before you switch.
- 1
Decide on need, not fear: NPSP has no announced end date.
- 2
Plan for a new org. The two products can't run side by side.
- 3
Settle households, gifts and campaigns on paper before any data moves.
- 4
Archive or rebuild what has no destination: Engagement Plans, Levels and rollups.
- 5
Reconcile totals, test real scenarios and train each role before cutover.
Plan Your Move from NPSP with a Salesforce Architect
On a 30-minute discovery call, a Twopir Salesforce architect will talk through your NPSP org, the packages and integrations around it, and whether to move now or optimise first. You will leave knowing the biggest risks in your migration.
Schedule a Discovery CallFrequently Asked Questions
Salesforce has not announced an end-of-life date. Its managed packages page says NPSP will continue to be supported. Since December 2025, NPSP is no longer offered as a preconfigured package in new production orgs, and new Salesforce nonprofit products are released as part of Agentforce Nonprofit.
Yes. In December 2025 Salesforce renamed Nonprofit Cloud to Agentforce Nonprofit and added prebuilt AI agents. Salesforce Help, the product pages and the implementation guides still often say Nonprofit Cloud, so you will see both names for the same platform-native product.
Salesforce strongly recommends against it. Its migration guide says NPSP and Agentforce Nonprofit cannot actively coexist in one org, features switched on early can't be reverted, and removing NPSP afterwards is error-prone. Plan the move into a new org instead.
For an NPSP migration, yes. Salesforce's migration guide makes moving every Contact to a Person Account mandatory, and Fundraising and full Program Management rely on them. Person Accounts can't be turned off once enabled, so test them in a sandbox first.
Closed gifts and payments become Gift Transactions, and refunds become Gift Refunds. Recurring donations become a Gift Commitment with a Gift Commitment Schedule. Only major gifts and grants still being cultivated stay as Opportunities. GAU allocations become Gift Designations.
Salesforce provides a migration guide and object-mapping spreadsheets rather than a one-click tool. The guide is software-agnostic, so the data is moved with standard tools such as Data Loader or an ETL platform, using legacy IDs as external IDs and a set load order.
Eligible nonprofits can receive 10 donated Enterprise Edition licences through Power of Us and can choose Agentforce Nonprofit as the donation product. Additional licences, add-ons and implementation are paid, so confirm eligibility and current terms with Salesforce.
Twopir Consulting
Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems, including Nonprofit Cloud implementations, NPSP migrations and fundraising integrations for nonprofits.
