Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

I want to switch CRM without losing my customer history

Short answer

A CRM move loses data in the joins, not the contacts: links between people, companies and deals, notes and emails, owner names, custom fields, and attachments. Take a full export and a written inventory first, import a small test batch, and keep the old system read-only until the numbers match.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • I want to change CRM but I am afraid of losing years of notes and deal history.
  • A test import created duplicates or deals with no contact.
  • Dates, owners, stages or custom fields came out wrong.
  • Emails, attachments and call notes are not in the export.
  • Forms, invoices and mailing tools are all connected to the old CRM.

Why does this happen?

  1. Records are linked, exports are flat

    A CRM holds people, companies, deals and activities that point at each other. A spreadsheet export is a set of flat files, so the links have to be rebuilt in the right order on the way in.

  2. Different systems, different shapes

    One CRM has pipelines and stages, another has lists and tags. A field that exists in one may have no home in the other, or a different type: a dropdown becomes free text, a number becomes text.

  3. Some data is not in the standard export

    Notes, email history, attachments, call logs and automation rules often need a separate export or an API route, and some cannot be exported at all.

  4. Duplicates arrive with the data

    The same person may appear three times in the old system with slightly different spellings. Imported as they are, they become three records in the new one, and the history is split.

  5. Everything around the CRM is connected to it

    Website forms, booking links, invoicing and email tools write into the old system. If they are not repointed on the day, new leads keep going to the wrong place.

What can I do about it today?

  1. Take a full export now and store it safelyDownload every export the system offers, for every object, and keep a copy outside the CRM. Do not delete anything in the old system.
  2. Count what you haveWrite down the number of contacts, companies, deals, notes and files. These counts are your check afterwards.
  3. List what is connectedForms, email, calendars, invoicing, phone systems and any automations that touch the CRM.
  4. Decide what is worth movingOld, dead leads can stay in an archive file. Moving less makes the check easier.
  5. Ask the vendor what its export leaves outNotes, emails, attachments and custom objects are the usual gaps.

When should I bring someone in?

  • The old system has custom fields, automations or history you cannot export by hand.
  • A test import already produced duplicates or broken links.
  • The old vendor is closing, or the contract ends soon.

How do I handle it?

  1. Inventory firstObjects, fields, types, relationships, owners and connected tools, written down and agreed before anything moves.
  2. Map old fields to newA table of each field, where it goes, and what happens when there is no equivalent.
  3. Clean, then load in orderDuplicates are resolved first. Companies and contacts load before deals, and deals before notes, so each link has something to attach to.
  4. Trial run and reconcileA small batch first, then counts and sample records compared against the written inventory.
  5. Cut over deliberatelyForms and tools are repointed on a set day, and the old system stays readable as a safety copy.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Will I lose my history?

Not if it is exported and mapped, but some history, such as email threads or call recordings, may only move in part. The inventory shows which, before you commit.

Can I run both systems for a while?

Yes, with a short, defined overlap and one clear source of truth at each moment, otherwise the two diverge.

Do I need a developer or can I import it myself?

For a small, simple list your CRM's own importer may do. Linked records, history and custom fields are where help is worth it.

How do I know it worked?

Matching counts, spot-checked records and a signed-off sample from the people who use the CRM every day.

How was this page made?

I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.