Blog

Switching CRMs without losing your lead history

· SyncYak team

  • crm-sync
  • crm-migration
  • google-sheets

Most teams only think about their lead data when they are about to leave the system that holds it. The new CRM is chosen, the old contract is ending, and someone asks whether anything important will be lost in the move. The honest answer is usually "some of it", because the import tool moves what it was built to move and nothing else.

This post is a practical plan for switching CRMs, or running two side by side during a move, without depending on either vendor for the one thing you cannot rebuild: your lead history.

What a CRM import usually misses

An import brings over names, emails and phone numbers. The parts that are harder to recreate are the ones that explain how a lead behaved:

  • the original lead source, such as which portal or campaign sent it
  • the stage history and the dates a lead moved between stages
  • the agent who owned the lead at each point
  • tags and custom fields, including scores and pre-approval status
  • deleted or merged records that still show up in old reports

Each of these feeds the report you will want six months from now, such as which source produced closings or how long leads waited for a first touch. If they are not in your own storage before the switch, you are relying on the old vendor's export, on a date you do not control.

Step 1: take a copy before you decide anything

Start the copy while you are still evaluating the new CRM. A copy that has been filling for a month gives you something to check the import against.

Pick the destination by who needs to read the data:

  1. Google Sheets if the readers are agents, assistants or a lender partner. Everyone can filter it without a CRM seat.
  2. Postgres or MySQL if you have a developer, a BI tool or a warehouse. You can join leads to transactions and marketing spend.

Either way, the shape matters more than the tool. Keep one row per lead, keyed by the CRM's own lead id, and never reorder or delete rows. A lead deleted in the CRM should get a timestamp in a column, not disappear, so your history stays complete.

Step 2: add your own columns

Anything you add to the copy stays yours. A few columns that pay off later:

Column Why it helps
legacy_id The old CRM's id, so you can trace a lead after the move
first_source The source on day one, before anyone edits it
score Your own score, independent of any CRM feature
migrated_to Which CRM now owns the lead, if you move in waves

Because these live in your sheet or database, they survive whichever CRM you use next.

Step 3: if you run both CRMs, match on email or phone

Teams rarely switch overnight. Agents move in groups, or two merged teams keep their own systems for a quarter. During that time the same person can exist in both CRMs.

Sync both into one shared tab or table, with each row tagged by its CRM, then match people on email or phone in a query or a spreadsheet formula. For example, in SQL:

SELECT lower(email) AS email,
       count(DISTINCT crm) AS crms,
       min(created_at) AS first_seen
FROM all_leads
WHERE email <> ''
GROUP BY lower(email)
HAVING count(DISTINCT crm) > 1;

This tells you which leads are in both systems, which one you saw first and which still need to be moved. You decide the rules: which CRM wins for a field and what counts as the same person.

Step 4: write the values you care about into the new CRM

Once the new CRM is live, the columns you built, such as a score or a pre-approval status, can go back onto the lead record by mapping each column to a custom field. Only new or changed rows are sent, and an empty cell leaves the CRM field alone, so a half-filled sheet will not wipe out good data.

Be clear about what this does not do. Writing values onto leads that already exist is not the same as migrating contacts, notes and activity history from one CRM to another. For that, use the vendors' own import tools or ask the new vendor for a written migration plan. Use your copy to check the result afterwards: compare row counts, sources and stages, and look at the leads that did not arrive.

A short pre-switch checklist

  • Start the copy at least a few weeks before the cutover.
  • Confirm the lead count in the copy matches the CRM's own count.
  • Add legacy_id and first_source columns before the import.
  • Export the custom field definitions, not just the values.
  • After the import, compare sources and stages between the copy and the new CRM.
  • Keep syncing the old CRM until the last agent has moved.

How SyncYak helps

SyncYak CRM connects Follow Up Boss, Lofty, BoldTrail, CINC, HighLevel, Cloze, Brivity and KW Command to a Google Sheet or to your own Postgres or MySQL. Every lead is written as one row, updated in place by its CRM id, and a lead deleted in the CRM is marked with a time instead of being removed. Your own columns are never written to.

Writing values back onto the CRM record works with Follow Up Boss, Lofty, HighLevel and Cloze; the other connectors sync one way, into your storage. The free plan includes 1 CRM connection and 100 leads per batch every 60 minutes. Paid plans start at $29 a month for 2 connections, 1,000 leads every 30 minutes and field mapping back to the CRM, which is what you need to run two CRMs side by side. See the pricing page for the full ladder.

For the two-CRM case in detail, read Follow Up Boss to Lofty: keep both in sync. To fill CRM fields from a sheet, see lead enrichment in Google Sheets. The product overview is on the CRM page.

Start the copy today, before you need it: create a free account and connect your current CRM.

Start free with SyncYak · All posts