CRM integration and data migration without a second source of truth
A CRM should not invent a second customer. Migration is a design problem before it is an import problem.
CRM programmes often treat migration as a last-mile import. That is how duplicates, dead opportunities, and conflicting billing addresses become the new normal. The first design question is which system is allowed to be right about which fact.
Identity before fields
Decide how a customer is identified across finance, support, and the new CRM. If you cannot match records, you cannot migrate them. Deduplication rules should be written and tested on a sample, including the ugly matches that a vendor “AI assist” will get wrong.
Move less
Closed-lost from nine years ago, personal notes, and fields nobody can define are expensive to keep. Bring the records that change a conversation this quarter. Archive the rest in a form you can search if legal asks.
Integrate on purpose
- Money stays in finance. The CRM may display a balance; it should not invent one.
- Tickets stay in support unless you have a real reason to merge the objects.
- Product usage belongs in the account only if someone will act on it.
If sales still live in the inbox after go-live, the process was not implemented. The licence was.
Common questions
What are CRM data migration best practices?
Define the system of record for each fact, agree identity and matching rules, test deduplication on real samples, migrate only active and useful records, rehearse the cutover, and archive the remaining history in a searchable form rather than importing it.
How should a CRM integrate with ERP and support systems?
Keep money in finance and tickets in support, and let the CRM display those facts rather than duplicate them. Integrate through APIs or events, decide sync direction and frequency per fact, and reconcile regularly so the CRM never becomes a second source of truth.
This article supports our CRM solutions services. If the situation it describes is familiar, tell us about the systems involved.
