CRM Migration Data Map Template

What This Template Does

The CRM migration data map provides a structured working document for planning and executing a nonprofit CRM migration. It is organized by record type (contacts/donors, grants, organizations, notes/activities, giving history) with field-level mapping tables, transformation documentation, and validation checklists.

A data map is not optional for a CRM migration. Organizations that skip it spend their time fixing migration errors after go-live rather than before. Errors found after go-live affect live operations and damage staff confidence in the new system.

Pre-Migration Data Audit

Before mapping any fields, audit the source system. What you migrate is what you have - and most source systems contain years of accumulated data quality problems that will transfer directly into the new system if not addressed first.

Audit checklist:

Duplicates

• Run a duplicate report in the source system (duplicate contacts, duplicate organizations, duplicate grant records)
• Establish and apply a merge rule: when in doubt, which record is the authoritative one
• Target: zero duplicate contacts by primary identifier (email address)

Blank required fields

• Identify which fields the target system requires (typically: contact name, primary email or mailing address, organization affiliation for institutional contacts)
• Run a report of source records where these fields are blank
• Resolve before migration: update the record with the correct data, flag as incomplete, or determine whether the record should be migrated at all

Outdated records

• Identify contacts with no activity in the past [5-7] years
• Decision: migrate (may have historical giving data), archive (move to inactive), or exclude (no useful data)
• Document the decision and the criteria - this protects against complaints after migration that “all our contacts are gone”

Inconsistent formatting

• Phone numbers (should be a consistent format: (XXX) XXX-XXXX or XXXXXXXXXX)
• Addresses (should include zip+4 for major gift cultivation; check for obvious errors)
• Salutations (inconsistent capitalization, honorifics mixed with first names)
• Fund designations (are all active restricted funds using consistent naming across all records)

Data that lives outside the system

• What is in spreadsheets that needs to be in the new system
• What is in email or shared drives that should be attached to records
• What custom fields does your team use that might not have obvious mapping to the target

Budget two to three weeks for the data audit. Organizations that rush this step find the problems after go-live, when fixing them disrupts staff workflows.