BYstudio. CRM data migration checklist
23 October 2026. https://bystudio.ru/en/solutions/crm-data-migration-checklist/

Project: ____________________  Responsible person: _________________
Source and destination CRM: ________________________________________
Trial date: __________________  Production cutover: ________________

1. SCOPE
For each object, record source, volume, required fields and relationships.
Companies / contacts / deals / products / tasks / files / conversations.
Archive exclusions, archive location and permitted access: __________
Required export and import capabilities verified: __________________

2. FIELD MAP
Object and source ID: _____________________________________________
Source field -> destination field -> type -> transformation -> check.
Date and time-zone rules: __________________________________________
Old statuses -> new stages: ________________________________________
Staff -> users, replacements for inactive owners: __________________
Company / contact / deal relationships and matching method: _________

3. DUPLICATES AND REPEAT RUNS
Matching key for each object: ______________________________________
Action: create / skip / fill empty fields / update agreed values.
Conflict priority and ambiguous matches: ___________________________
Repeat-run behaviour verified on a separate copy: __________________
Do not assume a standard deal CSV import updates existing deals.

4. TRIAL MIGRATION
Include a returning customer, several contacts, empty fields,
an inactive owner, an ambiguous duplicate, a file and an invalid date.
Disable outbound messages and unwanted actions on the verification copy.
Check field values, relationships, roles and continuation of an active deal.
Errors and changes to migration rules: _____________________________

5. RECONCILIATION. COMPLETE SEPARATELY FOR EACH OBJECT
Object: __________  File/batch: __________  Source rows: ____________
Created: ____  Updated: ____  Skipped: ____  Failed: _________________
Explained differences and agreed exclusions: _______________________
Verified key fields and relationships: _____________________________

6. CUTOVER
Source export, backup and verified recovery procedure: _____________
Working source before/after cutover: _______________________________
How changes made after the export will be transferred: _____________
New enquiry and integration checks: ________________________________
Recovery plan accounting for newly created records: ________________

7. ACCEPTANCE
Deliver field map, migration log, errors and repeat-run rules.
Confirm that staff can continue active deals.
Open issues, owners and verification dates: ________________________
Client acceptance decision for the agreed scope: ___________________

Do not put passwords, tokens or customer contact details in a public file.
Agree deliverables, limitations and acceptance for your project.