"I've done the whole transfer over to CRMs a couple of times and it sucks." An operator said that to me on a call, and I hear the same worry on a lot of calls. The fear is specific: "I don't wanna lose the history." So they stay on a tool that no longer fits, because leaving feels riskier than staying.
You can switch real estate CRM without losing leads. It takes a real estate CRM migration checklist, not luck: export everything before you cancel, move your opt-out list first, port your numbers the safe way, and run both systems side by side until the counts match.
I run a wholesale operation, and I built ForesightCRM, so read this knowing we sell one of the places you might move to. The checklist below is vendor-neutral and works for any move. Foresight specifics are in their own section at the end, including what does not import today.
Why switching CRMs loses leads
Leads rarely disappear in one big failure. They leak out through small gaps during the move:
- History left behind. The notes, texts, and call logs that tell you a seller's situation stay in the old account after you cancel.
- Someone else owns the login. One operator told me they were locked out of an account someone else controlled and lost about 400 leads overnight.
- Opt-outs that do not come along. A new system that has never heard "stop" will happily text the people who said it.
- Numbers canceled too early. Kill the old phone service before a port finishes and the number sellers know can be gone.
- Double texting. Old drips keep firing while new cadences start, and a seller hears from you twice in one afternoon.
- Sunk training time. SOPs, scripts, and habits built around the old screens have to be rebuilt, and a custom build can break when the person who made it leaves.
There is also a question buyers ask me directly: "Will the owner still be doing this in more than a year?" A good migration plan protects you either way, because you keep your own exports.
If you are still choosing where to go, start with our shortlists of REsimpli alternatives, Podio alternatives, GoHighLevel alternatives, and Salesforce alternatives.
Export everything before you cancel
| Export this | Why it matters |
|---|---|
| Contacts and leads, with every phone and email | The number that answers is not always the first one |
| Properties, lists, and tags | Tags are how you rebuild lists like "probate" or "auction in 30 days" |
| Pipeline stages and statuses | A seller under contract must not land back in "new lead" |
| Notes and tasks with due dates | Callbacks you promised live here |
| Text and call history, plus recordings | Context for every live conversation, and a record of consent and opt-outs |
| Documents and contracts | Signed agreements you may need later |
| Buyers list | Your dispo depends on it |
| Opt-out, DNC, and litigator flags | The one list that must come with you, covered next |
| Scripts, templates, and automation steps | Screenshots are fine; you will rebuild them |
Export options vary by tool, so find out early what yours can export in bulk. Ask the new vendor what they help with, too. BatchLeads' pricing page advertises unlimited imports in the first month for people moving from similar products, and Follow Up Boss lists help importing contacts from your current CRM on its Pro and Platform plans.
Save the raw export files untouched, and write down the row counts, before you cancel anything. Illustrative scene, not a ForesightCRM screenshot.
Bring your opt-out list first
This is the step that turns a messy migration into a legal problem. Under the FCC's rules in 47 CFR 64.1200, a reply of "stop," "quit," "end," "revoke," "opt out," "cancel," or "unsubscribe" revokes consent, and the request must be honored within ten business days. The same section's company do-not-call rules say a do-not-call request is honored for five years, and that a business is liable even when someone else keeps the list for it.
Which of those rules applies to your outreach is a question for your lawyer. What is not in question: none of them reset because you changed software.
A practical order that works in any system:
- Export opt-outs from every source: stop replies, DNC tags, litigator flags, and "wrong number" dispositions.
- Scrub those numbers out of every import file so they never land as textable phones.
- Load the suppression list into the new tool before you import leads.
- Test one blocked number for both texts and calls. Some tools block by channel, and a call-only block leaves a person textable.
Own the account, then port your numbers
Here is how to own the account and port phone numbers to a new CRM without losing them.
Own the login. The operator who lost 400 leads did nothing wrong on the phone. They just did not control the account. Put the new account in your name, with your email and your card, and give team members their own seats.
Keep the old service active. Twilio's porting guidance says not to close your account with your current carrier until the numbers finish porting. Cancel early and you can lose the number.
Gather the paperwork. Twilio's US porting guidelines list a letter of authorization, the name and address on your carrier's customer service record, a bill from the last 30 days, your account number, and a PIN if your provider uses one. They name mismatched name or address as the most common reason a port is rejected.
Plan for the timeline. Federal rules in 47 CFR 52.35 require carriers to complete a simple port within one business day and a non-simple port within four, once a complete request is in. In practice the paperwork takes longer: Twilio says standard ports typically take 5 to 15 days and can run to 4 weeks or longer, and bulk ports of more than 50 numbers take 4 to 6 weeks.
Register 10DLC in the new system. A ported number cannot text until it is attached to an approved campaign. Twilio's error 30034 is what happens otherwise: messages from a 10DLC number with no approved campaign are blocked. Start registration in week one. Our 10DLC registration guide covers the steps.
One judgment call: port the numbers sellers recognize, like the one on your signs, mail, and past threads. If a cold-outreach number was already getting flagged, a fresh number in the new system may serve you better than moving a tired one.
The numbers worth porting are the ones sellers already know from your signs, mail, and past threads. Illustrative scene, not a ForesightCRM screenshot.
A migration timeline to switch real estate CRM without losing leads
| When | Old system | New system |
|---|---|---|
| Week 0 | Check term and renewal date; full export; note row counts | Create the account in your name |
| Week 1 | Keep running as normal | Load opt-outs, import leads with outreach off, submit ports, start 10DLC |
| Weeks 2 and 3 | Pause drips for moved leads; use it for lookups only | Start outreach in small batches; team works here daily |
| Week 4 | Final export; cancel after ports complete | Reconcile counts; fix anything missing |
Twilio says standard ports typically take 5 to 15 days and can take up to 4 weeks or longer, and bulk ports of more than 50 numbers take 4 to 6 weeks, so keep the old service on until every port completes.
Show the numbers
| Starts | Ends | |
|---|---|---|
| Week 0: export, own the account | 0 days | 7 days |
| Week 1: opt-outs, import, ports | 7 days | 14 days |
| Typical port: up to 15 days | 7 days | 22 days |
| Slow port: 4 weeks or longer | 7 days | 35 days |
| Weeks 2 and 3: run both systems | 14 days | 28 days |
| Week 4: reconcile, then cancel | 28 days | 35 days |
| Old phone service stays on | 0 days | 35 days |
Source: Twilio US porting guidelines, checked September 17, 2026; weeks from the plan above
Pause the old automations the day leads go live in the new system. Skip this and the same seller hears from both systems. Turn off drips, auto-responders, and scheduled campaigns in the old tool, not just the new ones.
Reconcile before you cancel. Compare these numbers between the old export and the new system:
- Total leads, and leads by stage
- Deals under contract and open callbacks
- Phone numbers per lead, since secondary phones drop easily
- Opt-outs and DNC flags
- Buyers on your dispo list
Train the team in one sitting. Record a 30-minute walkthrough of the daily workflow, write one short SOP, and name one person who answers "where did this go?" questions for the first two weeks. Include where the do-not-call list lives: the FCC's company do-not-call rules expect telemarketing staff to be trained on it.
How to switch real estate CRM without losing leads in Foresight
Imports. The CSV importer has source presets that pre-map columns for NicheData, County Records, PropStream, BatchLeads, Foreclosure Attorney, Cold Call List, SMS List, Facebook / Meta, Google Ads, Direct Mail, Website & Hot Leads, and Pay Per Lead (PPL). There is no preset for another CRM's export, so use "Other CSV" and map columns: names, up to ten phones and five emails, mailing address, property and foreclosure fields, lead source, status, notes, and tags. A status column maps when its values match our statuses; anything else lands on the default status you pick, so match your stages in the file first.
Duplicates. You choose "Skip exact duplicates" (recommended), "Import all, flag duplicates for review," or "Update existing records." A completed import can be undone from the import history.
That setting shows for users with permission to enroll cadences, so have the account owner or an admin run the import.
Opt-outs. Scrub opted-out numbers out of your files before you import them. If you need to keep a record for someone who opted out, use "Block all numbers" on the lead to stop calls and texts before any outreach starts. Going forward, Foresight honors carrier stop keywords and plain-language opt-outs like "take me off your list."
What does not come over. One Notes column per lead imports. Text threads, call logs, recordings, tasks, and dated note history from another CRM do not import automatically today. Keep your exports, and keep the old account open for lookups during the parallel run.
Numbers. Under Settings, Phone Numbers, "Port in a number" asks for the number, current provider, account number, port-out PIN, billing name and address, and your letter of authorization. Our team files the carrier port, which usually takes 1 to 4 weeks, and your current service must stay active until it completes. When the number lands, it is attached to your account and enrolled in your texting registration. Cold first texts still wait for your own 10DLC approval, while calling works before approval.
Leaving later. The Leads page exports to CSV, with do-not-call and dead numbers either excluded or included and flagged. You should be able to leave any tool, including ours, with your data in hand. If you are weighing us against where you are now, Foresight vs REsimpli is the head-to-head.
The bottom line
A switch goes wrong in the gaps: history left behind, opt-outs that did not move, numbers canceled early, and old drips still firing. Close those gaps in order and you can switch real estate CRM without losing leads, or the history that goes with them.
Do the exports first. Then start the trial, so the two weeks go to the parallel run instead of cleanup. Foresight's 14-day trial starts with a card, nothing is charged until it ends, and billing is month to month or annual.
ForesightCRM is our product. Foresight import, port-in, and export details are from the live product as of September 17, 2026. Legal citations are from eCFR (47 CFR 64.1200 and 52.35), and porting and 10DLC details are from Twilio's public documentation and BatchLeads and Follow Up Boss pricing pages on the same date, linked above. This is not legal advice. If something has changed, tell us and we will correct it.