Salesforce Nonprofit Cloud Implementation and Migration

If you run a nonprofit on Salesforce and you’ve searched anything about “Nonprofit Cloud” in the last few months, you’ve probably landed on an agency page telling you the clock is ticking. NPSP is being retired, they say. You need to migrate now, before support runs out. Book a call today.

None of that is true, and it’s worth saying plainly: there is no announced end-of-life date for the Nonprofit Success Pack, and there is no end-of-sale date either. Salesforce has not told a single nonprofit that their NPSP org will stop working on a specific day. What actually happened is narrower, and once you understand it, the migration decision gets a lot less urgent and a lot more strategic.

What Salesforce actually announced

In March 2023, Salesforce stopped adding new features to its managed-package nonprofit products, NPSP included. That was the beginning of what was then called Nonprofit Cloud, a ground-up rebuild on Salesforce’s core platform rather than a managed package layered on top of it. In 2026, that product was folded into Salesforce’s Agentforce branding and renamed Agentforce Nonprofit, the umbrella term you’ll now see on Salesforce’s own site and help documentation.

So the accurate timeline is: NPSP stopped getting new features in 2023, and the replacement product has been renamed twice since (Nonprofit Cloud, then Agentforce Nonprofit). At no point in that sequence did Salesforce announce that existing NPSP orgs would lose support. NPSP remains fully supported today. It still receives security patches and bug fixes. Organizations running it are not on borrowed time.

That distinction matters, because “no new features” and “no more support” are two very different sentences, and a lot of the agencies competing for your migration budget are letting you conflate them.

The Power of Us program did change, though

Here’s the part that’s genuinely new, and it’s worth knowing even if you have no plans to migrate. Starting in December 2025, Salesforce changed what nonprofits get for free through the Power of Us program. Instead of the familiar 10 free NPSP licenses, approved organizations now choose between two bundles: 10 free Agentforce Nonprofit Enterprise Edition licenses, or 10 free Sales Cloud and Service Cloud Enterprise Edition licenses.

If you’re a brand-new nonprofit signing up for Power of Us today, you’re choosing a starting point, not being pushed off one. If you’re an existing NPSP organization, this change doesn’t touch your current licenses at all, it only affects what new or additional licenses look like going forward.

Why the household-to-Person-Accounts change is the real technical story

If there’s one part of this that deserves more attention than “is there a deadline,” it’s this: NPSP and Agentforce Nonprofit model your constituents completely differently, and that difference is why migrating is a project, not a settings toggle.

NPSP organizes individual donors as Contacts nested inside Household Accounts, the household is the giving unit, and rollups, soft credits and mailing preferences are all built around that structure. Agentforce Nonprofit uses Person Accounts instead, where an individual’s account and contact information live on a single record. These aren’t two versions of the same idea. They’re structurally incompatible, which means there’s no straightforward one-click conversion from one to the other.

In practice, a migration means rebuilding several pieces of your data model rather than copying it across. The household container itself goes away, so any household-level giving relationships have to be reconstructed using the new relationship and grouping tools. Soft credits, the attribution you give a spouse, an employer’s matching program, or someone who influenced a gift, run on different objects and different logic, so those rules need to be rebuilt, not just re-pointed. Relationship records carry over conceptually but behave differently under the new model, and every custom rollup you’ve built for giving totals, last-gift dates or largest-gift tracking needs to be recalculated under the new architecture, because the old rollup engine doesn’t apply anymore. Recurring donations add one more layer: NPSP’s Recurring Donation object becomes Gift Commitment in the new model, which is a different way of representing the same ongoing relationship.

None of this is a reason to be scared of migrating. It’s a reason to plan for real weeks of data mapping and testing rather than expecting a weekend cutover, and to pick a partner who will tell you that upfront instead of selling you urgency.

Four honest reasons to consider migrating

You’re hitting the ceiling of what a managed package can extend. If you’ve spent years layering custom code and third-party tools onto NPSP to make it do things it wasn’t built for, a platform-native rebuild removes that ceiling entirely.

You want the automation and AI tooling Salesforce is investing in. Agentforce Nonprofit is where Salesforce’s actual product investment is going now. If AI-assisted donor engagement, grant tracking or case management genuinely matters to your roadmap, that investment is landing on the new architecture, not the old one.

You’re already planning a new Salesforce implementation. If you’re standing up a fresh org anyway, after a merger, a major systems overhaul, or simply outgrowing your first build, there’s little reason to build it on a package Salesforce has stopped extending.

Your current build is small and clean enough that remapping is genuinely low-risk. Organizations with straightforward household structures, minimal customization and few integrations have the easiest path across. The complexity above scales with how much you’ve built, not with how long you’ve used NPSP.

Four honest reasons to stay put

Your org runs on years of custom logic you can’t easily rebuild. If soft credits, rollups and household relationships have been tuned for years to match exactly how your organization tracks giving, that institutional knowledge doesn’t transfer automatically. Rebuilding it takes real staff time, and staying on a stable, supported NPSP org can be the more responsible choice while that logic still works.

You don’t have the internal capacity for a multi-week project right now. A migration needs someone on your team who understands your data model well enough to validate the remapping. If that person doesn’t exist right now, migrating under pressure is how organizations end up with broken rollups nobody notices until year-end reporting.

Nothing is actually broken. NPSP is supported, it’s stable, and “no new features” only matters if you were actually waiting on new NPSP features. Plenty of organizations aren’t.

The cost of migrating hasn’t been weighed against the cost of staying. A migration is a project with a real price tag in either staff time or a partner’s fees. If nothing about your current setup is causing friction, that spend competes with every other priority your budget has this year, and it should be evaluated the same way.

The honest bottom line

There’s no deadline forcing your hand. What changed is that Salesforce stopped investing in NPSP’s feature set in 2023 and has since rebranded its replacement, most recently to Agentforce Nonprofit. New Power of Us signups get a different starting license bundle than they used to. Everything else, your live org, your support, your data, is exactly as stable as it was before any of these announcements.

If you’re evaluating a move, the right first question isn’t how soon you need to do this. It’s whether the Person Accounts model actually solves a problem you have. Get that answer honestly, and the deadline question stops mattering.

How the migration actually unfolds, step by step

Because Person Accounts and Household Accounts are structurally different, a real migration follows a sequence rather than a single cutover event. Most projects that go well follow roughly this order.

First comes a data audit: pulling a full inventory of every custom field, rollup, trigger and third-party integration touching Contacts, Households, Opportunities and Recurring Donations in the current org. This is where most timeline surprises get caught early instead of late. Second is building the target data model in a sandbox, standing up Person Accounts, rebuilding the relationship and grouping structures that replace Household Accounts, and re-creating soft-credit logic before a single real record moves. Third is a trial migration of a small, representative slice of data, checked field by field against the original records, specifically looking at rollup totals and relationship attributions, since these are where structural mismatches show up first. Fourth is validating recurring giving separately, because Recurring Donation to Gift Commitment isn’t a field rename, it changes how the ongoing relationship is represented, so payment schedules and dues need their own pass. Only after all of that checks out does the full migration run, followed by a parallel verification period where the team reconciles totals against the old org before decommissioning anything.

Organizations that skip the sandbox trial and migrate directly in production are the ones who end up with the horror stories, a major donor’s giving history fragmented across two records, or a rollup quietly reporting zero because the trigger it depended on no longer exists. None of that is a flaw in Agentforce Nonprofit. It’s what happens when a structural change gets treated like a settings update.

Common myths worth retiring

“NPSP will stop working on a set date.” False. No end-of-life or end-of-support date has been announced. NPSP is fully supported today.

“You have to migrate to keep using Salesforce for your nonprofit.” False. You can continue running NPSP indefinitely under current terms; migrating is a choice about where you want to invest, not a requirement to keep functioning.

“Migrating is basically an upgrade, like a version bump.” False, and this is the myth that causes the most damage. Household Accounts and Person Accounts are different data models. Every rollup, soft credit rule and relationship needs to be rebuilt and validated, not carried over automatically.

“Power of Us no longer supports existing NPSP nonprofits.” False. The December 2025 change affects what new license bundles look like for organizations applying or expanding now. It does not revoke or alter licenses already in use.

NPSP vs Salesforce Nonprofit Cloud: How the Data Model Differs

The clearest way to judge the move is to compare the objects your fundraising team relies on today with where they live in Nonprofit Cloud (now Agentforce Nonprofit). None of these map one to one, which is why a migration is a rebuild and not an upgrade.

Rollups, reports, dashboards, integrations with payment processors and any custom code that touches Opportunities all need to be rebuilt against the new objects. That is the work to scope before anyone commits to a date.

Where Nonprofit Cloud Connects to the Rest of Salesforce

Most nonprofits we work with need more than a donor database. Volunteer, donor and beneficiary portals are built on Salesforce Experience Cloud. Supporter journeys and appeals run through Salesforce Marketing Cloud, and organisations with many data sources use Salesforce Data Cloud to build a single supporter profile. Case management for programme services often sits on Service Cloud features.

Whether you stay on NPSP or move, the org needs an owner. Our Salesforce managed services cover release testing, admin support and small enhancements, and our Salesforce CRM implementation team handles the migration build itself. See the full range of Salesforce cloud services we deliver.

Quick answers

Is NPSP being discontinued? No. There is no announced end-of-life or end-of-sale date. NPSP remains supported, and organizations can continue running it.

What actually changed in 2023? Salesforce stopped adding new features to its nonprofit managed packages, including NPSP, and began building what was then called Nonprofit Cloud as a platform-native replacement.

Why was it renamed to Agentforce Nonprofit? In 2026, Salesforce folded the product into its broader Agentforce branding, which covers its AI agent tooling across the platform.

Does the Power of Us change affect my current licenses? No. It only changes what new license bundles look like for organizations applying or requesting more licenses after December 2025.

Is migration reversible if something goes wrong? Not cleanly. This is exactly why a sandbox trial and parallel verification period matter before any production cutover, treat it as a one-way data project, not a toggle you can flip back.