Nonprofit systems

Do we have to migrate from NPSP? A plain answer for 2026

Do you have to migrate from NPSP? No deadline yet. What Salesforce has said, signs it is time to move, and how to plan an NPSP to Nonprofit Cloud migration.

Two parallel paths of tiles, one older and one newly laid, with a few tiles crossing from the first to the second.

No, you do not have to migrate from NPSP today. Salesforce has not published a date by which existing customers must leave, and it says NPSP will continue to be supported. But the new tools Salesforce has announced for nonprofits are part of Agentforce Nonprofit, formerly Nonprofit Cloud, so an NPSP to Nonprofit Cloud migration is a question of when and how, and it deserves a plan rather than a panic.

The question usually comes from a small development team. Gifts, grants and the annual appeal run on the Nonprofit Success Pack, and it works, but the team keeps hearing that NPSP is going away and wants an answer before the board asks. Below is what Salesforce has actually said, and how to tell when moving is worth the work.

What Salesforce has said about NPSP

Three official statements matter, and none of them sets a deadline.

On its managed packages page, Salesforce says NPSP is used by thousands of organizations and “will continue to be supported.” For new customers of its Program Management Module and Outbound Funds packages, the same page recommends Nonprofit Cloud instead.

In December 2025, Salesforce announced Agentforce Nonprofit, describing it as formerly Nonprofit Cloud, with new AI agents for fundraising, programs, volunteers and donor support. Those agents are part of Agentforce Nonprofit, not NPSP. Salesforce’s own Trailhead material now uses the new name too, and notes that since December 2025 NPSP is no longer offered as a preconfigured package in production orgs.

The Power of Us program, which donates 10 Enterprise Edition licenses to eligible nonprofits, now has approved organizations choose between 10 Agentforce Nonprofit licenses and 10 Sales and Service licenses, according to Salesforce’s help article on the program. If you already run NPSP, nothing in these pages says your org stops working.

In practice, an NPSP org keeps running as it does today. The SI (super intelligence) agents Salesforce announced and the new fundraising objects are part of the other product.

Why an NPSP migration is a rebuild, not an upgrade

Many teams expect an upgrade button. There is not one. NPSP is a managed package installed on top of Salesforce. Agentforce Nonprofit is built into the platform with its own data model.

The differences are not cosmetic. In NPSP, a donation is an Opportunity record, recurring gifts live in Recurring Donations, and households follow NPSP’s household account model. Agentforce Nonprofit uses its own fundraising objects, such as Gift Transaction, Gift Commitment and Gift Commitment Schedule. Anything that touches a gift, from the board dashboard to the payment processor sync, needs a decision on whether it moves, gets rebuilt or goes away.

That is a data migration project, with the same risks as moving off any legacy CRM: every record has to be checked against the source before cutover, not after. A donor database deserves that care, because gift history feeds receipts, audits and grant reports.

Signs it is time to plan your NPSP to Nonprofit Cloud migration

Many nonprofits do not need to rush, and some should not move for a while. Use these signals to decide which camp you are in.

SignalWhat it suggests
NPSP runs well, data is clean, reports are trustedStay for now and review once a year
A key AppExchange tool or payment processor stops supporting NPSPStart planning
You need program, case or outcome tracking that add-ons cannot handleStart planning
Your org has years of custom code nobody understandsClean up first, then plan
You are already replacing a major system, such as finance or email marketingPlan both together
Year-end giving or an audit is in the next three monthsWait until it passes

The two “Start planning” rows are the real triggers. If a vendor you depend on announces it will only build for Agentforce Nonprofit, or if your programs team keeps tracking clients in spreadsheets because NPSP was never meant for case management, the cost of staying starts to rise.

How to stay well on NPSP in the meantime

Staying is a fine choice if you keep the org healthy. Four habits can make a later move cheaper.

Clean your data now. Merge duplicate contacts, close stale open pledges, and fix households that list the wrong people. Back up before any mass change; our guide to Salesforce backup and restore options covers what is included at no extra cost. Every bad record you fix today is one you will not have to map later.

Document what you have built. List custom fields, Flows, Apex classes and the integrations that write gifts, with who owns each. If your admin leaves, our guide to what to do when your Salesforce admin quits covers the handover, and this list is the core of it.

Retire what nobody uses. Old fields and reports add mapping work and confuse new staff.

Ask your key vendors, in writing, how long they will support NPSP. Their answers may set your real timeline.

Timing the move around your giving calendar

For most nonprofits across Nebraska, Iowa, Kansas and Colorado, the calendar decides more than the technology. Year-end giving, the January receipt run, the audit and grant reporting all lean on the donor database. A food bank or a land trust should not be cutting over to a new data model in December.

Plan the build for the quieter months, run the old and new systems side by side for at least one full reporting cycle, and reconcile gift totals before you switch off NPSP. Small teams, often one part time admin and a development director who also writes grants, need training time built into the plan, not squeezed in after go live.

If you want an outside view of whether to stay or move, our diagnostic can put a cost on both paths before you commit to either.

Common questions

Is NPSP being retired?

Salesforce has not announced a retirement date. Its managed packages page says NPSP will continue to be supported, while new features go into Agentforce Nonprofit.

Is Agentforce Nonprofit the same as Nonprofit Cloud?

Yes. Salesforce describes Agentforce Nonprofit as formerly Nonprofit Cloud. Older articles, job posts and partner pages still use the old name, and much of the AI work Salesforce announced for nonprofits is tied to the new one.

Can we upgrade NPSP to Nonprofit Cloud in place?

Not as a simple upgrade. The two use different data models, so the move means mapping and migrating your data and rebuilding reports, automation and integrations.