---
type: "Blog Post"
title: "CRM migration checklist | Roicool"
description: "A checklist for moving to a new CRM without losing data: inventory, mapping table, data cleanup, test import, integrations and validation, step by step."
url: "https://www.roicool.com/en/blog/crm-migration-checklist"
lang: "en"
dateModified: "2026-10-20"
author: "Zehra Adaş"
resource: "https://www.roicool.com/en/blog/crm-migration-checklist"
alternates:
  tr: "https://www.roicool.com/blog/crm-migrasyon-kontrol-listesi.md"
generated: { by: "process:roicool-cms", at: "2026-10-20T15:58:59.777Z" }
related:
  - { title: "How to choose a CRM: an 8-question decision guide for B2B companies", resource: "https://www.roicool.com/en/blog/how-to-choose-crm.md" }
  - { title: "Google Ads offline conversion tracking: tying CRM sales back to your ads", resource: "https://www.roicool.com/en/blog/google-ads-offline-conversion-tracking.md" }
  - { title: "Zoho CRM setup, step by step", resource: "https://www.roicool.com/en/blog/zoho-crm-setup.md" }
sources:
  - { id: "1", resource: "https://knowledge.hubspot.com/import-and-export/import-objects", title: "HubSpot Knowledge Base, Import records for multiple objects" }
  - { id: "2", resource: "https://www.mevzuat.gov.tr/mevzuatmetin/1.5.6698.pdf", title: "Law No. 6698 on the Protection of Personal Data (KVKK)" }
---

# CRM migration checklist: moving to a new CRM without losing data

A safe CRM migration has five stages: an inventory of existing data and processes, a field-by-field mapping table, cleanup, a small test import, and a final import with validation. Automations and integrations are rebuilt separately from the data, and the old system is not shut down until the new one is validated.

- Migration is not a copy job; it is a reorganization of data and processes.
- The mapping table records each field's source, target and transformation rule.
- Clean up before migrating; dirty data stays dirty in the new system.
- First a small test import, then a freeze date and the final import.
- Automations, integrations and reports do not move with the data; they are rebuilt.

CRM migration means moving your contact, company, deal and activity records, the associations that link them, and your business processes from one CRM to another. The hard part is not the data itself but moving it without breaking the associations and rules. The checklist below walks through a migration from start to finish, in order.

## 1. Inventory: what do you have?

The first step is to map what is in the old system and what is actually used.

- \[ \] Objects: contacts, companies, deals, quotes, products, activities, notes, files, custom objects.
- \[ \] Record count and last-updated dates for each object.
- \[ \] Fields: which are populated, which have never been used.
- \[ \] Sales pipelines and stages.
- \[ \] Automations, workflows, assignment rules.
- \[ \] Integrations: web forms, ad platforms, email, phone, ERP, analytics.
- \[ \] Reports and dashboards: which reports does management look at?
- \[ \] Users, roles and permissions.

## 2. The mapping table

The mapping table is the contract of the migration: it states where each field in the old system goes in the new one and how it is transformed.

| Old object.field | New object.field | Type | Transformation rule | Note |
| --- | --- | --- | --- | --- |
| Lead.Source | Contact.Lead source | Picklist | "Web" → "Web form" | Value list merged |
| Account.Industry | Company.Industry | Picklist | 24 old values → 9 new values | Mapping on a separate tab |
| Opportunity.Stage | Deal.Stage | Picklist | Stage mapping | Based on the new pipeline definition |

- \[ \] Source, target, type and rule written for every field.
- \[ \] Picklist values mapped one by one.
- \[ \] Record owners (users) mapped to users in the new system.
- \[ \] Unique ID field defined (the old system's ID is kept in a field in the new system).
- \[ \] Associations defined: contact–company, deal–company, activity–contact.

## 3. Cleanup

Dirty data stays dirty in the new system; clean up before you migrate.

- \[ \] Duplicate contacts and companies merged.
- \[ \] Invalid emails and phone numbers flagged.
- \[ \] Formats standardized: country, phone, company name.
- \[ \] Decision made for records untouched for a long time: migrate, archive or delete.
- \[ \] Contacts without marketing consent flagged (consistent with KVKK and İYS records, Turkey's data protection law and commercial message consent registry).

## 4. Test import

Before the big import, try it with a small, representative sample.

- \[ \] A sample of a few hundred records from each object selected.
- \[ \] Sample imported into a sandbox or a separate trial account.
- \[ \] Associations, owners, dates and picklists checked.
- \[ \] Someone from the sales team tried their daily work with the sample records.
- \[ \] Errors found were fed back into the mapping table.

## 5. Final import

- \[ \] Freeze date shared with the team: no records are entered in the old system after this date.
- \[ \] Full backup of the old system taken.
- \[ \] Import order: users → companies → contacts → deals → activities and notes.
- \[ \] Record counts compared object by object.
- \[ \] Randomly selected records checked field by field.

## 6. Rebuilding processes

Automations, assignment rules, email templates, reports and integrations do not move with the data; they are rebuilt in the new system. This is also a chance to simplify old rules.

- \[ \] Web forms connected to the new CRM; a test lead came through.
- \[ \] Ad platform lead integrations and [offline conversion](https://www.roicool.com/en/blog/google-ads-offline-conversion-tracking) uploads moved to the new system.
- \[ \] Assignment rules and automations set up and tested.
- \[ \] Management reports rebuilt and compared with the old system.

## 7. Go-live and after

- \[ \] Team training held before go-live day.
- \[ \] A support channel opened for the first two weeks.
- \[ \] Old system left read-only; shutdown date set.
- \[ \] Retention period for the old data documented together with KVKK obligations.

## The most common mistakes

The most expensive mistakes are lost associations (deals left without a company), all record owners being assigned to a single user, and picklist values migrated without mapping. All three are prevented by the mapping table and the test import.

If you want to plan the migration together, our [CRM migration](https://www.roicool.com/en/services/crm-migration) service covers this entire list; if you are still choosing the new CRM, start with [how to choose a CRM](https://www.roicool.com/en/blog/how-to-choose-crm). Our overall approach is on our [CRM consulting](https://www.roicool.com/en/services/crm-consulting) page.

## Sources

1. [HubSpot Knowledge Base, Import records for multiple objects](https://knowledge.hubspot.com/import-and-export/import-objects), 2026
2. [Law No. 6698 on the Protection of Personal Data (KVKK)](https://www.mevzuat.gov.tr/mevzuatmetin/1.5.6698.pdf), 2016

## FAQ

### How long does a CRM migration take?

It depends on the number of records, the number of objects (contacts, companies, deals, activities, custom objects) and the integrations. A migration with one pipeline and the standard objects can be done in a few weeks; migrations with many custom fields, automations and integrations take longer. What shortens the timeline most is a complete mapping table from the start.

### Can old emails and activities be migrated?

Most CRMs let you import activities, notes and email records, but formats and association rules vary from tool to tool. Decide which history you really need: moving everything takes longer and carries old, dirty data into the new system.

### Can the sales team keep working during the migration?

Yes, but you need to set a freeze date. For a short period before the final import, records are updated in one system only; then the final import runs and the team moves to the new system. Entering data in two systems in parallel leads to inconsistencies.

### When should I shut down the old CRM?

After validation is complete and the team has worked in the new system for at least one full sales cycle or a reasonable period. Before shutting it down, take a full export of the old system and document the retention decision together with your KVKK (Turkey's personal data protection law) obligations.

Breadcrumb: [Home](https://www.roicool.com/en) › [Blog](https://www.roicool.com/en/blog) › [CRM](https://www.roicool.com/en/blog/category/crm) › CRM migration checklist: moving to a new CRM without losing data

Related pages:

- [How to choose a CRM: an 8-question decision guide for B2B companies](https://www.roicool.com/en/blog/how-to-choose-crm)
- [Google Ads offline conversion tracking: tying CRM sales back to your ads](https://www.roicool.com/en/blog/google-ads-offline-conversion-tracking)
- [Zoho CRM setup, step by step](https://www.roicool.com/en/blog/zoho-crm-setup)

Source: https://www.roicool.com/en/blog/crm-migration-checklist · Last updated: 2026-10-20