Agentforce Nonprofit vs NPSP: Which Should You Run in 2026?

If you run a nonprofit on Salesforce, the last year has produced a lot of noise and very little clear guidance. Nonprofit Cloud got a new name. The Power of Us Program changed what it hands out. Consultants started sending migration quotes. Meanwhile your Nonprofit Success Pack org keeps working fine, which makes the urgency hard to judge. This guide separates what Salesforce actually committed to from what the market is inferring, and gives you a decision you can defend to a board.

What actually changed, and when

Three separate things happened. They get blended together in most conversations, which is why the picture looks more alarming than it is.

Nonprofit Cloud was renamed Agentforce Nonprofit. Salesforce announced this in December 2025 and shipped purpose-built agents alongside it: a Prospect Research Agent, a Participant Management Agent, a Volunteer Capacity and Coverage Agent, and a Donor Support Agent. The underlying product did not get replaced. If you were evaluating Nonprofit Cloud, you are evaluating Agentforce Nonprofit. Same objects, same data model, new name and an AI layer on top.

The Power of Us Program changed what it provisions. From December 2025, the "10 free NPSP licenses" option went away. Approved organizations now receive 10 donated Agentforce Nonprofit CRM licenses plus 10 donated Agentforce Sales and Service CRM licenses. This is the change with real teeth, because it means every new nonprofit joining the Salesforce ecosystem starts on the modern platform. The ecosystem is going to shift underneath NPSP whether or not NPSP itself changes.

NPSP feature development ended earlier, and separately. Salesforce stopped building new features for its nonprofit managed packages when Nonprofit Cloud launched in 2023. That was a product strategy decision about managed packages in general, not a reaction to the rename. It is old news that many organizations are only hearing now.

Is NPSP dead? No. Here is its real status

This matters, so read it carefully and quote it to whoever is panicking.

As of this writing, Salesforce has not announced an end of life for the Nonprofit Success Pack. It has not announced an end of sale either. NPSP orgs continue to run, continue to be supported, and continue to receive the platform releases that everyone else gets, because NPSP sits on top of standard Salesforce.

What NPSP does not get is new capability. No new fundraising features, no new program management features, and no participation in the nonprofit AI work. The gap between the two products will widen every release, because one of them is where all the investment goes.

So the honest framing is not "migrate or die." It is closer to "you are on a platform that has stopped improving, in an ecosystem that is moving on." That is a real problem with a multi-year timeline, not a fire.

Be skeptical of any partner who quotes you a migration on the basis of a deadline. Ask them to name the deadline and cite it. They cannot, because there is not one.

Two different data models, side by side

The products are not two versions of the same schema. They model a constituent differently at the foundation, which is why migration is a real project rather than an upgrade.

Read that table as a migration scope estimate. Every row is a mapping exercise, a data load, and a set of reports to rebuild. The rows about designations, soft credits, and rollups are where projects overrun, because that is where finance has strong opinions and the numbers have to reconcile exactly.

For a field-level walk through the newer model, see our guide to the Agentforce Nonprofit data model.

The decision table

Find your situation. The recommendation is what we would tell a client with no other information.

Four good reasons to stay on NPSP for now

• It fits and you only fundraise. If your NPSP org handles gifts, recurring donations, and donor reporting, and nobody is asking for more, the newer model gives you no new capability you will use this year.
• Your team is at capacity. A migration needs your development director and your database person in workshops and testing. If they are already the bottleneck, adding a migration produces a bad migration.
• You are mid-campaign. Never cut over during a capital campaign or in the weeks around your year-end appeal. The reconciliation risk is not worth it.
• You have integrations you cannot afford to rebuild. Payment processors, email tools, and accounting connectors that write to Opportunity records need new plumbing. Count them before you budget.

Four good reasons to move now

• You are about to build something NPSP does not do. Program tracking, outcome measurement, grantmaking, and volunteer management all ship standard in Agentforce Nonprofit. Building them custom on NPSP means paying twice.
• Your funders want outcome data. The outcome objects exist for exactly this. Reproducing indicator definitions, performance periods, and results as custom objects is a serious build.
• Your NPSP org is already a mess. If you were going to pay for a cleanup anyway, do the cleanup as part of a move to the platform that has a future. A new org gives you a clean data model and a chance to leave old junk behind.
• You are replacing a legacy donor database. If you are leaving Raiser's Edge, Bloomerang, DonorPerfect, or a set of spreadsheets, you are doing a migration regardless. Migrate once, to the current platform.

What the move actually costs

We will not publish a single number, because the honest range is too wide to be useful. What we can give you is the shape of the cost, so you can spot a quote that has missed something.

• Data mapping and migration. Usually the largest line. Contacts and Households become Person Accounts and Party Relationship Groups. Opportunities and Payments become Gift Transactions. Recurring Donations become Gift Commitments and Schedules. Allocations become designations.
• Deduplication. Do it before the load. Loading duplicates into a new org just relocates the problem, and it is much harder to fix once gift history is attached.
• Rollup and report parity. Budget real time here. Your board pack and your year-end totals must match the old system to the cent, or nobody will trust the new org.
• Integration rework. Every system that reads or writes donation records needs to be repointed and retested.
• Customization triage. Go through the Apex, the flows, and the custom fields and sort them into port, replace with standard function, and delete. The third pile is usually bigger than people expect, and it is the pile that saves money.
• Training and change management. The screens change. Gift entry in particular looks different. Underfund this and adoption fails no matter how good the build is.

Our step-by-step approach is in how to migrate from NPSP to Agentforce Nonprofit, and the wider budget picture is in what Salesforce really costs a nonprofit.

How to decide in one week

You do not need a three-month evaluation. You need five answers written down.

1. List what you need in the next 18 months that NPSP cannot do. Be specific. "Better reporting" is not an answer. "Report attendance and job placement retention at 30, 90, and 180 days for eight grants" is.
2. Count your integrations. Every system that touches donation data. This number drives a large part of the cost.
3. Measure your data quality. How many duplicate constituents? How many gifts with no designation? You will pay to fix this in either scenario, so find out now.
4. Inventory your customizations and mark each one port, replace, or delete.
5. Name the window. Which eight weeks of the year could you cut over without touching a campaign or an audit? If the answer is none, that is your real constraint and it drives the timeline.

With those five answers, the decision usually makes itself. If item one is empty, wait. If item one is full, plan the project.

Frequently asked questions