CRM Migration: moving contacts, pipelines and conversation history without losing a lead

A CRM migration moves your contacts, pipelines, deals and conversation history from one system to another without losing a lead along the way. Done properly it is not a copy and paste. It is a plan, a mapping, a test run, a check of every record, and a short handover window where nothing new goes missing.

What do people mean when they search for CRM migration?

We read the fifteen suggestions Google returns for "crm migration" (probed on 13 October 2026, South Africa). Alongside "tool" and "meaning" they include services, project plan, checklist, specialist, software and cost. That is the search of an owner who has already decided to move and is worried about the move itself.

The worry is reasonable. A CRM holds the business's memory: who asked for what, which quote is open, what was promised on the last call. Lose that and the sales team starts the next month cold.

What usually gets lost in a CRM migration?

Contact names and numbers rarely go missing. The things that do are the things that make the record useful:

• Conversation history. Emails, notes and messages that explain why a deal is where it is.
• Pipeline position. A deal that was at "quote sent" lands at the first stage, and nobody follows up.
• Ownership. Which person looks after which client, so replies go to the wrong inbox or nobody's.
• Consent and opt-outs. Who agreed to hear from you and who asked to stop. Losing an opt-out is the expensive one.
• Attachments. Signed quotes, briefs and photos that sat on the old record.
• Duplicates. The same person entered three times in the old system arrives as three people in the new one.

What is a sensible CRM migration checklist?

1. Decide what moves. Not every old record deserves a place. Agree what is active, what is archived, and what is deleted under your retention rules.
2. Take a full backup first. Export everything, including attachments, and keep it somewhere safe before anything is touched.
3. Map the fields. Every field in the old system gets a home in the new one, including pipeline stages, owners and consent status.
4. Clean on the way in. Merge duplicates and fix phone number formats during the move, not after.
5. Test with a sample. Move a small batch, open the records, and check them against the old system by eye.
6. Move, then count. After the full move, the totals in the new system should reconcile with the old one: contacts, deals, notes, files.
7. Freeze and cut over. Pick a short window where new leads go only to the new system, so nothing lands in the old one after the copy.
8. Keep the old system read-only for a while. Switch it off only when the team has worked in the new one and nothing is missing.

What does POPIA expect while you move personal information?

A migration is processing of personal information, so the Protection of Personal Information Act applies to the move itself, not only to the new system. Three sections are worth reading in the Act itself:

• Section 19 requires appropriate, reasonable technical and organisational measures to prevent loss of, damage to or unauthorised destruction of personal information, and to identify foreseeable risks. Exports sitting in an inbox or on a laptop are exactly that kind of risk.
• Section 16 requires reasonably practicable steps to keep personal information complete, accurate and not misleading. A migration that duplicates people or drops opt-outs works against that.
• Section 21 requires a written contract that obliges any operator processing personal information for you to maintain those security measures. If someone else runs the move, that contract matters.

Our post on how to choose a CRM in South Africa covers the POPIA questions to ask of the new system before you commit to it.

How does NexBrand handle the move to one inbox and pipeline?

NexBrand is the omni-channel communications platform we set up and manage for a business: WhatsApp, email, calls, social messages, the pipeline and the automations in one place. When a business moves onto it, the migration is part of the setup, not a job left to the owner.

1. We plan the move with you. What comes across, what is archived, and which pipeline stages and owners map to which.
2. Contacts arrive with their context. History, notes, stage and owner travel with the contact, so a deal at "quote sent" is still at "quote sent".
3. Consent travels too. Opt-outs and preferences come across with the record, so the first campaign from the new system does not message someone who asked to stop.
4. We check before we hand over. Counts are reconciled and records are spot-checked against the old system, then your team works in it before the old one is switched off.
5. New leads land in one place from day one. After cut-over, every channel feeds the same inbox and pipeline, so there is no second system to forget about. Our guide to lead tracking shows the stages that keep a lead moving once it is there.

What changes for the owner?

The first change is that the fear of switching stops being a reason to stay on a system that no longer fits. The second is that the team keeps selling during the move, because the cut-over window is short and planned. The third is one place to look afterwards: conversations, deals and follow-ups on one record instead of spread across the old CRM, a spreadsheet and a few phones.

What does not change is the relationship history. That is the whole point of doing it carefully.

Frequently Asked Questions

How long does a CRM migration take?

It depends on how many records, how much history and how messy the data is. The planning, mapping and test run usually take longer than the move itself. The cut-over window, when the team switches, should be kept short.

Can conversation history be migrated, or only contacts?

History can usually come across too: notes, emails, files and deal stages. Plan for it from the start, because a contact without its history arrives in the new system as a stranger, and the team loses context.

Should we clean the data before or after migrating?

During. Merging duplicates and fixing number formats as records move is easier than tidying a live system afterwards, and it keeps the information complete and accurate, which POPIA section 16 asks of you.

When can we switch off the old CRM?

Only after the counts reconcile, records have been spot-checked, and the team has worked in the new system without missing anything. Keep the old one read-only until then, and keep the backup safe.

Thinking of switching but worried about what gets lost? The free Business Autopsy maps where your conversations and leads live today and what to move first. See how NexBrand puts every channel in one place at nexbdm.co.za.