NPSP vs Agentforce Nonprofit: should you migrate in 2026?
Salesforce has stopped adding features to the Nonprofit Success Pack, but it has not set a retirement date. Here is what that means for your org, what actually changes in a migration, and how to decide on timing.
Short answer: you do not have to migrate. NPSP is still supported and upgraded, and Salesforce has announced no end-of-life or end-of-sale date. Plan a move when you are already redesigning your data model, need capabilities only Agentforce Nonprofit offers, or are starting a new org.
What happened to NPSP
Salesforce launched its new Nonprofit Cloud in March 2023, built on the core platform rather than as a managed package. In 2024 it announced end of innovation for its nonprofit managed packages, NPSP included. End of innovation means no new features. It does not mean the end of support: NPSP orgs still receive maintenance and release upgrades, and the package can still be installed.
Nonprofit Cloud has since been rebranded as Agentforce Nonprofit. Salesforce recommends it for new customers, and new Agentforce Nonprofit implementations now outnumber new NPSP implementations.
Licensing for eligible organizations still starts with the Power of Us program, which has offered nonprofits 10 free licenses for many years, alongside discounts on additional products.
What changes in a migration
Moving from NPSP to Agentforce Nonprofit is a reimplementation in a new org, not an upgrade. Three changes drive most of the effort.
Person Accounts become mandatory
NPSP uses the Household Account model, with Contacts grouped under Accounts. Agentforce Nonprofit uses Person Accounts. Once Person Accounts are enabled in an org they cannot be turned off, so the decision needs to be made deliberately and tested in a sandbox first.
The gift model changes
In NPSP, a donation is an Opportunity. Agentforce Nonprofit introduces dedicated gift objects for transactions, commitments and designations. Every report, dashboard, Flow and integration that reads Opportunities as gifts has to be remapped, including payment processors and online giving tools. This is where migration estimates most often go wrong.
Programs and case management move to native objects
If you use the Program Management Module or case management packages, those processes map to Agentforce Nonprofit's built-in program, benefit and case objects. That is often an improvement, but it is still a redesign.
When migrating makes sense
- Your NPSP org has years of customization and technical debt, and you were going to rebuild anyway.
- You need program and outcome management, case management or grantmaking in the same platform as fundraising.
- You want Salesforce's AI agents and Data 360 features, which are being built for the new data model.
- You are implementing Salesforce for the first time. In that case, start on Agentforce Nonprofit.
When staying on NPSP makes sense
- Your org works, staff trust the data and your reporting is stable.
- Your budget this year is better spent on data quality, training or reporting.
- You depend on AppExchange packages or integrations that have not been updated for the new gift model.
Staying is a legitimate choice. Anyone selling you a migration against a deadline is selling a deadline Salesforce has not published.
How to prepare either way
Whether you migrate next year or in five, the same work lowers the cost and risk later:
- Clean duplicates and inactive records now. Every bad record migrated is paid for twice.
- Document your custom fields, Flows, Apex and integrations, and mark which ones are still used.
- Inventory every report and dashboard that reads Opportunities as gifts.
- Ask your payment, email and event vendors about their Agentforce Nonprofit support.
- Agree on definitions for donors, members and households with development, programs and finance.
A practical migration sequence
| Phase | What happens |
|---|---|
| Assessment | Org audit, process interviews and a go or wait recommendation |
| Design | Target data model, Person Account and gift mapping, integration plan |
| Build | New org configuration, automation and security, built in sandboxes |
| Migration | Test loads reconciled to NPSP totals, then a cutover load |
| Go-live | Training, parallel reporting period, NPSP org retired on a set date |
How we can help
We run NPSP org assessments that end in a written recommendation: migrate now, migrate later, or stay. If you migrate, the same senior team designs and runs it. See our Salesforce consulting services or book the free health check below.