How to switch CRMs without wrecking your database

Plenty of agents stay on a CRM they’ve outgrown for far longer than they should, and the reason is almost never the software. It’s the migration. Specifically, it’s a vague fear that something irreplaceable will be lost in the move, and that fear is reasonable, because occasionally it is.

Here’s the version that works, in order.

What should you export first?

Everything, today, whether or not you’re switching. Export your contacts from whatever you currently use, download the file, and put it somewhere that isn’t the CRM: a folder on your machine, a cloud drive, or both.

You want this file regardless. It’s your insurance against the vendor going out of business, getting acquired and shut down, changing pricing in a way you hate, or locking your account over a billing problem at the worst possible moment. All four of those happen.

Export three things, not one:

• Contacts with every column. Many CRMs export only the columns you have on screen unless you ask for all of them. Ask for all of them.
• Your unsubscribe and do-not-text lists, as their own files. More on why below.
• Anything you’d hate to rebuild from memory: a screenshot of each automation’s steps, your lead routing rules, your templates.

If your current CRM makes this hard, and export is a support ticket rather than a button, write that down. It tells you what the cancellation experience is going to be like.

What moves cleanly, and what doesn’t?

Data moves. Logic doesn’t. Here’s the field-by-field version.

Email threads are the one that alarms people. Most CRMs don’t own your email; they sync your mailbox. The fix is usually to connect the same mailbox to the new system and let it sync again. Don’t panic if the first import looks thin here.

Logic is where the real work is, and it’s also an opportunity. Automation setups accumulate for years, and most contain a sequence nobody remembers writing and one that’s been sending something embarrassing for longer than anyone would like. Rebuilding is a chance to keep only what’s working.

What about unsubscribes and texting opt-outs?

Move them before you send anything. The obligation to honor them belongs to you, not to whichever software you use.

For email, the FTC’s CAN-SPAM compliance guide says “you must honor a recipient’s opt-out request within 10 business days,” and each email in violation is subject to penalties of up to $53,088. An opt-out recorded in your old CRM doesn’t stop being an opt-out because you changed systems.

For texts and calls, the FCC’s TCPA rules (47 CFR 64.1200) say a request to revoke consent must be honored “within a reasonable time not to exceed ten business days,” and a do-not-call request “must be honored for 5 years from the time the request is made.” Keep your records of who agreed to receive texts, too. If you ever need to show consent, the old system’s history may be the only proof.

In practice:

1. Export the unsubscribe, do-not-email and do-not-text lists as separate files.
2. Before any campaign or automation runs in the new system, make sure those people are marked so they’re excluded.
3. If the new system has no way to mark them, leave them out of any bulk or automated messages until it does.

This isn’t legal advice. Check with your broker or attorney if you’re unsure how the rules apply to your lists.

What order avoids the pain?

Set up, check, rebuild, repoint, overlap, then cancel. In that order.

1. Set up the new system and import. Don’t cancel anything. Don’t repoint anything. Just get the data in and look at it.

2. Check the import properly. Not “does it look about right.” Pick fifteen contacts you know well (a past client, someone mid-transaction, someone with a long history) and check each one field by field. Import problems are systematic. If one contact’s phone number landed in the notes field, they all did, and you want to find that on day one rather than in month three.

3. Rebuild the automations you actually use. Look at what fired in the last 90 days in your old system. Rebuild those. Ignore the rest until you miss them, which you mostly won’t.

4. Repoint lead sources one at a time. This is the step people rush and regret. Your website forms, your portal accounts, your ad platforms, your integrations: each one goes over individually, and you confirm a test lead actually arrives before moving to the next. Portals that send leads by email are often the easiest, because you only change where the email goes.

5. Run in parallel for two to four weeks. Both systems live. New leads go to the new one; you keep the old one open and readable. It costs one extra month of a subscription you’re about to cancel, and it’s the cheapest insurance in the whole process.

6. Then cancel. After you’ve exported again from the old system, with the final state of everything.

How long does a migration take?

For a solo agent, about a month from start to cancel, with an afternoon or two of real work in it.

One thing to plan around: trials are short. Follow Up Boss and Wise Agent each offer a 14-day free trial, which is less time than a proper parallel run. Either import on day one of the trial so the decision is informed, or test with a free plan that doesn’t expire.

For a team, add a week and a real conversation about who owns what, because permissions and record ownership are where team migrations get complicated. That’s not a data problem. It’s an agreement problem, and it’s better solved before the import than after. Decide, too, who is allowed to export the database once it’s in the new system.

What should you check in the first two weeks?

That leads arrive, that nothing sends that shouldn’t, and that people are working from the new system.

• A test lead from every source has landed, with its source and details intact.
• No automation has messaged anyone on your opt-out lists.
• Email is syncing, and replies from clients land on their records.
• Your calendar shows the right appointments.
• Birthdays and home anniversaries imported with the right dates.
• Everyone on the team has logged in and worked a lead in the new system.
• Nobody is quietly still using the old one “just for now.”

What do people forget?

Your calendar and email connection. Reconnecting these is usually five minutes, but if you skip it, the new CRM looks broken and empty and you’ll conclude the migration failed when you just didn’t plug it in.

Telling anyone who needs to know. If you work with a transaction coordinator, an assistant or a team, they need warning and about twenty minutes of orientation. A migration that surprises your coordinator mid-closing goes badly for reasons that have nothing to do with software.

The anxiety is out of proportion to the work. The database is the part that moves cleanly. It’s the rules and the habits that take time, and those were going to need revisiting anyway.

If you want to try this against ours, Workspace Free costs nothing and has room for 100,000 contacts. Import takes a CSV of up to 10,000 rows per file, matches the columns for you with a preview, and skips rows that match an existing email or phone. Lead emails from Zillow, Realtor.com and other sites that email you leads can be forwarded to your workspace’s private address, which makes step 4 a matter of changing where emails go; the Lead Inbox shows how. You can look at your whole database properly and decide without cancelling anything, and our comparison of Follow Up Boss alternatives covers the other options.