NPSP vs Agentforce Nonprofit in 2026: do Australian not-for-profits have to move?

If you have been told your not-for-profit must migrate off the Nonprofit Success Pack this year, start here: no, you do not have to. The NPSP vs Nonprofit Cloud question — more accurately NPSP vs Agentforce Nonprofit since Salesforce renamed the product in December 2025 — is a real strategic decision for Australian charities and community organisations. It is not an emergency, and it is not a deadline. Salesforce has published no retirement date and no end-of-life date for NPSP. Anyone selling you urgency against a deadline has invented that deadline.

The summary you can act on: NPSP is frozen, not dying. Feature development stopped in March 2023, but the product is still available and still supported. Move when you have a capability gap the new platform genuinely closes — program and case management, service delivery records, a longer runway on skills. Stay when NPSP is doing its job and the money is better spent elsewhere.

Where things actually stand in 2026

Three facts frame the whole decision.

Salesforce ended feature development on NPSP in March 2023. No new features are planned. The managed packages still work, still receive support, and still underpin thousands of fundraising operations worldwide.

Salesforce has never announced an NPSP retirement or end-of-life date. Not in 2023, not since. That is the honest answer to the search query, and it is worth repeating because it is routinely obscured in sales conversations.

What did change is the front door. Since December 2025, the Power of Us program no longer grants NPSP. Qualified nonprofits receive 10 Enterprise Edition licences and choose either Agentforce Nonprofit or Sales and Service Cloud. NPSP was never a licence in its own right — it is a set of managed packages installed on Sales Cloud licences — so the practical effect is that new Australian not-for-profits now start on the newer product by default. Existing NPSP orgs are unaffected by that change.

NPSP vs Nonprofit Cloud: the differences that matter

The critical point is that these are not two versions of the same thing. Agentforce Nonprofit is a different product built on a different data model. Side by side:

• Constituent model. NPSP uses Household Accounts with Contacts, plus the familiar account model workarounds. Agentforce Nonprofit uses Person Accounts. This is the single biggest structural difference and it ripples through everything downstream.
• How it is delivered. NPSP is managed packages layered onto Sales Cloud. Agentforce Nonprofit is native platform functionality, which is why new capability lands there and not in the packages.
• Program delivery. NPSP has no real program management. Agentforce Nonprofit ships Program Management with Program Enrollments, so participation in a service or program is a first-class record rather than a custom object someone built in 2019.
• Service records. Benefit Disbursements track what was actually delivered to whom. If you provide material aid, food relief, housing support or funded services, this is the gap NPSP never filled.
• Case and outcome tracking. Case Management and Outcome Management are built in. NPSP orgs typically achieve some of this with custom objects and reporting glue.
• Fundraising. NPSP’s fundraising model is mature and well understood. Agentforce Nonprofit’s equivalent is capable but different, and your recurring giving, soft credits and allocation logic will need rebuilding rather than porting.
• Roadmap. Everything new lands on Agentforce Nonprofit. NPSP receives support, not features.

Read that list as a capability comparison, not a quality judgement. A pure fundraising organisation with clean NPSP data may find nothing on the right-hand column it actually needs.

The real cost of moving

This is where honest advice separates from a licence pitch. Migration is a data project, not an upgrade button. There is no toggle, no in-place conversion, no “Salesforce will handle it”.

Data model rework. Moving Household Accounts and Contacts to Person Accounts is a genuine transformation, not a field mapping. Every custom object, every relationship, every automation built against the NPSP model has to be re-pointed or rebuilt. Donation history, recurring gifts, relationships and affiliations all need a considered landing place. Our NPSP data migration checklist covers the ground this consumes in practice.

Reporting and dashboards rebuilt from scratch. Reports do not migrate. Every board pack, every acquittal report, every grant return built on NPSP objects has to be reconstructed against the new model and then validated against the old numbers. Budget for the validation, not just the rebuild — the reconciliation conversation is usually where timelines slip.

Integrations and automation. Fundraising platforms, payment gateways, email tools, rostering and finance systems all touch the model you are about to change. Each one is a re-test, and some are a rewrite.

Retraining. Staff and volunteers who know where everything lives will not recognise the new screens. Frontline workers in community services are not full-time system users, and the change cost lands hardest on them. Under-resourcing training is the most common way a technically successful migration is judged a failure.

Money and time. Migrations of this type are costed like data projects, and the drivers are data volume, customisation depth and integration count. Our note on what Salesforce data migration costs in Australia explains how to size it honestly before you commit.

Stay on NPSP if

• Your org is fundraising-led and NPSP already does what you need.
• Your data is clean, your reporting works and your team is fluent in it.
• You have no program, case or service-delivery requirement that NPSP is failing.
• Your budget for the next eighteen months has a higher-value home — donor experience, data quality, a broken integration, a genuine capability gap.
• You are mid-way through another significant change. Do not stack two transformations.
• The only argument you have been given for moving is a deadline. There is no deadline.

Staying is a legitimate, defensible position. NPSP will keep working. The risk you accept is a slowly widening capability gap and an ecosystem whose skills are drifting elsewhere — real, but gradual, and manageable with a deliberate review date rather than a panic.

Move if

• You deliver programs or services and need Program Enrollments, Benefit Disbursements, Case Management or Outcome Management. This is the strongest reason by a distance.
• You are already carrying heavy custom objects that duplicate what the new platform provides natively.
• You are consolidating multiple orgs or replacing an ageing case management system anyway, so the data work is happening regardless.
• Agentforce capability is on your genuine roadmap and you want the native foundation under it.
• Your NPSP org has accumulated a decade of technical debt and a rebuild is warranted on its own merits. Migration then becomes the vehicle for work you needed to do.
• You are a new organisation. The Power of Us change has effectively made this decision for you.

Two signals worth reading correctly

Salesforce is retiring the Nonprofit Success Pack Consultant certification on 1 February 2027, along with 23 others, with the last exam sitting on 31 August 2026. That is a directional signal about where ecosystem skills are heading. It is not a product deadline and should not be presented to your board as one, though it does bear on partner availability over time.

Winter ‘27, with production waves on 4 September, 2 October and 9 October 2026, added guided setup in Salesforce Go for Program, Case and Outcome Management, plus household naming formulas. Note where those features landed: Agentforce Nonprofit, not NPSP. Some require specific editions and an add-on, so check the fine print before you build a case on them. We have written up the detail in our Winter ‘27 nonprofit release note.

What this looks like in practice

We have completed one NPSP to Nonprofit Cloud migration for an Australian community-care provider, delivered alongside the implementation partner. The lesson from it was not technical. The data model conversion was demanding but tractable; what needed the most care was reporting continuity and the retraining of staff who use the system between client visits rather than at a desk. That work is documented in our NPSP to Nonprofit Cloud migration case study.

If someone has quoted you a migration against a deadline, ask them to show you where Salesforce published it. Then decide on the merits: capability you need, cost you can justify, timing you control.

We are happy to give you a straight read on whether your NPSP org should move, stay, or simply be tidied up — including when the honest answer is “not yet”. Get in touch and we will tell you what we would do in your position.