Salesforce Nonprofit Success Pack: Is NPSP Dead?

Search for the Nonprofit Success Pack and you will read some version of the same sentence: Salesforce stopped innovating on NPSP in March 2023, and the sector should migrate. The sentence is accurate about intent and misleading about what is actually happening to the software.

NPSP is not a product with a licence. It is a suite of six managed packages installed on top of Sales Cloud licences, and its source is public. That means the question of whether it is still being maintained does not have to be taken on anyone’s word.

The release history, counted

We counted tagged production releases in the Salesforce Foundation’s public NPSP repository. Beta tags excluded, only the rel/ tags that ship to installed orgs.

Eleven production releases across 2024, 2025 and 2026 to date. The most recent is 3.238 on 10 August 2026, with repository activity as recently as 24 August. The repository is not archived.

So the widely repeated claim needs splitting in two. Feature development did stop: nothing meaningful has been added since 2023, and nothing is planned. Maintenance did not stop. Releases fell roughly 80% from the 2021 peak and settled at about five a year, which is what a package in support rather than development looks like.

That distinction matters because the two possible worries are different. “Will it break when Salesforce ships a platform release” is answered by the maintenance cadence, and the answer is currently reassuring. “Will it get the thing I need next year” is answered by the development status, and the answer is no.

What actually changed for new nonprofits

This is the change that gets reported as NPSP being withdrawn, and it is worth stating precisely.

Organizations approved through the Power of Us programme now receive ten donated Enterprise Edition licences, choosing between Agentforce Nonprofit and Sales and Service Cloud. There is no such thing as an NPSP licence, because NPSP was never licensed separately. An organization that takes the Sales and Service Cloud bundle can still install NPSP on top of it.

So NPSP has not been taken away from new nonprofits. It has been taken out of the default path, which in practice means most new organizations will never encounter it.

The naming, decoded

Three names for essentially one product line in three years is itself a fact worth weighing. It makes documentation, community answers and consultant quotes difficult to date, and a search result from 2024 may describe the same software under a name that no longer appears anywhere in your org.

What NPSP actually is

Understanding the status is easier once you know the shape of the thing. NPSP is not an application. It is six managed packages that install into a standard Salesforce org and reshape it for fundraising: a household account model, a donation and opportunity structure, recurring donations, relationships between contacts, allocations to funds and campaigns, and a set of automation and rollup fields that keep donor totals current.

Because it sits on top of Sales Cloud rather than replacing it, an NPSP org is a Salesforce org. Reports, flows, permissions and the API all behave normally. That is why the maintenance question is narrower than it first appears: what the release cadence has to keep up with is compatibility with three Salesforce platform releases a year, not a whole product roadmap.

It is also why the community around it matters. A decade of documentation, forum answers and consultant experience is attached to this data model, and that body of knowledge does not transfer to the native product.

Should you migrate

There is no deadline, no forced migration and no announced end of life. Anyone presenting this as urgent is selling migration services, and migration off NPSP is a data model change rather than an upgrade. Accounts, contacts, households, opportunities and recurring donations do not map one to one.

The case for moving is forward-looking. Everything Salesforce builds for this sector now, including the AI features, is being built on Agentforce Nonprofit. If your roadmap depends on that, the migration is unavoidable eventually and doing it deliberately beats doing it under pressure.

The case for staying is that a working NPSP org is a working system with a live maintenance cadence, and a migration consumes budget and staff attention that most organizations would rather spend on almost anything else.

What a migration actually touches

If you do decide to move, three areas consume the budget, and none of them is the part people expect.

Historical giving data. The household model and the opportunity structure differ between the two products, so donation history has to be transformed rather than copied. Soft credits, matching gifts and tribute gifts are where transformations break, because they encode a relationship between records rather than a single value.

Recurring donations. These are live financial commitments with payment schedules attached, and they are the highest risk objects in the whole exercise. A migration that drops a schedule stops money arriving, and nobody notices until the month end reconciliation.

Integrations. Anything that writes into NPSP objects has to be rebuilt against the new model: your payment processor, your email platform, your events tool, any custom flow a previous consultant left behind. This list is usually longer than the organization thinks, and inventorying it is the first job rather than a later one.

What to ask a consultant

Ask them to state, without hedging, whether Salesforce has announced an end of life date for NPSP. The answer is no. A partner who implies otherwise is either out of date or creating urgency, and both are reasons to get a second quote.

Then ask what the migration does to your historical giving data, your recurring donation schedules and any integration that writes into NPSP objects. Those three are where migration budgets are actually consumed.

Ask for the inventory before the quote. A partner who can produce a written list of every integration, custom object and automation currently touching your NPSP data, and price against that list, is quoting from your org. A partner who prices from a tier or a headcount is quoting from a template, and the difference will appear later as change requests.

One last question, asked plainly: what happens if we do nothing for another year. A partner worth hiring will give you a straight answer, which is that very little happens, and will then explain what you give up by waiting. A partner who cannot say that is managing you rather than advising you.

Questions people ask

Is Salesforce NPSP being discontinued?

No. Salesforce has not announced an end of life or end of support date for the Nonprofit Success Pack, and it remains available and supported.

What ended is feature development. Salesforce stopped adding capability to NPSP in March 2023 when it launched Nonprofit Cloud, and nothing new is planned.

Maintenance continued. The public repository shows eleven production releases across 2024, 2025 and 2026, the most recent being 3.238 on 10 August 2026.

Treat urgency about migration as a sales signal rather than a deadline.

Is NPSP still being updated in 2026?

Yes, at a maintenance cadence rather than a development one.

Counting tagged production releases in the Salesforce Foundation's public repository: 22 in 2021, 12 in 2022, then 3 in 2023, 5 in 2024, 5 in 2025 and one so far in 2026. That last one is release 3.238, published 10 August 2026.

Releases have fallen roughly 80% from the peak and settled at about five a year. The repository is not archived and had commit activity in late August 2026.

That pattern answers whether NPSP will keep working through platform releases. It does not mean new capability is coming, because it is not.

What is the difference between NPSP and Agentforce Nonprofit?

NPSP is a suite of six managed packages installed on top of Sales Cloud licences, using a data model built up over more than a decade. Agentforce Nonprofit is a native product built on the Salesforce platform, launched in 2023 as Nonprofit Cloud and renamed since.

The practical difference is the data model. Households, opportunities, recurring donations and program management are structured differently, which is why moving between them is a migration rather than an upgrade.

Agentforce Nonprofit is where all new development goes, including the AI features. NPSP receives maintenance only.

Can new nonprofits still get NPSP?

Yes, indirectly, and this is the point most reporting gets wrong.

There is no NPSP licence, because NPSP was never licensed separately. It is a set of managed packages installed on Sales Cloud.

Organizations approved through the Power of Us programme now receive ten donated Enterprise Edition licences and choose between Agentforce Nonprofit and Sales and Service Cloud. An organization that takes the Sales and Service Cloud bundle can install NPSP on top of it.

So NPSP was removed from the default path rather than withdrawn. Whether a new organization should choose it is a separate question, and the answer is usually no.

Is there a deadline to migrate off NPSP?

No. Salesforce has announced no migration deadline and no end of life date, and existing NPSP organizations are not required to move.

Migration is a data model change, not a version upgrade. Accounts, contacts, households, opportunities and recurring donations do not map one to one, and any integration writing into NPSP objects has to be rebuilt.

If a consultant presents a deadline, ask them to name the date and cite the Salesforce announcement. There is not one.

Why do so many articles say NPSP development stopped in March 2023?

Because it did, in the sense they mean. Salesforce ended innovation on its nonprofit managed packages in March 2023 when Nonprofit Cloud launched, and has been consistent about that.

The confusion is that many readers hear "development stopped" as "updates stopped", and those are different claims. The repository has shipped eleven production releases since the start of 2024.

The accurate summary is that NPSP receives bug fixes and platform compatibility work but no new capability, and none is planned.

What is Agentforce 360 for Nonprofits?

An umbrella bundle name rather than a product you install.

The naming has moved three times in three years. Nonprofit Cloud launched in 2023, was renamed Agentforce Nonprofit, and Agentforce 360 for Nonprofits is the wider solution ecosystem around it.

This matters practically because it makes documentation and community answers hard to date. An article from 2024 may describe exactly the software you are evaluating under a name that appears nowhere in your org, and a consultant quote may use a fourth name again.

When comparing quotes, ask which specific licences and packages are included rather than accepting a bundle name.

Should we migrate from NPSP to Agentforce Nonprofit?

It depends on whether your roadmap needs anything new.

Stay if NPSP works and you have no new requirements. It is supported, it is maintained, and a migration consumes budget and attention you could spend elsewhere. Reassess once a year.

Move if you want the AI capability Salesforce is building, since none of it is coming to NPSP. Move now if you are already replatforming for another reason, because the data work is funded once.

If you are new to Salesforce, start on Agentforce Nonprofit. Starting on a package that receives no development needs a specific reason.

This is reference information, not legal or tax advice. Rules vary by state and change over time. For a decision that carries real consequences, check the current text at irs.gov or your state registry, and talk to a nonprofit attorney or CPA.