Salesforce NPSP vs Agentforce Nonprofit: What Australian Charities Need to Know
If you're running Salesforce for your nonprofit, you've probably heard the term Agentforce Nonprofit by now. And if you're on NPSP (Nonprofit Success Pack), you might be wondering: do we need to migrate? When? And what does it actually mean for our organisation?
These are the right questions to be asking. This article breaks down the key differences between NPSP and Agentforce Nonprofit and helps you think through whether a migration makes sense for your charity or NFP right now.
What is NPSP?
NPSP stands for Nonprofit Success Pack. It's a set of managed packages built on top of Salesforce's core platform, designed specifically for nonprofits. It introduced concepts like Households, Affiliations and the NPSP data model that many Australian nonprofits have been using for years.
NPSP has been the standard for nonprofit Salesforce implementations for a long time. It works well and many organisations have built sophisticated systems on top of it.
What is Agentforce Nonprofit?
Agentforce Nonprofit (previously known as Nonprofit Cloud) is Salesforce's next-generation product for the nonprofit sector. Unlike NPSP which sits on top of the core platform, Agentforce Nonprofit is built natively into Salesforce's platform architecture. This means it benefits from Salesforce's latest innovations including AI, automation and the full suite of Einstein features without the workarounds that NPSP sometimes requires.
Agentforce Nonprofit does not only cover Fundraising, it spans Case Management, Program Management, Outcome Management, plus Grantmaking. That breadth is the real drawcard for organisations delivering services as well as fundraising.
Salesforce is actively investing in Agentforce Nonprofit. NPSP will continue to be supported but it is not where new development is happening.
What are the key differences?
The differences between NPSP and Agentforce Nonprofit go deeper than just architecture. The entire data model has changed.
In NPSP, donor records are built around the Household Account model. In Agentforce Nonprofit, Person Accounts are used instead, bringing nonprofits more in line with how the rest of the Salesforce platform works.
The way giving is recorded has also changed significantly. In NPSP, every gift is an Opportunity with one or more Payment records, with General Accounting Units and GAU Allocations handling fund splitting. In Agentforce Nonprofit, Opportunities are reserved for high-touch giving like major gifts and grants that need stewardship. Recurring donations and pledges are handled by Gift Commitments, while actual payments received become Gift Transactions. GAUs become Gift Designations and soft credits, previously spread across three objects, are consolidated into a single Gift Soft Credit object.
Campaigns work differently too, with outreach source codes now used to drive performance measurement rather than the campaign model NPSP users will be familiar with.
For teams moving from NPSP, this means a genuine learning curve. The concepts are similar but the objects, fields and relationships are different enough that your processes and reports will need to be rebuilt rather than simply migrated.
Should your organisation migrate?
This is where it gets nuanced. Not every organisation should migrate to Agentforce Nonprofit right now. Here are some questions to help you think it through.
Are you hitting the ceiling of what NPSP can do? If your team is regularly frustrated by limitations in your current setup and you're building workarounds to achieve things that should be straightforward, that's a signal.
Are you about to invest significantly in your current system? If you're considering a major NPSP customisation or integration project, it might be worth pausing to evaluate whether that investment would be better placed in an Agentforce Nonprofit migration instead.
Do you have clean data and strong internal processes? A migration is only as good as the foundation you're migrating from. If your data is messy or your processes are unclear, fix those first.
Do you have leadership buy-in and an internal champion? A migration of this scale needs someone internally who owns it and can drive adoption across the team.
What does a migration actually involve?
Moving from NPSP to Agentforce Nonprofit is not a simple upgrade. It requires careful planning, data migration, configuration work and training. The timeline depends on the complexity of your current setup, how customised your NPSP instance is and the quality of your existing data.
A good implementation partner will help you assess your readiness, scope the migration clearly and manage the process so your team can stay focused on your mission throughout.
Our recommendation
If you're a new organisation choosing Salesforce for the first time, choose Agentforce Nonprofit. If you're on NPSP and it's working well for you, don't migrate just because it's the newer product. Migrate when you have a clear reason to: you're hitting limitations, you're about to invest in a major new capability, or you have the organisational readiness to do it well.
Ready to talk through your options?
Clara Partners works with nonprofits and charities across Australia and New Zealand on both NPSP and Agentforce Nonprofit. If you're trying to figure out where you sit and what makes sense for your organisation, we'd love to have an honest conversation.