Moving from the Nonprofit Success Pack to Salesforce Nonprofit Cloud is a data model change, not an upgrade button. NPSP is a managed package on standard objects; Nonprofit Cloud uses native platform objects for giving, programs, grants and cases. A migration therefore means redesigning the model, mapping and moving historical data, and rebuilding reporting and automation on the new foundation.
Inventory the current NPSP org — objects, managed package customizations, integrations, reports, automation and data quality. The output is a clear picture of what maps directly to Nonprofit Cloud, what needs redesign and what should be retired.
Design the target Nonprofit Cloud data model for giving, programs, grants and cases, then agree the migration approach: what moves, what is rebuilt natively, and how historical data is treated.
Build and configure in a sandbox, migrate data in test cycles, rebuild reporting, and run user acceptance testing with the teams who work in the system daily before any production cutover.
Cut over, support hypercare, then extend into the capability that motivated the move — unified impact reporting, grantmaking, portals, Data 360 or Agentforce automation.
No two NPSP orgs are alike, so AX3 assesses before estimating. These are the factors that most often move a migration from straightforward to complex.
It is the move from the Nonprofit Success Pack, a managed package layered on standard Salesforce objects, to Nonprofit Cloud, which uses native platform objects for giving, programs, grants and cases. Because the underlying data models differ, this is a redesign and data migration rather than an in-place upgrade.
There is no need to migrate on a fixed timetable, and NPSP orgs continue to run. Most organizations decide based on need rather than urgency — a move makes sense when new program, grant or reporting capability is on the roadmap and rebuilding it twice would be wasteful.
Timelines depend on customization depth, data volume and integration count, so AX3 confirms a range during assessment rather than quoting a generic figure. The assessment phase itself is short and produces the scope, sequencing and effort estimate you need to plan.
Historical giving, contact and campaign data is mapped to the Nonprofit Cloud model and migrated in test cycles before production cutover, with reconciliation against source totals. Where a legacy structure has no clean equivalent, the treatment is agreed with you rather than decided silently.
Yes, and phasing is common where fundraising must keep running uninterrupted. A typical approach establishes the Nonprofit Cloud foundation and core giving processes first, then adds program, grant or portal capability in later releases.
Start with an assessment of your current org, then decide on timing with real scope in hand.