Nonprofit Cloud · implementation and NPSP move
Donors are not customers.
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.
Elapsed
-
Fixed price
-
Scale
-
Engagement
-
What makes up the price
Phases
Every line above is a fixed price, not a range. It becomes the contract price once the written scope is signed, and it cannot move upward afterwards. Everything is built inside your own org and documented as the work happens.
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.
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.
Giving is recurring, seasonal and restricted
Recurring gifts, pledges paid in instalments, restricted funds that can only be spent on one programme, and a December that produces a third of the year's income. None of this behaves like a sales pipeline and none of it should be modelled as one.
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.
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.
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.
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.
You are starting fresh
Then build on Nonprofit Cloud. There is no reason to adopt the older package for a new implementation, and the data model differences are easier to live with when nobody has learned the previous one.
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.
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 ongoing weekly support rather than a finished system
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 · RevOps Architect · 7 Salesforce certifications · on the platform since 2018
Questions
Asked often enough to answer here.
How much does a Nonprofit Cloud implementation cost?
From €11,000 for a base package covering constituent and household modelling, giving records, acknowledgement, reports, up to 15 staff users, training and a 60-day handover. Programme management, grants, volunteers and migration are itemised separately.
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. New implementations should start on Nonprofit Cloud; heavily customised NPSP orgs should be measured before a date is committed.
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.
When is the worst time to migrate a fundraising system?
Between October and January. Year-end appeals frequently produce a third of annual income, so a migration during that window risks the organisation's most important quarter.
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.