Migrate from NPSP now if your instance is heavily customized, hard to maintain, or you're working around missing program and case management — every year you wait makes the eventual migration bigger. Wait if NPSP runs your fundraising cleanly and a mission-critical integration doesn't yet support Nonprofit Cloud. For most organizations this is a when, not a whether — NPSP is not going away, but the platform is being built on NPC.
Here's how to place yourself on that spectrum without guessing.
Migrate sooner if…
- Your NPSP org is heavily customized and painful to maintain. You're already paying a migration's price in admin drag and workarounds; migrating converts that recurring cost into a one-time project.
- You track programs, cases or grants in spreadsheets next to Salesforce. Nonprofit Cloud covers those natively — you'd be replacing duct tape, not just moving data.
- You want Salesforce's AI and Data Cloud features. They're built for Nonprofit Cloud's architecture and are not coming to NPSP.
- You're launching a new Salesforce org anyway. Start on NPC directly — there's no legacy to unwind.
Wait if…
- NPSP runs smoothly and covers everything you need. A working system has real value, and there's no deadline forcing your hand.
- A critical app or payment processor doesn't support NPC yet. Verify this app by app — vendor support has broadened a lot since 2023, so re-check rather than assume.
- You're mid-campaign or mid-fiscal-year with no capacity. Timing a migration into a quiet season is legitimate. Just set the date; don't leave it open-ended.
The cost of waiting
"No deadline" is the most misread fact in this whole topic. There's no cliff — but there is a slow, compounding cost:
- Every new custom field and workaround you add to NPSP is more to migrate later.
- Every quarter, the feature gap with the platform widens (AI, Data Cloud, native program management).
- The pool of consultants deeply fluent in NPSP shrinks as the ecosystem shifts to NPC.
Waiting is a valid choice. Waiting without a plan is how a $20,000 migration becomes a $60,000 one.
A simple way to score it
| Signal | Points toward |
|---|---|
| Heavy customization / hard to maintain | Migrate |
| Programs/cases/grants in spreadsheets | Migrate |
| Want AI / Data Cloud | Migrate |
| Everything works, no gaps | Wait |
| Critical app not NPC-ready | Wait |
| No team capacity this quarter | Wait (but set a date) |
If you're landing on "migrate," the readiness checklist tells you how prepared you are, and the readiness check tool gives you an objective now/soon/later verdict in six questions. When you want a human to sanity-check it, that's what our Salesforce consulting team does.
Frequently asked questions
Should we migrate from NPSP now or wait?
Migrate sooner if your NPSP org is heavily customized and hard to maintain, you track programs or cases in spreadsheets, or you want Salesforce's AI and Data Cloud features. Wait if NPSP runs smoothly, covers your needs, and a mission-critical app doesn't yet support Nonprofit Cloud. For most organizations it's a question of when, not whether.
Is there a deadline to migrate from NPSP?
No. Salesforce has announced no end-of-life date for NPSP. But 'no deadline' isn't 'no reason to plan' — the feature gap widens each quarter and every customization you add grows the eventual migration, so the cost of waiting compounds even without a cutoff.
What is the cost of waiting to migrate?
There's no cliff, but a slow, compounding cost: each new custom field and workaround is more to migrate later, the platform feature gap (AI, Data Cloud, native program management) widens, and the pool of NPSP-fluent consultants shrinks. Waiting without a plan is how a $20,000 migration becomes a $60,000 one.
Yash
Founder & Principal Consultant, Ynexgen
Yash leads Ynexgen, helping small and mid-sized businesses turn technology into a stronger foundation for growth — 7+ years across Salesforce CRM, websites, and AI adoption.
