# Life After NPSP: Your Options When Salesforce NPSP No Longer Fits

By EvolveFundraising editorial team

Published: 2026-10-27

Updated: 2026-10-27

Category: Software migration

Canonical: https://getevolvefundraising.com/blog/npsp-alternatives

## Summary

If you run Salesforce's Nonprofit Success Pack (NPSP), you have three realistic options: stay on NPSP for now, re-implement on Salesforce Nonprofit Cloud, or move to a purpose-built fundraising platform. NPSP remains supported with no announced end-of-life, but Salesforce's new nonprofit features are going into Nonprofit Cloud. Because moving from NPSP to Nonprofit Cloud is a re-implementation rather than an upgrade, many organizations are using this moment to compare all three paths.

## Key takeaways

- Compare staying, re-implementing and switching as distinct choices.
- Map the data model and integrations before moving.
- Confirm current vendor guidance before making a decision.

If you run Salesforce's Nonprofit Success Pack (NPSP), you have three realistic options: stay on NPSP for now, re-implement on Salesforce Nonprofit Cloud, or move to a purpose-built fundraising platform. NPSP remains supported with no announced end-of-life, but Salesforce's new nonprofit features are going into Nonprofit Cloud. Because moving from NPSP to Nonprofit Cloud is a re-implementation rather than an upgrade, many organizations are using this moment to compare all three paths.

## What is happening with NPSP?

Salesforce introduced Nonprofit Cloud (NPC) as its long-term nonprofit product. According to [Salesforce Ben](https://www.salesforceben.com/salesforce-nonprofit-success-pack-to-nonprofit-cloud-migration/), NPSP is still supported with no immediate end-of-life, while Salesforce invests in NPC for future innovation.

The catch is the data model. NPC uses Person Accounts and a different gift model (gift transactions and gift commitments instead of opportunities and NPSP recurring donations). [MagicFuse](https://magicfuse.co/blog/salesforce-nonprofit-cloud-vs-npsp) notes that because Person Accounts and NPSP can't coexist in one org, migration often means standing up a new org. Customizations, automations and integrations must be rebuilt.

## Option 1: Stay on NPSP for now

**Good fit if** your NPSP org is stable, lightly customized, well administered, and meets your needs today.

**Watch for:** fewer new features over time, dependence on a shrinking pool of NPSP-specific expertise, and integrations that move their attention to NPC.

**Plan:** Set a review date. Staying is a decision to revisit in 12–18 months, not a permanent answer.

## Option 2: Re-implement on Salesforce Nonprofit Cloud

**Good fit if** you are committed to Salesforce, have in-house admin or developer capacity or a trusted partner, and need the platform's extensibility for programs, case management or complex integrations.

**Watch for:** project scope. You'll remap households to Person Accounts, opportunities to gift transactions, recurring donations to gift commitments, and rebuild flows, reports and integrations. Budget for partner fees, licenses beyond the [Power of Us](https://www.salesforce.org/power-of-us/) grant and ongoing administration.

## Option 3: Move to a purpose-built fundraising platform

**Good fit if** you don't have a dedicated Salesforce admin, your NPSP org has become fragile or expensive to maintain, or you're running fundraising alongside membership, events and accounting in other tools.

**Watch for:** the platform's ability to handle the NPSP concepts you rely on (households, soft credits, recurring gifts, pledges, campaign hierarchy) and the quality of its import tools.

## Comparing the three options

| Factor | Stay on NPSP | Move to Nonprofit Cloud | Purpose-built platform |
| --- | --- | --- | --- |
| Migration effort | None now | High (re-implementation) | Medium (data migration) |
| Admin skills needed | Salesforce admin | Salesforce admin, often developer | Fundraising staff |
| New features | Limited | Ongoing | Ongoing |
| Customization | High | High | Moderate, configured |
| Membership, events, accounting | Add-ons or other systems | Add-ons or other systems | Depends on platform |
| Total cost drivers | Admin time, apps | Partner fees, licenses, admin | Subscription, migration |

## How to decide: five questions

1. Do we have a Salesforce admin today, and will we in two years?
2. How many custom objects, flows and integrations does our org depend on?
3. What did we spend on Salesforce partners and apps in the last 24 months?
4. Which systems outside Salesforce hold donor-related data (membership, events, accounting)?
5. What would we do with the admin time saved by a simpler system?

## Migrating from NPSP: what to map

| NPSP object | Typical destination in a fundraising platform |
| --- | --- |
| Contacts and Household Accounts | Contacts and household records |
| Organization Accounts and Affiliations | Organizations and employer relationships |
| Opportunities (donations) | Gifts |
| Payments | Gift payments and installments |
| Recurring Donations | Recurring schedules plus payment tokens |
| Partial and Account Soft Credits | Soft credits |
| GAU Allocations | Fund designations and splits |
| Campaigns and campaign members | Campaigns, appeals and packages |
| Engagement Plans and Levels | Journeys and donor levels |

## Why associations on NPSP look at Evolve Fundraising

Many associations built NPSP into a home-grown association system, adding membership, events and dues through custom objects and apps. Evolve Fundraising runs on the Evolved Systems platform alongside a complete association management system, so membership, events, fundraising and a real general ledger are native, not custom. It covers the NPSP concepts above, imports historical data with AI-assisted mapping and doesn't require a dedicated Salesforce administrator.

## Frequently asked questions

### Is Salesforce NPSP being discontinued?

Not as of late 2026. NPSP is still supported, but Salesforce's new nonprofit features are being built in Nonprofit Cloud.

### Is moving from NPSP to Nonprofit Cloud an upgrade?

No. It's a re-implementation with a different data model, often in a new Salesforce org.

### What are the alternatives to NPSP?

Staying on NPSP, re-implementing on Nonprofit Cloud, or moving to a purpose-built fundraising platform.

### How long does an NPSP migration take?

Usually three to six months, depending on customization, integrations and data volume.

### Do we need a Salesforce partner to leave NPSP?

Not if you move to a platform whose vendor runs the migration. You will need someone who understands your NPSP data model to help map it.

**Weighing your post-NPSP options?** Talk to the Evolve team: [Request information from EvolveFundraising](https://getevolvefundraising.com/request-information).

*Salesforce, Nonprofit Success Pack and Nonprofit Cloud are trademarks of Salesforce, Inc. Evolved Systems is not affiliated with Salesforce. Status checked October 2026; confirm current Salesforce guidance before publishing.*

## Sources and further reading

1. [Salesforce Ben](https://www.salesforceben.com/salesforce-nonprofit-success-pack-to-nonprofit-cloud-migration/) — salesforceben.com
2. [MagicFuse](https://magicfuse.co/blog/salesforce-nonprofit-cloud-vs-npsp) — magicfuse.co
3. [Power of Us](https://www.salesforce.org/power-of-us/) — salesforce.org

## Related reading

- [Fundraising Software Migration: The Complete Guide for Nonprofits and Associations](https://getevolvefundraising.com/blog/fundraising-software-migration-guide)
- [Why Associations Should Run Fundraising Inside Their AMS](https://getevolvefundraising.com/blog/ams-fundraising-software)
- [The Real Cost of Switching Fundraising Software, and How to Build the Business Case](https://getevolvefundraising.com/blog/fundraising-software-switching-cost)
- [Discuss your fundraising goals with the Evolve team](https://getevolvefundraising.com/request-information)

## Discovery

[All articles](https://getevolvefundraising.com/blog) · [RSS feed](https://getevolvefundraising.com/rss.xml) · [Site guide](https://getevolvefundraising.com/llms.txt)
