How to switch CRMs at a Dubai brokerage without losing leads, listings or agent trust

Before you touch anything: should you switch at all?

Migration costs time, double licences and some agent goodwill. Ask first whether the problem is the tool or the habit. If agents do not log calls in the old CRM, they will not log them in the new one. If the gap is a missing layer such as a shared WhatsApp (messaging app) inbox or an owner report, a layer added to the current CRM may fix it without moving anything. My comparison of the options is in PropSpace alternatives for Dubai brokerages.

Do not switch while many deals are in transfer, or during a launch. Commission risk is highest when records are in motion.

What you stand to lose, and what usually does not transfer

• Activity history: call logs, emails and notes often do not come across cleanly.
• Tags, automations and integrations: these are usually rebuilt by hand.
• Leads sitting in portal dashboards: PropSpace, a Dubai real estate CRM, says its import brings live Property Finder listings and up to 90 days of leads directly, and that leads from other portals are not imported. Property Finder is a major UAE property portal.
• WhatsApp history: usually lives on agents' phones, not in the CRM. See WhatsApp CRM for Dubai brokerages.
• Deep history: PropSpace itself says how much transfers depends on what the old system can export.

Step 0: read the exit terms of both vendors before you sign

This is the step no ranking page covers. Before you sign with the new vendor, and before you give notice to the old one, get these in writing:

1. Export format and scope: leads, contacts, listings, notes, activities, documents, chat logs.
2. Who owns the data and any export fee.
3. Notice period and minimum term. PropSpace publishes a 12-month minimum term; other vendors do not publish theirs.
4. How long data stays available after you cancel, and whether API access (the way other software connects to the CRM) continues.
5. What the new vendor will import and what you must supply. PropSpace says it needs clean, de-duplicated templates from you.

BeHomes' export terms are not public that I could find, so ask. If you are moving from spreadsheets, see real estate lead spreadsheet management first.

Audit and clean your data: a Dubai-specific checklist

1. List every place data lives: CRM, portal dashboards, spreadsheets, agents' phones, email.
2. Count records by type, status, source and agent. Write the numbers down. You will compare them at the end.
3. Merge duplicates. The usual test is the same mobile number in international format (+971), not the name, because Arabic names are spelled several ways in English.
4. Archive dead leads rather than importing them. Moving a list nobody will call just clutters the new system.
5. Drop personal data you do not need, such as old passport scans, but keep records the law requires you to keep.

On record-keeping: under the UAE anti-money-laundering rules, real estate brokers must keep customer due diligence (identity and background check) and transaction records, including business correspondence, for at least five years from the latest of the end of the relationship, the transaction, an inspection, an investigation or a final judgment (Cabinet Resolution 134 of 2025 and Ministry of Economy guidance). Do not delete anything covered during a clean-up, and confirm with a lawyer what you must keep. For handling client data in general, see PDPL (the UAE personal data protection law) and client data. I could not confirm the implementing regulations of the Personal Data Protection Law, so I would ask a lawyer before moving client data to a supplier abroad.

For a general clean-up method see cleaning up old contacts in your CRM.

Field mapping for a Dubai brokerage

Field	What to decide
Phone	One format, +971 followed by the number; keep a second field for WhatsApp if different
Portal reference	Its own field, never in notes, so a lead can be matched to a listing
Permit number	Own field on each listing. The Trakheesi permit is the Dubai Land Department advertising permit
Lead source	A fixed list: Property Finder, Bayut, Dubizzle, Meta ads (Facebook and Instagram adverts), referral, walk-in
Listing status	Map every old status to one new status, written in a table
Agent	Match on email and broker card number (BRN), the same ones used on the portal accounts
Language	Arabic, English or other, to support routing
Nationality or residence	Only if you already hold it lawfully and need it

Agent identity is the failure mode that catches most migrations. PropSpace says username, email, mobile and BRN must match the portal accounts or publishing fails. Check this before cutover day, not on it.

Who owns which contacts: brokerage vs agent-sourced

Owners fear losing the lead database and the commission pipeline. Agents fear losing their own contacts and history. Agree in writing, before the migration, which contacts are brokerage property and which an agent brought personally, especially for agents who are leaving. This is a contract matter, so confirm with a lawyer.

Import order: deals in progress, warm leads, then history

1. Deals in progress. Anything with a signed agreement or an open commission.
2. Warm leads. Contacted in the last 60 to 90 days.
3. Listings. Live and recently active.
4. Older contacts and history. Last, in bulk, once the rest is verified.

Test with 50 records first and read them on the screen as an agent would. A small test finds most mapping errors for almost no cost.

Re-linking Property Finder, Bayut and Dubizzle feeds without a gap

Bayut and Dubizzle are other major UAE property portals. According to PropSpace, a portal accepts one feed at a time and the new connection replaces the old one. So the feed switch is the moment of risk. Schedule it on a quiet day, confirm that new leads arrive in the new inbox and none go to the old one, and check each portal separately. Vendor timelines suggest the import takes about 14 working days and portal connection 3 to 5 business days. Those are vendor figures that assume a clean export, and the parts add up to nearer three weeks. My article on the Property Finder API explains how lead delivery works.

Parallel run, reconciliation and sign-off

Run old and new together for two to three weeks. Commonly quoted ranges for how long agents are slower after a switch conflict between sources, so measure your own. During the run:

• Agents work in the new system; the old one is read-only.
• Count records by status, source and agent again and compare with your Step 1 numbers.
• Sample 30 records from end to end, from portal enquiry to deal note.
• The operations lead signs a one-page reconciliation before anyone cancels anything.

Keep the old subscription and a full backup until sign-off. Budget for the cost of two licences for two to four weeks.

How software and AI help with the move, and where a person decides

This is where scripts and AI save days:

• Duplicate detection and phone clean-up. A script can normalise phone numbers to +971 and flag likely duplicates.
• Field mapping assistant. Paste the old and new field lists into an AI assistant and it can propose a mapping table for you to correct.
• Diff report. A script compares the old export with the new import and lists records that are missing or changed.
• Tag and status clean-up. AI can group 300 inconsistent tags into 20 sensible ones.
• Arabic-name normalisation. Suggests matches between spellings. A person confirms them, because merging two different clients is hard to undo.

A person decides ownership of contacts, what to delete, and the sign-off. AI can misjudge a duplicate or silently drop a column, so every output is checked against the counts you wrote down at the start. I write these one-off scripts and checks for brokerages; they are small jobs next to the cost of a failed migration.

Try it yourself with Claude

Paste only the column headings of your old export (not client data) and the field list of the new CRM into Claude, an AI assistant, and ask: "Propose a field mapping table. Flag columns with no home, columns that might hold personal data, and fields where I need a rule for Arabic and English names." Review it with your operations lead.

Rebuild automations, retrain agents and cancel the old system

Rebuild lead routing, reminders and templates before agents move. Train in short sessions on three things: log in, find my leads, log a call. Cancel the old system only when the reconciliation is signed, the notice period has been handled and you have a stored export. For the wider checklist on judging vendors see evaluating real estate software vendors.

Cost and timeline: a realistic plan

Team size	Plan (my estimate, not a benchmark)
10 agents	Week 1 audit and exit terms; week 2 mapping and test import; week 3 full import and feed switch; weeks 3 to 5 parallel run
30 agents	Add a week for team-by-team go-live, a named champion per team and a second reconciliation per team

How I'd approach this

I would spend the first week on exit terms and counts, because that is where migrations go wrong, and the new tool is the easy part. I would move one team first, learn from it and then do the rest. If you are unsure whether to switch or extend, see my CRM buying checklist.