Nonprofit CRM Data Cleanup Checklist: Before You Migrate or Switch
Why clean first?
A migration moves whatever is in your old database, including duplicates, inconsistent coding and broken records. Fixing problems before the move is cheaper than fixing them in the new system, and it means your first reports in the new CRM can be trusted.
The checklist
1. Back up and document
- Export a full backup of constituents, gifts, notes, attachments and configuration before changing anything.
- List every system that feeds the database: online giving, events, email, accounting, spreadsheets.
- Write down known problems and who owns each decision.
2. Duplicates
- Run duplicate searches on name, email, address and phone. Review matches manually before merging.
- Decide which record wins on conflicts (name, address, preferences) and apply the rule consistently.
- Check organizations, donor-advised fund sponsors and spouses as well as individuals.
3. Addresses and contact data
- Standardize formats, states, ZIP codes and country values.
- Run an address-update service if you mail regularly, and flag returned mail.
- Remove invalid emails and mark seasonal or alternate addresses clearly.
4. Households and relationships
- Confirm who is linked to whom, and which record receives solicitations and receipts.
- Resolve constituents who appear both on their own and inside a household.
- Document how soft credits and matching gifts are recorded today.
5. Gift, fund, campaign and appeal coding
- Standardize fund, campaign and appeal lists. Merge or retire near-duplicates.
- Check that GL codes match your accounting system and note the code length your new system must support.
- Identify gifts with missing or generic codes before migration, not after.
6. Recurring gifts and payment data
- Verify active schedules, amounts, frequencies and next payment dates.
- Find out which payment processor holds donor payment tokens and whether they can move to the new system.
- Close out cancelled or lapsed schedules so they do not migrate as active.
7. Notes, attachments and history
- Decide what history must come over (how many years of gifts, notes, event and athlete history, grants) and what can be archived.
- Check attachments for size and format limits in the new system.
8. Consent and communication preferences
- Capture opt-outs, do-not-mail and do-not-call flags and make sure they migrate.
- Keep a record of how and when consent was given where required.
9. Inactive and deceased records
- Archive or flag them rather than deleting, unless policy or law requires deletion.
10. Test, then migrate
- Run a sample migration and compare totals: gift counts, amounts by fiscal year, constituent counts and recurring schedules.
- Have finance, development and operations staff verify results against known reports.
- Plan a freeze window and a parallel-run period before cutover.
Common mistakes
- Merging duplicates automatically without review.
- Migrating everything and planning to clean up later.
- Forgetting payment tokens and recurring schedules until the final week.
- Skipping a reconciliation of gift totals before and after the test load.
Common questions
Why clean donor data before migrating to a new CRM?
Migration moves whatever is in your old system, including duplicates, inconsistent coding and broken records. Cleaning first is cheaper than fixing problems after they are loaded into the new system, and it makes the new system's reports trustworthy from day one.
What should be cleaned first in a nonprofit database?
Start with duplicate constituents, then standardize addresses, households and relationships, and gift, fund and campaign coding. These affect reporting and mailings the most and are the hardest to untangle after a migration.
How long does donor data cleanup take?
It depends on record count, how many sources feed the database and how much history is inconsistent. Plan separate time for review, a test migration and corrections, and start well before your contract end date.
Should old records be deleted or archived?
Archive or flag inactive and deceased records rather than deleting them, unless policy or law requires deletion. Keep a backup of the original data before any bulk change.
Need help?
Precedent Nonprofit Advisory provides data hygiene, deduplication and backend configuration across major nonprofit CRMs, and independent CRM evaluation with no vendor commissions. See also our guide to running a nonprofit CRM RFP and Raiser’s Edge NXT alternatives. Request a discovery call or email adam@precedentnonprofit.com.