Key takeaways
- Plan six to eight weeks: inventory, export, clean, map, test, cut over, then run both systems read-only for a short overlap.
- Export everything, not just contacts: notes, tasks, call and text history, tags, lead sources, deals and consent records.
- Carry over opt-outs and do-not-call flags exactly; Do Not Call registrations must be honored indefinitely or until cancelled[1].
- Test-import a sample of a few hundred records and have agents check their own contacts before the full import.
- Rebuild automations deliberately in the new system rather than copying old drips that nobody reviewed.
What can go wrong in a CRM switch
A CRM holds years of relationships: past clients, sphere contacts, notes from listing appointments, consent records and the reasons a lead went cold. A careless migration loses the context that makes those records valuable. The most common failures are notes that do not come across, tags that collapse into one field, duplicate contacts, broken lead routing on the first weekend and, most seriously, lost opt-out flags that lead to messages being sent to people who asked to stop.
Agents are also slow to adopt a new system if their data looks wrong on day one. Only 46% of REALTORS use a CRM at all, and 63% say the learning curve is their biggest challenge in adopting new technology[2]. A clean migration removes one big reason to give up.
The migration timeline
| When | Work | Owner |
|---|---|---|
| Weeks 1–2 | Inventory data and integrations; decide what moves, what is archived and what is deleted | Project lead with team leads |
| Week 2 | Full export from the old CRM; store a dated archive copy securely | Admin |
| Weeks 2–3 | Clean data: merge duplicates, standardize stages and tags, fix phone and email formats | Admin with agents |
| Week 3 | Field mapping document agreed and signed off | Project lead |
| Week 4 | Test import of a sample; agents check their own records | Admin and pilot agents |
| Week 5 | Rebuild routing, automations and integrations in the new CRM | Admin with vendor |
| Week 6 | Cutover weekend: final export, full import, switch lead sources | Project lead |
| Weeks 7–8 | Old CRM read-only for lookups; fix issues; then cancel | Admin |
Step by step
Inventory what you have
List every object in the old system: contacts, leads, deals or transactions, tasks, notes, call recordings, text history, email history, tags, custom fields, lead sources, automations and users. Then list every integration that sends data in or out: portals, website, phone system, transaction software, email marketing and calendar.
Export everything
Request a full export even if you do not plan to import all of it. Keep a dated, encrypted archive copy that you can search later. Check whether notes, texts and call logs come in the export or need a separate request.
Clean before you move
Merge duplicates, remove junk records and test leads, standardize phone numbers and email addresses, and collapse inconsistent tags such as “Buyer”, “buyers” and “BUYER - hot” into a single agreed list. Cleaning in a spreadsheet is far easier than cleaning in the new CRM.
Map every field
Write down where each old field goes in the new system, how values translate and what happens to fields with no home. Agree it with team leads before anything is imported.
Test with a sample
Import a few hundred records that include tricky cases: contacts with long note histories, couples, past clients with closed deals, and opted-out contacts. Have each pilot agent check five of their own contacts.
Rebuild automations, don't copy them
Review each old drip or action plan. Keep only what still fits, rewrite messages that sound dated, and test each one with an internal contact before switching it on.
Cut over over a weekend
Freeze changes in the old CRM on Friday afternoon, run the final export, import, then re-point lead sources and phone integrations. Test every lead source with a real inquiry on Saturday morning.
Keep the old system read-only briefly
Give agents lookup access for a few weeks while issues are fixed, then cancel and keep the archive.
Field mapping: the part people skip
| Old field | New field | Rule |
|---|---|---|
| Stage: “Hot”, “A lead”, “Active” | Stage: Active | Merge into one stage; keep the old value in a note |
| Tags (free text, 400 variations) | Tags (controlled list of about 40) | Map with a lookup table; unmapped tags go into one “legacy tag” field |
| Lead source | Lead source | Standardize names; keep original source for reporting |
| Notes and call logs | Activity timeline | Import with original dates and author |
| Assigned agent | Owner | Map by email address; reassign leavers' contacts before import |
| Opt-out and DNC flags | Communication preferences | Map exactly; verify every opted-out contact after import |
| Closing date and address | Deal record | Create past-client deals so anniversaries and reporting work |
Use your stage definitions as a chance to fix reporting. If the old system had six overlapping stages, agree a simple set before import. For a model, see lead stages: new, hot, nurture and closed.
Consent and compliance flags
This is the part of a migration that can create real liability. If opt-outs are lost, the new system may start texting or calling people who asked you to stop.
- Move every opt-out, unsubscribe and do-not-call flag, with the date it was set. Registrations on the National Do Not Call Registry must be honored indefinitely or until cancelled[1], and the registry held 259 million active registrations as of September 30, 2025[3].
- Treat replies such as “stop”, “quit”, “end”, “revoke”, “opt out”, “cancel” or “unsubscribe” in old text history as revocations of consent to automated texts[1], even if no flag was set in the old system.
- Bring over consent records for marketing texts and calls, including when and how consent was given.
- Leave automations switched off for imported contacts until opt-out checks are complete.
- Spot-check at least a few dozen opted-out contacts in the new system before the first campaign.
Integrations to reconnect, in order
Lead sources are the obvious integrations, but a CRM usually sits in the middle of many connections. Reconnect them in order of business risk, and test each one with real data before moving on.
- Lead sources: portals, website forms, ad platforms and open-house sign-in tools. A broken connection here loses new business immediately.
- Phones and texting: call logging, missed-call texts, call recordings and any answering service or AI phone assistant that posts summaries to the CRM.
- Calendar and booking links, so appointments created by agents or clients land in the right place.
- Email sync and marketing tools, with suppression lists carried over before any send.
- Transaction management and back office, so closed deals and dates flow into past-client records.
- Reporting dashboards and spreadsheets that pull from the CRM.
Keep a simple log of every integration: what it does, who set it up, which account credentials it uses and when it was last tested. The log is the document most teams wish they had the next time something breaks.
Agents who leave, and agents who join
Migrations expose unresolved questions about who owns contacts. Agents move: the median REALTOR has been with their current firm for six years[4], so over the life of a CRM some agents will leave and others will arrive with their own databases. Decide the rules before import, not after a dispute.
- Reassign contacts belonging to agents who have already left before you import, so leads are not orphaned in the new system.
- Agree in writing which contacts are brokerage or team leads and which are an agent's personal sphere.
- Set permissions in the new CRM to match that policy from day one.
- Give new agents a standard import template, so their contacts arrive clean and correctly tagged.
Example: a 15-agent team's cutover
Example (fictional). A team moving 22,000 contacts finds 4,100 duplicates and 600 test or junk records during cleaning, and reduces 380 tag variations to 35. The test import of 300 records shows that call notes arrive without dates, so the vendor adjusts the import file. On cutover weekend, the team switches four portal sources and the website form, and sends a real test inquiry through each one. One portal is still pointing to the old CRM on Saturday morning; because it was tested, it is fixed before any real lead is lost. The old system stays read-only for three weeks. Agents report missing notes on 14 contacts, all found in the archive and added manually.
Budget the migration honestly
Agents' ongoing technology spending varies widely: 36% of REALTORS spend $50 to $250 a month on technology, 22% spend more than $500, and 18% spend less than $50[2]. A migration adds one-time costs on top of that: admin hours for cleaning and mapping, vendor import fees if any, overlap months when both systems are paid for, and agent time for training. Budget them explicitly so the project is not rushed to save a month's fees.
First-month checklist after go-live
- Every lead source tested with a real inquiry and confirmed in the new CRM.
- Routing rules checked against a week of real leads.
- Opted-out contacts spot-checked; no campaign sent until confirmed.
- Each agent has checked their top 20 contacts and past clients.
- Automations switched on one at a time and monitored.
- Old CRM archived securely, access removed and subscription cancelled on schedule.
- A short post-migration review held to record lessons for next time.
Frequently asked questions
How long does a real estate CRM migration take?
For a team or small brokerage, six to eight weeks is realistic, including cleaning, mapping, testing and a short overlap. Rushed migrations usually lose notes or break routing.
Should we import every old contact?
Import contacts with real relationships and history, and archive the rest. Old junk leads clutter the new system and skew reports.
Will text and call history transfer?
It depends on both systems. Check whether the old CRM exports texts and call logs, and whether the new one can import them with dates. If not, keep them in a searchable archive.
What is the biggest compliance risk in a migration?
Losing opt-out and do-not-call flags, which could lead to messages to people who asked you to stop. Map those fields exactly and verify them before any campaign.
References
Legal Information Institute, Cornell Law School (eCFR text) (2026). 47 CFR § 64.1200 - Delivery restrictions (TCPA rules) (opens in a new tab) ↑
National Association of REALTORS® (2026). REALTORS® Adopt Technology to Save Time and Improve the Client Experience, NAR Report Finds (2026 REALTORS® Technology Report) (opens in a new tab) ↑
Federal Trade Commission (2025). National Do Not Call Registry Data Book, Fiscal Year 2025 (opens in a new tab) ↑
National Association of REALTORS® (2026). Experienced REALTORS® Anchor the Industry as Housing Affordability Remains Top Hurdle (2026 Member Profile) (opens in a new tab) ↑