Solutions4sf I build CRMs, and fix the ones that broke

Agentforce Nonprofit, formerly Nonprofit Cloud · implementation and NPSP move

Nonprofit Cloud for a charity, from €4,550.
Ten licences are free. Three fixed packages, and each step up costs no more than the first.

Donors are not customers, and modelling them that way is the mistake. A household gives, an individual attends, an employer matches, and a grant funds a programme rather than a deal. Nonprofit implementations go wrong when that structure is forced into an opportunity pipeline. Scope yours below before anyone quotes you.

SCOPING ESTIMATOR BASIS Nonprofit Cloud Fundraising build for a UK charity SENIOR-LED · PHASES IN SEQUENCE

Elapsed

-

Estimate

-

Scale

-

Engagement

-

What makes up the price

Phases

Each package has a published price, so the estimate is one figure, not a range. The estimator picks the smallest package that covers your answers. It is an estimate rather than a quote until the written scope is signed; once that is signed, its price cannot move upward. Lines marked by agreement sit outside all three and are scoped with you one at a time, each with its own written scope and price. Everything is built inside your own org and documented as the work happens.

The price

What does a Nonprofit Cloud implementation cost?

Three fixed packages. Fundraising essentials is €4,550 (about £3,800) for 70 hours, Fundraising complete is €8,450 (about £7,050) for 130 hours, and Charity operations is €13,000 (about £10,850) for 200 hours. Each includes training, thirty days of support after handover, up to eight hours in total, and a sixty day warranty, and each is built on the ten Agentforce Nonprofit (formerly Nonprofit Cloud) licences Salesforce donates to eligible charities. Moving up from one package to the next costs €3,900 or €4,550 (about £3,250 or £3,800), so a charity can fund one step a year.

Prices are in euro and invoices are issued in euro. Pound sterling figures are approximate: converted at the European Central Bank reference rate of 4 November 2026, 1 EUR = 0.8346 GBP, and rounded to the nearest £50.

Product name from Salesforce’s announcement of 2 December 2025.

01

Fundraising essentials · 70 hours · €4,550 about £3,800

For a charity moving off spreadsheets with up to ten users. Help applying for the ten donated licences, donors and households, promises and payments split across your programmes, thank-you letters, three dashboards and a simple import from your spreadsheets. Not included: Gift Aid, migration from another fundraising system, grants, payment integrations, programmes and volunteers.

02

Fundraising complete · 130 hours · €8,450 about £7,050

For a charity with several income streams and an old system to leave. Everything in essentials, plus Gift Aid declarations, eligibility and the claim export for HMRC; migration from one system (NPSP, Raiser’s Edge, Donorfy, Beacon or spreadsheets) with the totals reconciled to the penny before anyone uses it; incoming grants from trusts and foundations with stages and deadlines; one payment integration from one giving platform, either a ready-made connector that writes gifts into Nonprofit Cloud, such as MoveData for JustGiving, on a subscription the charity pays, or a file import into a gift batch; and income dashboards by type on the NCVO income scale. From essentials: 60 hours, €3,900.

03

Charity operations · 200 hours · €13,000 about £10,850

For a charity that reports impact to funders and runs a grants or application process. Everything in complete, plus committee scoring with a stage that moves on the committee’s own rules, an application form that applicants fill in without a Salesforce login, one module of your choice (programme and outcome tracking, or volunteers and shifts), and report packs in the formats your funders set. From complete: 70 hours, €4,550.

Outside all three, priced with you once scoped: a second module, a donor portal, events, a second migration source, licences beyond the donated ten, a payment processor such as Stripe or GoCardless, or a giving platform with no ready-made connector, connected directly, and accounting integration with the reconciliation that stops a gift being counted twice.

Most published price guides for this still describe the Nonprofit Success Pack, the older managed package. Nonprofit Cloud is a different data model, built on Person Accounts, Gift Commitments and Gift Transactions, so the work and the price are not the same thing.

Applying for a grant to pay for it? Ask for a written scope with the package and its price, ready to attach to a funding application. Nothing is paid before you sign it, and its price holds until the funder decides, for up to sixteen weeks. The charity below built its system in phases.

Proof

What did this look like for a UK charity?

A small community charity in the east of England, raising money through contracts, grants and giving, all of it tracked in colour coded spreadsheets. I built its fundraising on Nonprofit Cloud and moved the money history in. Six things from that build; the charity case study has the decisions behind them.

01

Three spreadsheets became one fundraising system

The same applications sat in three overlapping sheets at different stages, with the status held in cell colour that does not survive an export, and fund holders listed twice under different names. Applications, promises and payments now live in one place, with the stages the charity’s own team asked for and a separate outcome field.

BeforeStatus as a cell colour
02

Every pound reconciled to the charity’s own book

Funders, applications, promises and payments moved in, and three totals were checked against the charity’s own workbook: money received, money still expected and money promised. All three matched to the penny before anyone was shown a dashboard. No email went to a donor during any load.

CheckedTo the penny
03

Each payment splits across programmes on its own

Salesforce documents that a payment inherits the programme split of its promise. Tested on both steps, it inherits nothing unless the payment is entered through Gift Entry, which this charity does not use. So the split is written onto every payment as it is created, and programme income is a stored number rather than a formula nobody can audit. How to write the split onto every payment.

TestedNot taken from the documentation
04

A declined bid can no longer carry money

An audit found a draft promise on an application that had already been declined, quietly counted in the year to date totals. A guard on the screen and validation on the money records now stop it by every route, including data loads.

Found byAn audit of the build
05

The board saw where its income really comes from

The project started from the belief that the charity leaned on grants. Once every promise carried its income type, the committed money showed the opposite: most of it came from contracts and tenders, and grants were a small share. That is the picture its diversification strategy now starts from.

ResultContract led, not grant led
06

The investment committee scores inside Salesforce

Nine criteria scored 0 to 3, so the outcome bands were checked against the arithmetic and set on a maximum of 27 before the first application was scored. An application moves on once any four members have scored, the number is a setting rather than code, named members can be made compulsory, and scoring closes at a deadline. Members without a Salesforce login score through a form.

CheckedThe arithmetic of the bands

Built with Nonprofit Cloud Fundraising in the charity’s sandbox. The charity is not named and none of its figures are published here: a client’s money and records stay the client’s.

What makes this different

Why does a nonprofit build cost differently?

The platform is the same Salesforce. The data model is not, and neither is the way decisions get made inside the organisation.

01

The constituent is not one person

A household gives jointly, an individual attends, an employer matches, and the same human appears in all three roles. Getting this structure right at the start is what makes soft credits, household rollups and acknowledgement letters work later. Getting it wrong is a rebuild.

Decided inDiscovery, before anything is configured
02

Giving is recurring, seasonal and restricted

Recurring gifts, pledges paid in instalments, restricted funds that can only be spent on one programme, and a final quarter that raises more than a third of the year's income. None of this behaves like a sales pipeline and none of it should be modelled as one.

NeverDonations as opportunity stages
03

Programme delivery is the other half

Many organisations need to track who was served, not only who paid. Programme management, case tracking and outcome reporting are separate work from fundraising, and quoting them together without saying so is how nonprofit projects overrun.

PricedAs its own line, always
04

Reporting answers to funders, not managers

Grant reports, impact statements and annual returns have formats somebody else decided. That constrains the data model from the outset, which is why funder requirements belong in discovery rather than in the reporting phase.

Bring to discoveryYour two largest funders' report formats

NPSP

Should we move off the Nonprofit Success Pack?

Nonprofit Cloud is the current product and NPSP is the older managed package. That does not by itself make moving urgent, and the honest answer depends on what your setup is doing today rather than on which product is newer.

A third shape needs neither package: a charity foundation runs its donations on plain Sales Cloud, with donors as person accounts and gifts as opportunities.

A

NPSP works and your team knows it

Then plan rather than panic. Moving a functioning fundraising system in the middle of an appeal season is how organisations lose a December. Diarise the decision for the quieter part of your year.

TimingNever between October and January
B

You are starting fresh

Then build on Nonprofit Cloud. For a new org the older package has little to offer that the current product does not, and the data model differences are easier to live with when nobody has learned the previous one.

StraightforwardGreenfield is the cheapest shape
C

NPSP is customised beyond recognition

Years of workarounds, custom objects for things the package could not do, and reports that only one person understands. This is the expensive case, and it is worth measuring before committing to a date.

Already on NPSP

What can a charity on NPSP buy before deciding to move?

Two things, neither of them a migration: support from €520 (about £450) a month and the €650 (about £550) data quality check. The check takes one working day, delivered within three, and on NPSP reads Setup, the inventory Salesforce’s migration guide asks for before a move. Its verdict says stay and fix, or move, with the hours for each.

01

Nobody has looked after NPSP since the person who set it up left

Continued support is a fixed number of hours a month with an end date in the agreement: €520 (about £450) for 8 hours, €1,040 (about £850) for 16 or €2,080 (about £1,750) for 32, three months minimum. In an org somebody else set up, the first month goes on reading what NPSP does today and writing it down, so the next change does not break something nobody described. What the hours cover. Pardot for Nonprofits: Donor Segments, Journeys.

Start withSupport, from €520 (about £450) a month
02

Is NPSP at end of life?

No Salesforce page I could find gives NPSP an end date. Salesforce’s managed packages page says NPSP “will continue to be supported”. New charities get something else: Salesforce’s Power of Us help page of 16 October 2026 offers them Agentforce Nonprofit or Sales and Service licences and does not name NPSP. When staying on NPSP is the right call.

03

The verdict says move

Then the move is priced as one of the packages above, not as an upgrade: Salesforce’s guide says a move “more closely resembles a reimplementation than a traditional software upgrade”. Fundraising complete, €8,450 (about £7,050) for 130 hours, is the first of the three with a migration from NPSP in it, with the totals reconciled to the penny before anyone uses the new org. The check’s fee is credited in full against any engagement booked within sixty days of delivery. If the verdict says stay, its order of work is what the support hours go on.

ThenA package, from €8,450 (about £7,050) for a move

I have not moved an NPSP org myself. I built the UK charity’s fundraising above on Nonprofit Cloud, which is where a move lands. Two checks from that build are ones a migration needs too: three totals reconciled to the penny, and a test showing that a payment inherits no programme split unless it is entered through Gift Entry, although Salesforce documents that it does.

NPSP status from Salesforce’s managed packages page, read on 5 November 2026, and its Power of Us help page of 16 October 2026. The inventory and the size of a move from Salesforce’s Agentforce Nonprofit Migration Guide, version 2 of 1 June 2026.

Fit

Is this the right practice for a nonprofit?

This works well if

  • Between 5 and 100 staff who will use the system
  • You would rather own the system than rent a consultant indefinitely
  • Somebody internal can be freed up for two hours a week
  • You want the data model documented for whoever comes after you
  • Budget is a fixed figure a board has to approve, not an open hourly rate

This is not the right fit if

  • You need a nonprofit-specialist partner listed for grant compliance
  • The requirement is to replicate Raiser's Edge exactly
  • Nobody can commit to decisions between board meetings
  • You need somebody to own the org permanently, with no end date

Salesforce's Power of Us programme grants eligible nonprofits ten donated subscriptions, which changes the licence conversation but not the implementation one. Check eligibility with Salesforce directly; it is not something a consultant can grant.

Bring the estimate to the board.

The document above is written to be forwarded. Read it out on a call and I will tell you where it is optimistic, where it is generous, and what I would phase into next year.

Serhii Skrypnyk · Senior Salesforce Administrator · 7 Salesforce certifications · on the platform since 2018. Reviewed 14 November 2026.

Questions

Asked often enough to answer here.

Q

Should a nonprofit move from NPSP to Nonprofit Cloud?

Not automatically. Nonprofit Cloud is the current product and NPSP the older managed package, but a functioning NPSP setup does not need moving urgently. For a new org, Nonprofit Cloud is the usual starting point; heavily customised NPSP orgs should be measured before a date is committed.

Depends
Q

Why should donations not be modelled as opportunity stages?

Giving is recurring, seasonal and often restricted to a specific programme, and a single human can appear as a household, an individual attendee and a matching employer. A sales pipeline cannot express soft credits, pledge instalments or restricted funds without workarounds that later break reporting.

Because
Q

When is the worst time to migrate a fundraising system?

Between October and January. More than a third of annual income arrives between October and December, and December alone brings about 18 percent, according to the Blackbaud Institute's 2025 Trends in Giving, so a migration during that window risks the organisation's most important quarter.

Worst time
Q

Does the Power of Us programme cover implementation?

No. Power of Us grants eligible nonprofits ten donated Salesforce subscriptions, which changes the licence cost but not the implementation cost. Eligibility is confirmed by Salesforce directly rather than by a consultant.

Discount