# CRM migration review checklist

Prepared by Serhat Dereli / Show Up — CRM Migration Checker

A practical planning aid for CRM implementation teams. This checklist does not run checks or certify a migration. A marked item records your review, not an automatic pass.

Project: ____________________
Review owner: _______________
Review date: ________________
Source export: _____________
Destination export: ________
Object / agreed subset: ____

## 01. Confirm authority and handling

- [ ] Reviewed

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.

**Evidence / owner / next action:**

---

## 02. Fix the export scope

- [ ] Reviewed

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.

**Evidence / owner / next action:**

---

## 03. Retain unique record IDs

- [ ] Reviewed

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.

**Evidence / owner / next action:**

---

## 04. Find missing and extra records

- [ ] Reviewed

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.

**Evidence / owner / next action:**

---

## 05. Agree transformations first

- [ ] Reviewed

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.

**Evidence / owner / next action:**

---

## 06. Check the fields that drive decisions

- [ ] Reviewed

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.

**Evidence / owner / next action:**

---

## 07. Keep each finding traceable

- [ ] Reviewed

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.

**Evidence / owner / next action:**

---

## 08. State coverage and limitations

- [ ] Reviewed

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.

**Evidence / owner / next action:**

---

## 09. Rerun against the agreed rules

- [ ] Reviewed

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.

**Evidence / owner / next action:**

---

## 10. Make acceptance a business decision

- [ ] Reviewed

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.

**Evidence / owner / next action:**

---

## Scope and decision record

Selected fields and rules:

Checks not performed / known limitations:

Unresolved exceptions and owners:

Acceptance decision, conditions and authorised decision owner:

## Discuss a scoped comparison

The indicative managed pilot covers one object or agreed subset, two CSV exports, up to 5,000 records in each export, five comparison fields and one scoped rerun. The current matching approach requires retained, unique source IDs. Software-assisted comparison is reviewed by Serhat Dereli. The service does not migrate, repair or certify the CRM.

A written quote confirms scope, total payable including any applicable tax, delivery arrangements and availability before acceptance.

Share project details only when enquiring. Do not send customer records, credentials or access tokens before authority and handling arrangements are agreed.

Website: https://crm-migration-checker.sdereli1993.chatgpt.site/checklist/
Contact: serhat@showuplondon.co.uk

Free to share with your team or clients, with attribution to CRM Migration Checker / Show Up.
