Salesforce Nonprofit Cloud: Review and Pricing
Ten free licences through Power of Us, and licences are not the cost. Implementation and an administrator are. Also covers the NPSP transition, which is the decision most nonprofits are actually facing.
Salesforce is the most capable nonprofit CRM available and the one most likely to be abandoned eighteen months after purchase. Both of those things are true for the same reason: it is a platform rather than a product.
The ten free licences are real and they are not the question. The question is whether you can fund what makes them useful.
The transition you need to understand first
Salesforce’s nonprofit offering is mid-generation, and which product you are being sold depends on when you arrive.
| Nonprofit Success Pack, NPSP | Nonprofit Cloud | |
|---|---|---|
| What it is | A free managed package layered on Sales Cloud | A nonprofit product built into the core platform |
| Feature development | Ended March 2023 | Where all investment goes |
| Still supported | Yes, with no announced end of life | Yes |
| In Power of Us for new applicants | Removed December 2025 | Yes |
Two practical consequences. If you are adopting now, you are adopting Nonprofit Cloud, and advice written about NPSP may not apply. And if you are already on NPSP, there is no forced deadline, but you are on a platform receiving no new features, and migration when it comes is a second implementation project with a second round of consultant fees.
Factor that into a total cost comparison. An organization choosing between Salesforce and a purpose-built donor CRM today should price in one migration, not zero.
What the licences cost
Through the Power of Us programme, eligible nonprofits receive ten donated licences. In the US, eligibility generally requires 501(c)(3) status, and you apply with your determination letter and employer identification number.
Beyond ten users, you pay. Salesforce publishes nonprofit pricing per user per month, billed annually, across editions, and additional licences are discounted against commercial rates rather than free. This page is not quoting per-user figures, because Salesforce’s nonprofit line has changed name and structure twice in three years and the figures circulating in comparison articles do not reliably match what the vendor currently quotes. Get a written quote, for the specific edition, for your user count.
What is worth planning around is the shape of it. The eleventh user is a cliff, not a step, because that is the point at which a free deployment becomes an annual subscription. Organizations that grow past ten users unexpectedly find a budget line they did not plan.
The cost that is not the licence
This is the part that decides whether the project succeeds.
| Cost | Nature | Frequently underestimated because |
|---|---|---|
| Implementation | One off, typically a consulting partner | It is quoted against a scope that grows during discovery |
| Data migration | One off | Your existing data is messier than you think, and cleaning it is the work |
| Administrator | Ongoing, staff or retained | The system needs someone who owns it, and volunteers do not persist |
| Integrations | One off plus subscriptions | Payment processing, email and accounting connectors are usually separate products |
| Data storage | Ongoing | Allowances are modest and overages are billed |
| Training | Recurring | Staff turnover means retraining, not a single session |
The administrator line is the one that sinks deployments. Salesforce rewards configuration, and configuration decays without an owner. An organization that cannot name the person responsible for the system a year from now should not adopt it.
What it does that alternatives do not
It models anything. If your organization tracks clients, cases, sessions, outcomes, volunteers, donors and grants and needs them related to one another, Salesforce will do it. Purpose-built donor databases generally will not, because they are built around gifts.
Programme and case management alongside fundraising. For a human services organization this is the argument. One record of a person, whether they arrive as a client, a volunteer or a donor.
Reporting depth. Report and dashboard building is a genuine strength, and a board that wants a specific view can usually have it without a developer.
An enormous ecosystem. Thousands of applications, a large consultant market, and a nonprofit user community that is unusually generous with help.
Where it goes wrong
Adopted for the free licences. The most common failure. An organization takes the ten licences, has no budget for implementation, configures it themselves in evenings, and ends up with a worse version of the spreadsheet they replaced.
No internal owner. The consultant leaves, nothing is adjusted, staff work around it, and within two years the data is unreliable enough that people stop trusting reports.
Bought for a simple need. An organization that needs to record donations, send receipts and run an appeal is buying a platform to solve a product problem, and will pay for that in complexity every day.
Scope growth during implementation. Because it can do anything, the project tends to try to. A first phase that covers fundraising only, and works, beats a comprehensive one that never quite launches.
Who it is for
| Your situation | Verdict |
|---|---|
| Under $250,000, donations only, no technical staff | No. A purpose-built donor CRM will serve you better for less. |
| Growing, fundraising plus a simple programme | Possible, if you budget for implementation rather than taking the licences alone. |
| Case management, outcomes tracking, multiple programmes | This is the case Salesforce is genuinely strong for. |
| Already have a Salesforce administrator or a committed technical volunteer with continuity | Yes, the main obstacle is already solved. |
| Multi-site, complex reporting to funders, several data domains | Yes, and few alternatives will do it. |
Data protection, which nobody asks about until later
If you put client records in Salesforce, you have taken on obligations that are yours regardless of what the platform does. The vendor secures the infrastructure. Who inside your organization can see a case note is your configuration, and misconfigured permissions are the common failure, not breaches.
Decide before go-live who can see what, whether fundraising staff should see programme records at all, and how access is removed when someone leaves. Write it down, and review it annually alongside your conflict of interest acknowledgements, because both are the kind of control that quietly stops being true.
Questions to ask a consulting partner
The consultant market around Salesforce is large and its quality varies more than the pricing does. Six questions that separate the two.
| Ask | What a good answer sounds like |
|---|---|
| How many nonprofits our size have you implemented? | Specific references you may contact, in your subsector |
| What is out of scope in this quote? | A written list, offered before you ask twice |
| Who cleans our data, and when? | A named phase with our effort in it, not an assumption that it arrives clean |
| What happens after go-live? | A defined support period and a handover to a named person on our side |
| Will we be able to change things ourselves? | Configuration over custom code, and training that says so |
| What would you tell us not to do in phase one? | Anything at all. A partner who agrees to everything has not read your scope. |
That last question is the most useful one in the list. Implementations fail from scope, not from software, and a partner willing to argue with you about phase one is worth more than one who is cheaper.
A reasonable test before committing: write down who administers this in three years, and what you will pay them. If that sentence cannot be finished, the ten free licences are the most expensive thing on offer.
Questions people ask
Is Salesforce really free for nonprofits?
Ten licences are free through the Power of Us programme, and licences are a minority of the true cost.
What you will pay for: implementation by a consulting partner, data migration, integrations with your payment processor and accounting system, additional storage if you exceed the allowance, and somebody's time to administer it permanently.
Implementation is the large one and it varies enormously with scope. An organization that budgets nothing beyond the free licences is the classic failed deployment, and it fails slowly enough that nobody calls it a failure until the data is already unreliable.
What is the difference between NPSP and Nonprofit Cloud?
NPSP, the Nonprofit Success Pack, was a free managed package installed on top of Sales Cloud that added nonprofit objects such as households, recurring donations and campaigns. Nonprofit Cloud is a nonprofit product built into the core platform rather than layered on it.
Salesforce ended NPSP feature development in March 2023 and removed it from the Power of Us programme for new applicants in December 2025. New nonprofits now receive the current nonprofit product.
NPSP is still supported and no end of life has been announced, so existing users are not being forced anywhere. They are, however, on a platform that will not gain new capability, and should treat a future migration as a matter of when.
Who is eligible for the Power of Us programme?
In the United States, generally organizations recognised as tax exempt under section 501(c)(3), with some other exempt categories included. Outside the US, the equivalent charitable registration in your jurisdiction, such as Charity Commission registration in the UK or ACNC registration in Australia.
You apply with your organization's tax identification number and your determination letter, and review takes a few business days.
Some organization types are excluded, and the guidelines are published. If your organization is unusual, for example a political organization or a mutual benefit body, read the eligibility guidelines before planning around the grant.
How much does Salesforce cost beyond the ten free licences?
Salesforce publishes nonprofit pricing per user per month, billed annually, with additional licences discounted against commercial rates. This page does not quote a figure because the nonprofit product line has been restructured twice in three years and the numbers circulating in comparison articles do not reliably match current quotes.
Get a written quote for the specific edition and user count you need, and ask explicitly what happens at renewal, since introductory nonprofit rates and renewal rates are not always the same.
Budget separately for storage. Data and file storage allowances are modest relative to what an organization accumulates over several years, and overage is billed.
Do we need a consultant to implement Salesforce?
For anything beyond the simplest fundraising setup, in practice yes.
Organizations do self-implement successfully, and it takes a genuinely technical person with real time available, not an enthusiastic staff member with evenings. The failure mode is a half-configured system that people work around, which is worse than the spreadsheet it replaced because it looks authoritative.
If budget is the obstacle, the better move is to narrow the scope rather than skip the help. A properly implemented fundraising-only phase, done by someone who has done it before, beats a comprehensive self-build that stalls.
What are the alternatives to Salesforce for nonprofits?
Purpose-built donor CRMs are the main alternative and are the right answer for most small organizations. Products in this category handle donations, recurring giving, acknowledgements, appeals and basic reporting out of the box, with no implementation project.
The trade is capability against effort. They do fundraising well and stop there. If you need case management, outcome tracking or an unusual data model, you will hit their limits.
The honest decision rule: if you can list your requirements and a donor CRM meets them, buy the donor CRM. Salesforce earns its complexity when your requirements do not fit a standard shape, and not before.
Can Salesforce handle programme and case management?
Yes, and it is the strongest argument for choosing it.
You can model clients, cases, sessions, referrals, assessments and outcomes, relate them to the same person records as donors and volunteers, and report across all of it. Human services organizations reporting outcomes to government or foundation funders get real value here that a fundraising database cannot provide.
Two cautions. This is a larger implementation than fundraising alone, so phase it. And case data about identifiable people carries privacy and security obligations, sometimes including sector-specific ones, that your configuration and your access permissions must actually satisfy.
How long does a Salesforce implementation take?
For a fundraising-only deployment with clean data and a decided scope, commonly a few months. For a multi-programme implementation with case management and integrations, considerably longer, and the variable is rarely the software.
The time goes into three things: deciding how your organization actually works, cleaning data that turns out to be inconsistent, and training people. Configuration is the fast part.
Phase it. Launch fundraising, let people use it for a few months, then add programmes. Implementations that try to deliver everything at once are the ones that are still not live a year later, and by then the staff who specified it have moved on.