Before migrating a CRM: sort out duplicates without losing history
Similar records may belong to different customers. Agree the matching rules, move the linked activities, files and owners, and keep a record of the old and new IDs.

The workflow illustrates a possible design and is not a client case study.
- Identify matching customers
- Review and transform
- Reconcile import
When similar records should stay separate
One customer may use several email addresses; branches may share a company name. A match on name or phone alone can combine unrelated customers. While reviewing duplicates, keep track of each customer's owner, activities and attachments so staff can still follow the history in the new CRM.
How does the new CRM identify duplicates?
Check how the destination CRM handles duplicates. HubSpot’s rules vary with the record type and import method. Prepare or transform the source data where its identifiers and historical links do not fit those rules.
Try merging a small sample
Try the matching rules on a small sample. Process clear matches, send uncertain cases for review and retain records that must stay separate. Keep the reason for each merge, the old and new IDs and any rejected imports. Before the live import, make a restorable backup and agree how later updates will avoid recreating the duplicates.
Check that history and attachments follow
Compare record counts before and after the import, then inspect a few customers' owners, activities, attachments and full histories. Import the same file again to check that it does not create duplicates. When reviewing uncertain matches, staff need to see why records were merged and how a mistaken merge can be corrected.
Bring examples that must stay separate
Bring exports with personal information removed, field mappings and existing record IDs. Include examples of similar-looking customers who must remain separate.