Donor Data Migration: How to Switch CRMs Without Losing Giving History

Most nonprofits plan a CRM switch around the new software: the demo, the price, the training. Whether the switch works depends on the donor data migration, and the migration usually gets a weekend and a CSV export. Then at the first board meeting after go-live, someone asks why a major donor shows one gift when they have given every year since 2019, and your staff can’t explain it.

I spent part of this past week rebuilding donor export files for a nonprofit client moving their fundraising data into a new CRM. None of the problems were exotic. They are the same problems I have seen since I started working in nonprofits in 2014, and every one of them is cheaper to fix before the move than after it. Here is what to check, in the order I check it.

Why donor data breaks during a migration

Your current system has quirks your team has learned to work around. Maybe gifts from a business get logged under the owner’s name. Maybe online gifts come in automatically and checks get typed in by whoever opens the mail. Maybe a donor has two records because they gave once with a work email and once with a personal one. Your staff knows all of this, so the reports make sense to them.

A new CRM does not know any of it. It imports exactly what you give it, and it treats every row as the truth. The workarounds your staff remember do not come along. That is why a migration so often looks fine on day one and falls apart the first time someone pulls a giving report.

Step 1: Decide who gets credit for a gift

Start here, because every other decision depends on it. When a company, a family foundation, or a church gives, is that gift tied to the organization, to the person who arranged it, or both? Most donor CRMs separate the record that gave the money from the people who get soft credit for it. If your old system did not, you have years of gifts that need a decision.

This was the first thing I worked through with my client this week. A handful of business gifts sat under individual donors, and a few individuals had gifts filed under their company. Neither was wrong at the time. But if they move over as-is, your corporate giving totals are low, some individual donors look bigger than they are, and no report will show that one family is behind both. Write the rule down, apply it to the existing records, and link each organization to its people before you export anything.

Step 2: Map every way money reaches you

List every path a gift takes to get into your records. For most small nonprofits that is some mix of:

• Online card gifts from a donation form or payment processor
• Bank transfers and ACH, including recurring gifts
• Paper checks entered by hand
• Event revenue, sponsorships, and in-kind gifts
• Grants, which may or may not belong in the donor CRM at all

For each one, write down how it gets recorded today, who touches it, and what fields come through. Automated sources usually arrive complete. Manual ones are where the missing dates, blank addresses, and duplicate donors come from. I walked my client’s team through exactly how card, bank, and check gifts each reached their database, and that one conversation explained most of the gaps they had been asking about.

This map also tells you what has to be rebuilt after the move. If a form or an automation sends gifts into your current system, it has to be pointed at the new one, and someone has to test it with a real gift before the old system is turned off.

Step 3: Export giving history, not just donor totals

This is the mistake I see most. Someone exports a donor list with a “lifetime giving” column and a “last gift date” column and calls it done. The new CRM gets a number with nothing behind it. You lose first gift dates, gift frequency, which campaign a gift came from, and the ability to see who lapsed and when.

Export two files instead. The donor file has one row per person or organization, with contact details and a unique ID. The gift file has one row per gift, with the donor’s ID, the date, the amount, the payment method, and the fund or campaign. The new system can rebuild every total from the gift file, and the totals will be right because they come from the actual gifts.

For a quick check before import, I also add a field to the donor export that lists every gift date and amount for that person in one line. That field stays out of the new CRM. Its job is letting a staff member who knows the donors scan a row and say “that’s wrong, she gave in March too” without opening two files. That is the fastest way I know to catch missing history while it is still easy to fix.

Step 4: Clean before you move, not after

Cleanup feels like something you can do later in the shiny new system. It almost never happens, because once the new CRM is live, everyone is busy learning it. Do it now, in the system your team already knows.

• Merge duplicates. Search by email, then by last name and address. Two records for one donor means split giving history and two thank-you letters.
• Standardize your categories. If “Gala,” “gala 2024,” and “Annual Gala” are all the same thing, pick one.
• Fill the gaps that matter. A gift with no date cannot show up in a year-end report. Find it in the bank record or mark it clearly.
• Decide what not to bring. Ten-year-old event attendees with no gift and no email may not need to come with you.

Every decision you make here is one you do not have to make mid-import with a deadline on top of you.

Step 5: Run a test import and check it against reports you trust

Import a small batch first, ideally 20 to 50 donors you know well: a few major donors, a few monthly givers, a business, a family that gives jointly. Then compare. Does each donor’s total in the new CRM match the old system? Do the first and last gift dates match? Does the business show up as the business, with the right person attached?

Then pull one report you already trust, like last year’s total giving or a single campaign’s results, and rebuild it in the new system after the full import. If the numbers match, you are done. If they do not, the difference tells you exactly which gifts to go look at. Do not turn off the old system until that report matches.

When to bring in help

A clean donor list under a few hundred records, coming from one system, is something a careful staff member can handle with this checklist. It gets harder when your data is spread across several places (a spreadsheet, a payment processor, an old database, and somebody’s inbox), when organizations and individuals are tangled together, or when the new CRM has to stay connected to other tools after launch.

That is the work I do through nonprofit systems: mapping where your data actually comes from, deciding the rules, cleaning it, and building the exports so the new system starts out accurate. Some nonprofits keep their donor data in a dedicated CRM and run everything else in Airtable; if that is where you are headed, my Airtable setup work covers the operations side. If you are still deciding which system to move to, start with a Systems Blueprint Intensive so the migration plan comes from a clear picture of how your organization actually runs.

If you are not sure whether you need a new system yet, read signs your nonprofit has outgrown its spreadsheets. And if grants are part of what you are moving, how to build a grant tracking system for a small nonprofit covers how to keep them separate from individual giving.

Donor data migration FAQ

How long does a donor data migration take?

For a small nonprofit with one source system and reasonably clean data, plan on a few weeks from the first export to turning off the old system. Most of that time is cleanup and checking, not the import itself. Multiple data sources or years of inconsistent entry add time.

Should we migrate all of our historical giving?

Bring every gift for every donor you plan to keep. Giving history is what lets you see first gifts, lapsed donors, and upgrade patterns. What you can leave behind is contacts who never gave and cannot be reached.

What is the difference between hard credit and soft credit?

Hard credit goes to whoever the money actually came from, such as a company or foundation. Soft credit recognizes a person who influenced or arranged the gift, such as the owner or the board member who made the ask. Decide how you will use both before you migrate, because the rule affects every total in the new system.

Can we clean up our data after we move?

You can, but it rarely happens. Once the new CRM is live, staff are learning it and the cleanup keeps getting pushed back. Cleaning in the old system, before export, is faster and keeps bad data from becoming your starting point.