# CRM data migration – mapping and approval

Template date: 24 September 2026 · SYNQ

Working document for a specific transfer. The CSV contains fictional examples and blank rows. Both files support planning; neither is intended for direct import into a CRM.

## Ownership and scope

- Project / version: ____________________
- Business data owner: ____________________
- Technical implementation owner: ____________________
- Approval / abort decision by: ____________________
- Source systems and export date: ____________________
- Target system and prepared configuration: ____________________

| Dataset | Source | Transfer / separately accessible / decision pending | Owner | Reason |
|---|---|---|---|---|
| Organisations |  |  |  |  |
| Contacts |  |  |  |  |
| Opportunities |  |  |  |  |
| Activities / notes |  |  |  |  |
| Attachments |  |  |  |  |
| Other records |  |  |  |  |

Retention, deletion and access questions are assessed by the responsible people. Do not automatically delete records whose treatment remains unresolved.

## Mapping register

Complete the CSV: source/target field, transformation, ID mapping, conflict, expected and actual result, decision and approval. Give each additional custom mapping rule a unique identifier.

- Transfer method and checked limitations: ____________________
- Location of the approved source-to-target ID table: ____________________
- Mandatory fields and missing-value treatment: ____________________
- Treatment of original timestamps and people: ____________________
- Attachments / objects that cannot be exported: ____________________

## Duplicate review

- Signals that create a review case: ____________________
- Cases that must never be merged automatically: ____________________
- Role authorised to decide: ____________________
- Rule for conflicting field values: ____________________
- Treatment of relationships, history and attachments: ____________________
- Record of individual approvals: ____________________

## Test set and acceptance

- [ ] Several contacts at the same organisation
- [ ] Several open opportunities
- [ ] Change of record owner
- [ ] Activities, long notes and attachments
- [ ] Known duplicates and conflicting relationships
- [ ] Missing mandatory values
- [ ] Access with intended user roles
- [ ] Repeat run after an interrupted import

Add your own special cases: ____________________

| Object | Approved source count | Imported | Deliberately merged / excluded | Errors / difference explained | Approval |
|---|---|---|---|---|---|
|  |  |  |  |  |  |
|  |  |  |  |  |  |

Count reconciliation does not replace business relationship tests. Record expected and actual results in the CSV register.

## Switch and fallback

- Cut-off with time zone: ____________________
- Write pause or tested change-transfer process: ____________________
- Authoritative system before / after the switch: ____________________
- Backup and tested recovery procedure: ____________________
- Automations / integrations during import: ____________________
- Conditions that stop the switch: ____________________
- Decision owner and contact method: ____________________
- Treatment of changes already made in the target system if falling back: ____________________
- Approval for controlled reactivation of automations: ____________________

## Follow-up

- Period / owner: ____________________
- Issue register and reporting route: ____________________
- Late records and repeated import handling: ____________________
- Treatment of old synchronisations and access: ____________________
- Final approval with date: ____________________

CSV note: UTF-8 with BOM, semicolon delimiter. Format identifiers and dates deliberately when opening. Replace the examples; do not include real customer data in public project enquiries.