NPSP
A managed package added on top of standard Sales Cloud objects. Extending or maintaining it generally requires NPSP-aware developers who understand the package's own data model and automation.
NPSP remains fully supported, but new Salesforce nonprofit investment is now Nonprofit Cloud-first. AX3 assesses your NPSP environment and builds a migration path when it genuinely makes sense, not before.
NPSP is not being retired and continues to be supported, so no organization is being forced to move. What has changed is where Salesforce is investing: new nonprofit feature development is going into Nonprofit Cloud. AX3 treats migration as a decision to be evaluated on your circumstances — the cost of maintaining custom NPSP work, the capability you need next, and whether your current setup is holding anything back.
A managed package added on top of standard Sales Cloud objects. Extending or maintaining it generally requires NPSP-aware developers who understand the package's own data model and automation.
Fundraising, program management, grantmaking and case management built natively into the Salesforce core, with Agentforce AI capabilities designed nonprofit-first rather than retrofitted.
NPSP is not being deprecated and is not losing support. What has changed is where new feature development is concentrated: Nonprofit Cloud is where Salesforce is investing going forward.
Audit the current NPSP configuration, customizations, integrations and data model, and document what is genuinely in use.
Honest guidance on whether migration timing makes sense now or later, with the reasoning and trade-offs written down.
Phased data migration and reconfiguration onto Nonprofit Cloud's native objects, preserving what is already working.
Layer in Agentforce Nonprofit AI capabilities once the core migration is stable and adopted.
Fundraising, program management, grantmaking, volunteer management and Agentforce for Nonprofit, module by module.
See the full Nonprofit Cloud overview →There is no deadline forcing a move, so the right year depends on your organization rather than the calendar. Migration is usually worth evaluating when custom NPSP development is becoming costly to maintain, when you want Agentforce nonprofit capabilities, or when fundraising, programs and grants sit in disconnected systems. If NPSP is stable, lightly customized and meeting your needs, waiting is a reasonable decision.
NPSP is a managed package layered on standard Sales Cloud objects, so extending it typically needs NPSP-aware developers. Nonprofit Cloud builds fundraising, program management, grantmaking and case management natively into the Salesforce core, with Agentforce AI designed nonprofit-first. Both are supported, but new Salesforce nonprofit feature development is focused on Nonprofit Cloud.
Customizations do not transfer automatically, because the two products use different underlying data models. Configuration, automation and reports are mapped to Nonprofit Cloud equivalents during migration, and some custom work is rebuilt natively or retired if the platform now covers it. AX3 documents this mapping during assessment so you know what is rebuilt, what carries over and what is dropped before any work starts.
No. NPSP remains fully supported and there is no obligation to move on a fixed timetable. Many organizations reasonably stay on NPSP until a specific need arises, such as new AI capability, grantmaking, or the cost of maintaining custom development.
Yes. AX3 works with eligible 501(c)(3) organizations holding Salesforce's Power of Us donated licenses as well as those on paid nonprofit licensing. Licensing entitlements are confirmed with Salesforce directly, and the migration plan is scoped around the licences your organization actually holds.