Short answer: because there is no in-place upgrade, a migration from NPSP to Nonprofit Cloud costs about the same as a fresh implementation plus a data migration. Using our published hours model, a simple 8-user org needs about 400 hours, a customised 20-user org about 740 hours, and a 40-user org with programmes and an integration about 1,460 hours. At offshore rates of $65 an hour that is roughly $26,500, $48,000 and $95,000. At onshore rates of $175 an hour it is roughly $71,400, $129,200 and $256,400. Timelines run from about two months to six months or more.
Why a migration costs as much as a new build
A Nonprofit Cloud org cannot be created by converting an NPSP org. You provision a new org, configure it for the new data model, rebuild the automations, reports and page layouts, then move your data across. The data move is real work too, because records change shape: Opportunities become Gift Transactions, Recurring Donations become Gift Commitments, households become Party Relationship Groups. Our data mapping guide goes object by object.
So the cost has two parts: the build, and the migration.
How we estimate the hours
We use the same model as our Salesforce implementation cost guide:
- Build: a base number of hours for the size of the build (QuickStart 150, Standard 400, Mid-market 900), scaled by team size (0.8 for 10 users or fewer, 1.0 up to 50).
- Data migration: 200 hours when moving from another CRM, which is what an NPSP org is in this model.
- Integrations: 120 hours per standard connection, such as a payment processor or email tool.
- Training: 30 hours plus 0.6 per user.
- Contingency: 15% on top.
Three example migrations
| Organisation | Build | Total hours | At $65/h (offshore) | At $90/h (nearshore) | At $175/h (onshore) |
|---|---|---|---|---|---|
| 8 users, donations only, little customisation | QuickStart | 408 | $26,521 | $36,722 | $71,404 |
| 20 users, donations and volunteers, several automations | Standard | 738 | $47,990 | $66,447 | $129,202 |
| 40 users, fundraising and programmes, one integration | Mid-market | 1,465 | $95,232 | $131,859 | $256,392 |
These are estimates from our model, not quotes. Licences are extra, though the first 10 are free under Power of Us. See our nonprofit pricing guide for licence costs.
How long does it take?
Our build bands give typical durations of 2 to 6 weeks for QuickStart, 6 to 12 weeks for Standard and 3 to 6 months for Mid-market. A migration adds time for data rehearsals and, ideally, a short period of parallel running where both systems are live and totals are compared.
| Organisation | Typical elapsed time |
|---|---|
| Small, simple | About 2 to 3 months |
| Customised, mid-size | About 3 to 5 months |
| Larger, with programmes and integrations | About 6 months or more |
For reference, Salesforce Ben reported one international nonprofit completing its NPSP to Nonprofit Cloud move over about six months.
The five phases
- Assessment. Inventory objects, automations, reports, integrations and data volumes. Decide what not to rebuild.
- Design. Map every NPSP object and field to its Nonprofit Cloud equivalent, and design households, designations and programmes in the new model.
- Build. Configure the new org in a sandbox: data model, automation, layouts, permissions and reports.
- Data migration. Load in rehearsals, reconcile totals each time, and keep a crosswalk of old and new record IDs.
- Test, train and go live. User acceptance testing, training, cut-over, then a period of support.
What makes a migration quote grow
- Heavy customisation. Every custom object and complex flow in NPSP has to be redesigned, not copied.
- Dirty data. Duplicates and broken households multiply migration effort. Clean before you move. See donor data clean-up.
- Integrations without Nonprofit Cloud support. If your payment or event tool only speaks NPSP, someone has to build the connection.
- Long gift histories. Decades of gifts mean more reconciliation work. Our illustrative Riverbend case study shows what reconciling to the penny involves.
- A rushed date. A go-live in three months or less carries a 25% premium in our model.
Five ways to keep the cost down
- Do not rebuild everything. Drop unused fields, reports and automations before you scope.
- Phase it. Fundraising first, programmes second, portals third.
- Clean data in-house beforehand. Staff who know the donors are better at deduplication than any contractor.
- Use free, native tools for repeated loads. Rehearsing a migration nine times should not cost nine times as much. Our free Smart Lookup Data Loader resolves lookups by name or code during import.
- Ask funders. Implementation suits a capacity-building grant.
To price your own organisation, run the cost estimator, choose nonprofit, and add data migration.
Frequently asked questions
How much does it cost to migrate from NPSP to Nonprofit Cloud?
Using our hours model, roughly $26,500 for a simple 8-user org, $48,000 for a customised 20-user org and $95,000 for a 40-user org with programmes, at offshore rates of $65 an hour. Onshore rates of $175 an hour are about 2.7 times higher. These are estimates, not quotes.
How long does an NPSP to Nonprofit Cloud migration take?
About 2 to 3 months for a small, simple org, 3 to 5 months for a customised mid-size org, and 6 months or more for larger orgs with programmes and integrations.
Why does migrating cost as much as a new implementation?
There is no in-place upgrade. You build a new org, rebuild automations and reports for the new data model, and then migrate your data into different objects.
Can we migrate ourselves without a partner?
Organisations with an experienced in-house admin can do much of the work, especially data clean-up and testing. Most still bring in a partner for data mapping and the migration rehearsals, because that is where costly mistakes happen.
Do our free Power of Us licences cover the migration?
No. Power of Us donates licences, not implementation services. Budget separately for the build and the data migration.
Prices in this article are Salesforce list prices in US dollars, per user per month billed annually unless stated, as verified on 29 September 2026. Salesforce changes pricing, so confirm with Salesforce before you sign. Figures from our hours model are estimates, not quotes.
Get a range for your own org in minutes with the cost estimator, or book a free call to scope it properly.