Key takeaways
- Most CRM switches fail on data and people, not software: plan the mapping, the cut-over and the training as three separate workstreams.
- Protect the data you cannot afford to lose: compliance dates, client money balances, live sales, consents and AML records[1].
- Migrations attract phishing; warn staff before the new-system emails start arriving[2].
- Pick a quiet cut-over date, run test migrations first and keep read-only access to the old system.
Why switches go wrong
Agencies switch CRM for good reasons: the old system is slow, the supplier has stopped developing it, lettings compliance is held in spreadsheets on the side or the contract renewal price has jumped. The new system usually works. The switch fails when data arrives incomplete, when staff do not know how to do their daily tasks on Monday morning, or when a compliance date or a client account balance goes missing in the move.
Treat the switch as three projects that run together. Data: what moves, how it maps and how you check it. Cut-over: when you stop using the old system and start using the new one. People: who needs to learn what, by when. Each needs an owner inside the agency, not just a project manager at the supplier.
The plan on a page
12 weeks before: agree scope
Decide what moves, what is archived and what is left behind. Name an internal project lead and a super-user in each team.
10 weeks before: map the data
Work through every field with the new supplier, deciding where each one goes and what happens to anything that does not fit.
8 weeks before: clean the data
Merge duplicates, close dead applicants and fix missing compliance dates in the old system before export.
6 weeks before: first test migration
Load a full copy into a test version of the new system and check it against agreed samples.
4 weeks before: training starts
Role-based sessions using the migrated test data, so staff practise on records they recognise.
2 weeks before: second test migration
Fix the errors from the first test, rerun it and sign off the results.
Cut-over weekend
Freeze the old system, run the final migration, check the samples and switch portal feeds.
First 4 weeks after: support
Daily check-ins in week one, then weekly, with a list of issues and owners.
Mapping the data
| Data | What to check | Common problem |
|---|---|---|
| Properties and listings | Status, price, descriptions, photos, floor plans, EPCs | Images or documents left behind |
| Applicants | Criteria, position, source, consent | Thousands of dead records copied across |
| Vendors and landlords | Contact details, ID check status, terms signed | ID evidence not linked to the right person |
| Viewings and offers | History and outcome for live listings | Offer history lost for live sales |
| Sales progression | Milestones, solicitors, chain notes | Free-text notes that do not map to new fields |
| Tenancies | Start dates, rent, deposit scheme and reference | Periodic tenancies imported with old fixed-term end dates |
| Compliance dates | EPC, electrical, gas, licences, registration | Dates in notes rather than fields |
| Client accounting | Balances, ledgers, standing orders | Opening balances not reconciled |
| Documents | Signed terms, tenancy agreements, certificates | Files moved but not linked to records |
For every field that does not fit, decide one of three things: map it to a new field, move it into a note, or archive it outside the system. Write each decision down; the supplier will ask again during testing.
Clean, archive or leave behind
A switch is the best chance you will get to clear out years of clutter. Most agencies hold far more applicant records than they use, many without valid consent. Agree rules before export, such as applicants with no activity for two years are archived, not migrated.
Be careful with records you have to keep. Under the Money Laundering Regulations, customer due diligence records must be kept for five years after the business relationship ends or an occasional transaction completes[1]. Archiving is fine, but the records must be retrievable. Keep a secure archive export, with a note of what it contains and who can access it, and apply your retention policy to it.
The data you cannot afford to lose
- Lettings compliance dates. Deposits must be protected within 30 days of receipt[3], electrics checked at least every 5 years[4] and an EPC is valid for 10 years[5]. A missing date can lead to a missed renewal and a penalty.
- Client money. Opening balances in the new system must reconcile exactly to the old system and the bank on cut-over day.
- Live sales and offers. Every agreed sale needs its offer history, solicitor details and progression notes on day one.
- Marketing consent. Preferences must move with each contact. Unsolicited marketing calls must not be made to numbers on the Telephone Preference Service register or to people who have said no[6], so losing opt-outs creates a real risk.
- AML records. ID evidence and risk assessments must stay linked to the right client.
Pick samples for each category, such as twenty tenancies, ten live sales and every client account, and check them by hand after each test migration.
Security during the switch
A migration is a gift to fraudsters. Staff expect emails asking them to log in to a new system, reset passwords and confirm details. 43% of UK businesses reported a cyber security breach or attack in the 12 months covered by the 2025/26 survey, and phishing was the most common, experienced by 38%[7][2]. 83% of businesses in the administration or real estate sector group said cyber security was a high priority[8].
- Tell staff in advance exactly which emails they will receive, from which address and when.
- Turn on multi-factor authentication for every account on day one.
- Never send exports by email; use the supplier's secure transfer method.
- Remove old-system access for anyone who has left, and set the old system to read-only after cut-over.
Choosing a cut-over approach
- Big bang: everyone moves on one date. Simple, and the usual choice for single-branch agencies. Choose a quieter period, avoiding month-end rent runs and the busiest weeks for completions.
- Phased by branch: one branch moves first, others follow. Lower risk for larger groups, but reporting is split for a while.
- Parallel running: both systems used for a period. Rarely worth it; staff double-key, and the two systems drift apart quickly.
Whatever you choose, agree a freeze: from a set time, no changes are made in the old system. Anything that happens during the weekend migration is recorded on paper or in a shared log and entered into the new system once it is live.
Training that sticks
- Train by role: negotiators, property managers, accounts and managers need different things.
- Use real migrated data, so staff practise on properties and applicants they know.
- Give each team a super-user who has extra training and answers questions first.
- Write a one-page 'how do I' sheet for the ten most common tasks in each role.
- Schedule a refresher two weeks after go-live, when people know what they do not know.
Integrations and the outside world
A CRM rarely works alone. Portal feeds, your website, telephony, ID checks, e-signing, accounting and texting services all connect to it, and each connection has to be moved. List every integration before the project starts, with who owns the account and how it is configured. Some, such as portal feeds, need the portal's own team to switch the source on a set date; others need new API keys or webhooks.
Tell the outside world too. Landlords may need new log-in details for their portal, tenants may receive rent reminders from a new address and contractors may be sent jobs in a new format. A short notice to each group a week before go-live, explaining what will change and what will not, prevents a flood of calls on Monday morning.
Example: a weekend cut-over
Example. A three-branch agency switches on a weekend in late January. The old system is frozen at 5pm on Friday and the final export runs that evening. On Saturday the supplier loads the data while the project lead and two super-users check samples: every client account balance, every live sale and fifty tenancies. Portal feeds switch on Sunday afternoon. On Monday the team starts with a fifteen-minute briefing, super-users sit with each team and a shared issues log collects problems. By Friday, the log has thirty-four items, all but three resolved.
The three that remain are all data issues found in the samples: two tenancies with the wrong deposit scheme reference and one landlord whose bank details did not transfer. Because the old system is still available read-only, each is fixed from the original record within a day, and the agency adds the missing checks to its notes for the next migration.
Frequently asked questions
How long does it take to switch estate agency CRM?
A typical plan runs about three months from agreeing scope to cut-over, with data mapping, cleaning, two test migrations and role-based training, followed by around four weeks of support.
What data is most at risk in a CRM migration?
Lettings compliance dates, client money balances, live sales and offers, marketing consents and anti-money laundering records. Check samples of each after every test migration.
Should we migrate every applicant record?
Usually not. Agree rules to archive inactive applicants, especially where consent is unclear, while keeping any records you are legally required to retain.
Is it better to run the old and new CRM in parallel?
Rarely. Parallel running means double entry and the systems drift apart. A planned cut-over with a data freeze is usually safer.
References
legislation.gov.uk (The National Archives) (2017). The Money Laundering, Terrorist Financing and Transfer of Funds (Information on the Payer) Regulations 2017, regulation 40 (opens in a new tab) ↑
Department for Science, Innovation and Technology (GOV.UK) (2026). Cyber security breaches survey 2025/2026 (opens in a new tab) ↑
GOV.UK (2026). Deposit protection schemes and landlords: Overview (opens in a new tab) ↑
Ministry of Housing, Communities and Local Government (GOV.UK) (2025). Electrical safety standards in the private and social rented sectors: guidance (opens in a new tab) ↑
GOV.UK (2026). Selling a home: Energy Performance Certificates (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2019). The Privacy and Electronic Communications (EC Directive) Regulations 2003, regulation 21 (opens in a new tab) ↑
Department for Science, Innovation and Technology (GOV.UK) (2026). Cyber security breaches survey 2025/2026 (opens in a new tab) ↑
Department for Science, Innovation and Technology (GOV.UK) (2026). Cyber security breaches survey 2025/2026 (opens in a new tab) ↑