Skip to content
Get a quote

Nonprofit CRM migration

Short answer

FlitStack AI migrates nonprofit donor databases such as Blackbaud Raiser's Edge NXT, Blackbaud CRM, DonorPerfect, Bloomerang and Salsa into Salesforce, including Nonprofit Cloud, or HubSpot. It keeps constituents, households, gifts, soft credits and activity history with original dates, validates every record, offers one-click rollback, and can set up the destination.

By

From Your industry system
DestinationSalesforce
Blackbaud Raiser's Edge NXTBlackbaud CRMDonorPerfectBloomerangSalsa (Bonterra)
Industry systems mapped into your new CRM

Systems we migrate from

Blackbaud Raiser's Edge NXT

Blackbaud's fundraising CRM. Data comes out through Query exports or the SKY API.

Blackbaud CRM

Blackbaud's enterprise fundraising CRM for universities, healthcare and large NGOs.

DonorPerfect

Donor management system with its own paid data transfer service for organisations moving in.

Bloomerang

Donor management system; plans that include conversion get a conversion project manager.

Salsa (Bonterra)

Salsa Labs is part of Bonterra; Salsa CRM is a constituent relationship manager and Salsa Engage handles digital engagement.

Salesforce Nonprofit Cloud (Agentforce Nonprofit)

Salesforce's nonprofit product, built into the core platform rather than the older Nonprofit Success Pack managed package.

HubSpot

Destination for organisations that want donor communications and CRM in one system.

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?

SourceHow data comes outWhat to plan for
Raiser’s Edge NXTQuery exports (to Excel) and Blackbaud’s SKY APIAPI query jobs have usage limits, so large databases are extracted in stages
Blackbaud CRMExport path confirmed during scopingEnterprise data models with years of customisation
DonorPerfectExport path confirmed during scopingCustom fields and gift codes need value maps
BloomerangExport path confirmed during scopingTimeline interactions and household rules
Salsa (Bonterra)Export path confirmed during scopingEngagement 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 CloudHubSpot
Data modelBuilt for nonprofits: donors, gifts, programmesGifts modelled as deals or a custom object
PlatformA core Salesforce product; NPSP was a managed packageOne system for email, forms and CRM
Admin effortNeeds an admin or partnerEasier 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?

  1. Scoping call on sources, record counts, gift history and the model you need. A written quote follows within one business day.
  2. Audit and design of households, gifts, soft credits, funds and value maps.
  3. Sample migration of real constituents and gifts, which your team checks in the new CRM.
  4. Full run and cutover with a delta sync for gifts entered during the project.
  5. 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.

Questions, answered

A few useful answers.

Can you migrate Raiser's Edge NXT to Salesforce?

Yes. Raiser's Edge NXT data comes out through Query exports or Blackbaud's SKY API. FlitStack AI maps constituents, relationships, gifts, soft credits, funds and appeals to the Salesforce data model, then runs a sample migration you check before the full run.

What happens to soft credits and fund accounting?

They need a design decision. Salesforce and HubSpot don't model soft credits or funds the way Blackbaud does, so we agree the structure first, often a related object for soft credits and a fund object or field, and map every gift to it.

Nonprofit Cloud or Nonprofit Success Pack?

Salesforce now positions Nonprofit Cloud as a core product and publishes a guide for moving from NPSP into it. New implementations generally start on Nonprofit Cloud; if you're already on NPSP, moving to Nonprofit Cloud is its own migration.

Our new donor platform offers free migration. Why use you?

If your destination vendor's own migration covers your data, use it. FlitStack AI fits when you're moving to a general CRM like Salesforce or HubSpot, need history and custom fields the vendor service leaves out, or want a sample run and rollback.

Can you set up the new CRM too?

Yes. FlitStack AI can build pipelines for major gifts and grants, properties, workflows for acknowledgements and stewardship, and user permissions in the same project.

A closer look

Tell us what you’re moving.

Share your source, destination and rough record counts. We scope the migration and the process work with you and send you a quote.

Get a quote