NPSP to Nonprofit Cloud Migration: A Practical 2026 Guide

Migrating from NPSP to Nonprofit Cloud (now called Agentforce Nonprofit) isn't an upgrade button. It's a re-implementation: you move your data, automations, and reports into a new data model built natively on Salesforce Core, usually in a new org. The good news is that NPSP isn't going away tomorrow, so you have time to do it right. This guide walks through where things stand in 2026, how the two data models differ, and a step-by-step plan for a migration that doesn't derail your fundraising.

Where NPSP stands in 2026

If you're running the Nonprofit Success Pack (NPSP), here are the facts that matter for planning:

• NPSP is still supported. Salesforce hasn't announced an end-of-life date, and you can still open support cases.
• NPSP is no longer evolving. Feature development stopped in March 2023, when Salesforce launched Nonprofit Cloud. Every new nonprofit capability, including AI, is being built on the new platform.
• Nonprofit Cloud has a new name. In October 2025, Nonprofit Cloud was rebranded as Agentforce Nonprofit, part of the broader Agentforce 360 for Nonprofits suite.
• New nonprofits no longer get NPSP by default. Since December 2025, according to Equals11, the Power of Us program no longer issues NPSP-based licenses to new applicants. Eligible organizations can request 10 donated Agentforce Nonprofit Enterprise Edition licenses, or 10 Sales and Service Cloud licenses on which NPSP can be installed manually (Salesforce Ben).

In short: "supported" is not the same as "actively developed." You don't have to migrate this quarter, but staying on NPSP should be a documented decision with a date to revisit it, not a default.

Should you migrate now, or wait?

Not every nonprofit needs to move immediately. Here's a practical way to decide.

Signs it's time to migrate

• You're already replacing your fundraising platform, payment processor, or a major integration.
• Funders or your board are asking for outcome reporting across programs that your current setup can't produce.
• AI is on your roadmap. Agentforce capabilities for nonprofits are being built for Agentforce Nonprofit, not NPSP.
• Custom code built around NPSP is getting expensive to maintain, and every Salesforce release means another round of regression testing.
• You need people to belong to more than one household or group, something NPSP's model doesn't handle well.

Signs it's reasonable to wait

• NPSP still does what your team needs, and users are productive.
• Your data is in reasonable shape, and no one is asking for reports you can't build.
• You don't have the budget or internal bandwidth for a project of this size this year.

Even if you wait, use the time well. The cleanup and inventory work described below pays off whichever way you go. If you need help making the case internally, our guide on how to build a business case for a Salesforce implementation applies here too.

NPSP vs Agentforce Nonprofit: the data model differences that matter

The biggest reason this migration takes planning is that the two products don't store information the same way. NPSP is a set of managed packages layered on top of Sales Cloud. Agentforce Nonprofit is built natively on Salesforce Core, with its own objects for fundraising, programs, and relationships.

• Constituents: Contacts grouped into Household Accounts in NPSP; Person Accounts plus Party Relationship Groups (households still available) in Agentforce Nonprofit
• Donations: Opportunities, Recurring Donations, and Payments in NPSP; Gift Commitments, Gift Transactions, and Gift Designations in Agentforce Nonprofit
• Relationships: Relationships and Affiliations in NPSP; Party role relationships and Account Contact Relationships in Agentforce Nonprofit
• Programs: Program Management Module (Programs, Services) in NPSP; Programs and Benefits, with built-in outcome tracking in Agentforce Nonprofit
• Case management: Referral, program assignment, Case Plan in NPSP; Referral, case, Care Plan, program assignment in Agentforce Nonprofit
• Architecture: Managed packages in NPSP; Native to Salesforce Core, includes OmniStudio in Agentforce Nonprofit

From households to Person Accounts

In NPSP, every contact lives in exactly one household account. Agentforce Nonprofit uses Person Accounts, which merge account and contact fields into a single record for each individual, and Party Relationship Groups to connect people to households and other groups. That means one person can belong to more than one group, like a child linked to two families. It's more flexible, but it changes how you count records, build reports, and integrate with other systems.

From Opportunities to the gift model

NPSP tracks donations as Opportunities with record types. Agentforce Nonprofit replaces this with a purpose-built gift model:

• Gift Commitment: the promise of a gift, whether one-time, recurring, or paid in installments
• Gift Transaction: an actual payment toward that commitment
• Gift Designation: where the money is earmarked, such as a specific fund or program

This is where most migration effort goes. Every rollup, report, dashboard, and integration that touches Opportunities or Recurring Donations needs a decision: keep, rebuild, or retire.

Features without a direct equivalent

Some NPSP pieces don't have a one-to-one replacement. Volunteers for Salesforce (V4S) isn't included in Agentforce Nonprofit, NPSP's seasonal and verified address features don't carry over in the same way, and the Program Cohort object has no direct counterpart. Identify these early so they don't surprise you mid-project.

Step-by-step: how to migrate from NPSP to Nonprofit Cloud

There's no in-place upgrade. Most migrations are built in a new Agentforce Nonprofit org and cut over once data and processes are validated. Here's the sequence we recommend.

1. Assess and align on goals

Start with why. Are you migrating to get outcome reporting, unlock AI, reduce maintenance, or all three? Write it down. Those goals decide what you rebuild, what you improve, and what you leave behind. Resist the urge to recreate NPSP one-to-one in a new platform.

2. Inventory everything that touches NPSP

List every automation, rollup, report, dashboard, integration, and AppExchange app connected to NPSP objects, and assign an owner to each. This inventory becomes your migration scope and your testing checklist.

3. Define your terms

Agree on what a household, an active donor, and a closed gift mean in your organization, and when a pledge becomes a gift. These definitions drive your data mapping and prevent arguments after go-live.

4. Clean your data before you move it

Deduplicate constituents, archive records you no longer need, and fix inconsistent fields. Dirty data gets paid for twice: once during the move and again after it lands in the new structure. We covered why this matters in Your Salesforce Org Is Ready for AI Agents. Your Data Isn't.

5. Map NPSP objects to the new data model

Build a field-level mapping from NPSP to Agentforce Nonprofit objects, define the import order based on dependencies (accounts before gifts, commitments before transactions), and plan how you'll convert households to Person Accounts and preserve soft credits and affiliations. Keep an old-ID-to-new-ID crosswalk so you can trace every record.

6. Build and configure the new org

Set up an Agentforce Nonprofit sandbox, then rebuild automations in Flow, modernize page layouts with Lightning pages and Dynamic Forms, and update profiles and permission sets so users keep the access they need. This is your chance to retire workarounds instead of copying them.

7. Update integrations and apps

Check every connected system, from payment processors to email tools and the AppExchange apps in your inventory, for Agentforce Nonprofit compatibility. Some vendors have native support; others need reconfiguration or replacement.

8. Migrate data in batches and test

Load data into a sandbox first, in small batches, and validate totals against NPSP: number of donors, total giving by year, open recurring commitments. Then run a full dress rehearsal before the production load.

9. Train, go live, and support

Give each team role-based training on the new model, plan the cutover around your fundraising calendar (avoid year-end giving season), and hold office hours for the first weeks after launch.

How long does an NPSP migration take?

It depends on how much you've built. A tidy org with a short list of reports and integrations can move in weeks. An org with years of undocumented automation, custom code, and duplicate records should plan for several months. The inventory in step 2 is the best predictor of your timeline and budget.

Common mistakes to avoid

• Treating it as a lift-and-shift. Rebuilding every NPSP customization in the new platform carries old problems forward.
• Underestimating reporting. Reports built on Opportunities won't work on Gift Transactions. Budget time to rebuild the ones leadership relies on.
• Cutting over during peak giving. Schedule go-live away from year-end campaigns and major events.
• Skipping the data cleanup. Migration is the cheapest moment to fix your data. Afterward, it only gets harder.
• Ignoring user adoption. The new model changes daily work for gift processors and program staff. Involve them early.

Why work with a Salesforce partner on your migration

An NPSP migration touches fundraising, programs, finance, and every system connected to your CRM. A partner who has done it before helps you set scope, avoid rebuilding what you don't need, and keep fundraising running during the transition. If you're comparing options, start with our checklist for evaluating a Salesforce consulting partner.

At Hikko, we work with nonprofits to focus on the business of their mission, and we take a practical approach to responsible AI adoption for nonprofits. If you're weighing a move to Agentforce Nonprofit, we can help you assess your org, size the effort, and build a plan your team can stand behind.

Planning your NPSP migration? Talk to our team and get a clear picture of what moving to Agentforce Nonprofit will take for your organization.

Frequently asked questions

Is NPSP being discontinued?
No end-of-life date has been announced. NPSP remains supported, but Salesforce stopped developing new features for it in March 2023 and is focusing innovation on Agentforce Nonprofit.

Is Nonprofit Cloud the same as Agentforce Nonprofit?
Yes. Salesforce renamed Nonprofit Cloud to Agentforce Nonprofit in October 2025.

Can I upgrade NPSP to Nonprofit Cloud in my existing org?
There's no in-place upgrade. Because the data models are different, migrations typically involve building in a new Agentforce Nonprofit org and moving data, automations, and reports into it.

Do I have to migrate off NPSP?
Not right now. Existing NPSP customers aren't required to migrate, but new features, including AI capabilities, are being built for Agentforce Nonprofit.

What happens to my donations data?
Opportunities, Recurring Donations, and Payments are transformed into the gift model: Gift Commitments, Gift Transactions, and Gift Designations. Historical giving can be migrated, but reports built on Opportunities need to be rebuilt.

How much does it cost to migrate from NPSP to Nonprofit Cloud?
Cost depends mostly on the volume of customizations, integrations, and data cleanup required. Eligible nonprofits can get donated Agentforce Nonprofit licenses through the Power of Us program, so the main investment is usually implementation work.