A practical handover resource
CRM migrationreview checklist. Ten checks to help a delivery team ask better questions before accepting migrated data. Use it to plan a review, record gaps and agree what happens next.
Free to read and share. No email address needed. Prepared by Serhat Dereli / Show Up.
A planning aid, not a migration certificate. This checklist does not run checks or certify data quality. Your review must reflect the project, business rules and checks outside the selected comparison scope.
Your review, in ten checks. Tick items to mark your notes in this tab. Ticks do not verify that checks passed.
01 Confirm authority and handling Confirm who may provide and review the records. Agree the transfer method, access, storage, retention and deletion arrangements before transferring data. Keep: A named owner, permission to use the data and recorded handling arrangements.02 Fix the export scope Use comparable snapshots from the same object or agreed subset. Record export dates, time zones, filters and excluded records so differences in scope are visible. Keep: A short export brief for both files, including known timing differences.03 Retain unique record IDs Confirm source IDs are present in both exports and are stable, unique and populated. Do not assume that a new destination ID, name or email is a reliable match. Keep: The identifier columns and counts of blank or duplicate identifiers.04 Find missing and extra records Compare IDs in both directions. Investigate missing destination records, unexpected extras and duplicate rows before interpreting field-level results. Keep: A record-level exception list, with expected exclusions explained.05 Agree transformations first Write down allowed changes such as whitespace, letter case, date formats, currency handling and mapped labels. Distinguish a transformation from an unexplained change. Keep: Rules accepted by the business owner, with concrete examples.06 Check the fields that drive decisions Compare selected fields such as amounts, owners, stages and dates. Confirm types, blank values, rounding and formats. Check totals where meaningful; matching totals can still hide record errors. Keep: A list of selected fields, comparison rules and any total checks.07 Keep each finding traceable For each discrepancy, preserve the record ID, field, before-and-after values and relevant export evidence. Record who will investigate and the resulting decision. Keep: Reviewable evidence and an owner for unresolved findings.08 State coverage and limitations Record how many records were compared, which fields were checked and what was excluded. Consider separate checks for relationships, files, permissions and automations. Keep: A coverage statement that separates pass, finding and not checked.09 Rerun against the agreed rules After corrections, create revised exports with the same scope and run the same checks. Keep earlier evidence and document any rule change instead of silently accepting differences. Keep: A dated rerun report and an explanation of remaining findings.10 Make acceptance a business decision Review unresolved exceptions and the checks outside scope with the client’s authorised owner. Record their decision, conditions and outstanding actions. Keep: An acceptance record for the agreed scope; not a blanket certification of the CRM.Working notes
0 of 10 marked 0 of 10 Your ticks are not saved. Print the page before closing it if you want to keep your marked copy.
Clear ticks Put the checklist to work
Agree the checks before you agree the outcome. For a scope conversation, bring the systems, approximate record count, retained-ID status and the fields that matter. Send a project outline only; agree authority and handling before transferring customer data.
