Salesforce for Australian not-for-profits: licences, Power of Us and what changed in 2026

If you have looked at Salesforce for nonprofits in Australia in the last year, you have probably come away confused, and that is not your fault. The product you were told about in 2023 has a different name, the free program grants something different to what it used to, and the acronym half your sector still uses — NPSP — was never a licence in the first place. This piece is an orientation for an Australian not-for-profit leader or operations manager who needs to work out, in plain language, what Salesforce actually offers now and whether it is worth the effort.

The short version: the donated licences are real and genuinely valuable, but they are the beginning of the cost, not the whole of it. What you get free is software. What you pay for is making it fit your organisation and keeping it running.

What Salesforce for nonprofits in Australia actually includes now

Power of Us is Salesforce’s nonprofit program, and it is the route by which qualified not-for-profits get donated licences. The important change: since December 2025, Power of Us no longer grants NPSP. Qualified nonprofits can instead request one of two Enterprise Edition bundles:

• 10 Agentforce Nonprofit licences, or
• 10 Sales and Service Cloud licences.

Ten licences is a real starting position for a small to mid-sized organisation. It is also a ceiling you will hit sooner than you expect once you count case workers, fundraising staff, finance and the people who only need to look things up. Additional licences are purchased at nonprofit pricing, and that recurring line item belongs in your business case from day one rather than in year two’s budget shock.

The “NPSP licence” myth, cleared up

This one causes more confusion in board papers than anything else in the stack, so it is worth being precise.

There is no such thing as an NPSP licence. The Nonprofit Success Pack is a set of managed packages — free add-on software from Salesforce.org — that you install on top of Sales Cloud licences. It reshapes the standard Salesforce data model for fundraising: households, soft credits, recurring donations, relationships between people. The licences underneath were always Sales Cloud. NPSP was the layer on top.

Why this matters practically: when your finance team asks “what happens to our NPSP licences”, the honest answer is that you do not have any. You have Sales Cloud licences with a free package installed. Your entitlement, your renewal and your cost base all sit with the licences, not the package. Getting this straight changes how you read every vendor quote you receive.

What things are called now

Salesforce renamed Nonprofit Cloud to Agentforce Nonprofit in an announcement in December 2025, sitting under umbrella branding of Agentforce 360 for Nonprofits. The name signals an AI emphasis, but the underlying product is the same purpose-built nonprofit platform, and you do not have to use any AI features to get value from it.

Structurally, Agentforce Nonprofit is built differently to NPSP. Its core elements are:

• Person Accounts rather than NPSP’s household-and-contact arrangement
• Program Management with Program Enrollments, to record who is in which program
• Benefit Disbursements, for recording service delivery — meals, sessions, visits, vouchers
• Case Management
• Outcome Management, for tracking what actually changed for the people you serve

If your organisation delivers services rather than only raising money, that list should read as an improvement. NPSP was fundraising-shaped, and every service-delivery organisation running it has built custom objects to compensate. We have set out the practical differences in more detail in NPSP versus Agentforce Nonprofit.

If you are already on NPSP, is the sky falling?

No, and you should be sceptical of anyone who tells you otherwise to accelerate a sale.

The facts, stated plainly: NPSP feature development ended in March 2023. NPSP remains supported, and Salesforce has published no retirement date. So you are on a frozen but supported product. Nothing breaks next quarter.

What you are giving up is momentum. No new features, a shrinking pool of partners whose best people are working on the newer platform, and a growing gap between what your system does and what a purpose-built service-delivery platform does. That is a reason to plan a migration deliberately over a year or two, not a reason to panic-buy one this quarter.

Be clear-eyed that migration is a real project. Your data model changes shape — households to Person Accounts is not a field mapping exercise — and data migration is usually the single largest line item. We have written about what Salesforce data migration actually costs in Australia, and the NPSP to Nonprofit Cloud migration we completed for an Australian community-care provider delivering counselling, home visits and aged-care navigation is a realistic picture of the work involved. That one was done alongside the implementation partner, and the platform work was the straightforward part. Agreeing what a “program”, an “enrolment” and an “outcome” meant across three service lines was not.

”It is in the release” does not mean “you have it”

Worth understanding before you read a Salesforce release note and assume it applies to you.

The Winter ‘27 release, which reached production in waves on 4 September, 2 October and 9 October 2026, added guided setup in Salesforce Go for Program, Case and Outcome Management, plus formula-driven household names and greetings. Useful, sensible improvements.

But some of it requires the Enterprise, Unlimited or Developer edition of Agentforce Nonprofit or Agentforce Education, plus the Automatic Household Creation and Naming add-on. In other words, features announced in a release are gated by edition and add-on. Before you build a plan around something you saw in a release note or a webinar, confirm in writing that it is available on the specific edition and add-ons you actually hold.

Free licences are the start of the cost

This is the part the excitement tends to skip. The donated licences remove one cost. The costs that remain are:

• Implementation. Configuration, data model decisions, migrating your existing records, integrations with finance or rostering systems, testing. For an organisation of any complexity this is the largest single number.
• Admin capability. Someone has to own the system — user access, fields, reports, release readiness. Without this the platform decays within a year.
• Training and change. Case workers who do not trust the system will keep their own spreadsheets, and then you have two systems and no data.
• Ongoing support and licences beyond ten. Budget for both annually.

A useful sanity test: if the total of those four numbers is uncomfortable, the free licences have not made Salesforce cheap. They have made an enterprise platform reachable, which is a different thing.

Should a small not-for-profit use Salesforce at all?

Sometimes the honest answer is no. Salesforce rewards organisations that have genuine complexity — multiple programs, funder reporting obligations, case management across service lines, a real fundraising base — and punishes those that do not, because you carry the administrative weight of an enterprise platform without needing its capability.

Reasonable signals that it is the wrong fit today: fewer than roughly ten staff touching client or donor data, one straightforward service line, no one who can own system administration, and no budget for a partner. A well-chosen sector-specific product may serve you better and you should not feel talked out of that.

Reasonable signals that it is the right fit: you deliver government-funded programs with their own reporting and data obligations, you need to show outcomes rather than activity, you hold sensitive personal and health information that needs proper access control under the Privacy Act and the Australian Privacy Principles, and you are already maintaining several disconnected systems that do not reconcile.

What to ask a partner

Ask these before you sign anything:

• Which specific edition and add-ons does your proposal assume, and what does each feature you have demonstrated actually require?
• What is the data migration approach, who cleans the data, and who signs off that it came across correctly?
• How many Australian nonprofit implementations have you delivered on Agentforce Nonprofit specifically, not NPSP?
• What happens after go-live — what support, at what cost, for how long?
• How will you leave us able to run this ourselves, and what does handover include?
• Where does our personal and health information sit, and who can access it?

If a partner cannot answer the edition question precisely, or cannot describe how they will build your internal capability, keep looking. Our approach to Salesforce consulting is deliberately handover-first for exactly this reason.

If you are weighing a migration, a first implementation, or simply whether Salesforce belongs in your organisation at all, we are happy to give you a straight answer — including that it might not. Get in touch and we will talk it through without a proposal attached.