Why do nonprofits switch donor CRMs?
The reasons we hear most: the current system has become expensive for what the team uses, staff turnover means the database needs to be easier to run, or the organisation wants fundraising, marketing and programme data in one CRM instead of several.
Salesforce and HubSpot are the usual destinations for that last reason. A dedicated donor system is often easier on day one; a general CRM gives more room to grow.
FlitStack AI moves the data with its history and can set up the new CRM around it.
What makes a nonprofit migration different?
A donor database looks like a sales CRM, but the data model isn’t the same:
- Gifts, not deals. Gifts carry funds, appeals, campaigns, payment types and tax receipting data, and recurring gifts have schedules.
- Soft credits. One gift can credit several people, such as a spouse or a board member who made the introduction. Most general CRMs have no native soft credit.
- Households and relationships. Constituents belong to households and organisations, with relationship types that drive mailings.
- Long history. Giving history is the basis of every major-gift conversation. It has to arrive with the right dates and amounts, and the totals have to reconcile.
What does each source give you?
| Source | How data comes out | What to plan for |
|---|---|---|
| Raiser’s Edge NXT | Query exports (to Excel) and Blackbaud’s SKY API | API query jobs have usage limits, so large databases are extracted in stages |
| Blackbaud CRM | Export path confirmed during scoping | Enterprise data models with years of customisation |
| DonorPerfect | Export path confirmed during scoping | Custom fields and gift codes need value maps |
| Bloomerang | Export path confirmed during scoping | Timeline interactions and household rules |
| Salsa (Bonterra) | Export path confirmed during scoping | Engagement data (forms, email activity) alongside CRM records |
Raiser’s Edge and Blackbaud CRM are covered by FlitStack AI’s Blackbaud to Salesforce migration. CiviCRM moves to Salesforce or HubSpot. For the other sources, we confirm on the scoping call whether we connect by API or work from the export.
Should you use the destination vendor’s migration service?
Sometimes, yes. Donor platforms often run their own conversions for new customers:
- DonorPerfect sells a paid data transfer service in which a specialist maps fields, transfers records and validates history.
- Bloomerang gives plans that include data conversion a dedicated conversion project manager, with a standard timeline of 12–14 weeks.
If you’re moving into one of those systems, start there. FlitStack AI fits when the destination is Salesforce or HubSpot, which don’t run conversions from donor systems themselves.
Salesforce Nonprofit Cloud or HubSpot?
| Salesforce Nonprofit Cloud | HubSpot | |
|---|---|---|
| Data model | Built for nonprofits: donors, gifts, programmes | Gifts modelled as deals or a custom object |
| Platform | A core Salesforce product; NPSP was a managed package | One system for email, forms and CRM |
| Admin effort | Needs an admin or partner | Easier for a small team to run |
Salesforce publishes its own guide for moving from NPSP to Nonprofit Cloud. If you’re on NPSP today, that is a migration too, and the same process applies.
How does FlitStack AI run the migration?
- Scoping call on sources, record counts, gift history and the model you need. A written quote follows within one business day.
- Audit and design of households, gifts, soft credits, funds and value maps.
- Sample migration of real constituents and gifts, which your team checks in the new CRM.
- Full run and cutover with a delta sync for gifts entered during the project.
- Validation and support: a field-level validation report, one-click rollback if the run fails validation, and 14 days of direct support.
What should you prepare for the scoping call?
- Record counts by object: constituents, households, gifts, recurring gifts and soft credits.
- The systems around the CRM that send or receive data, and who owns each one.
- Retention rules for what must stay in the old system or an archive.
- A target date for cutover, so the delta sync can be planned around it.
Where does FlitStack AI fit?
If you’re moving a donor database to Salesforce or HubSpot and need giving history to arrive intact and reconcile, book a scoping call. See Salesforce implementation or HubSpot implementation for the setup side.

