An estate agency CRM cleanup is a structured review of the people records in your system, mainly applicants, vendors and landlords, to remove duplicates, close inactive records, complete missing fields and record why you hold each person’s data. Done well, it makes follow-up faster and reports believable, and it supports your UK GDPR duty to keep personal data accurate and no longer than needed.
This checklist is vendor-neutral, so it works in Alto, Reapit, Street.co.uk, Jupix or a spreadsheet. The legal points come from the Information Commissioner’s Office (ICO) guidance as read in October 2026. It is practical guidance, not legal advice, so take advice on your own retention periods and consent position.
Why does an estate agency CRM cleanup matter?
Because every feature that depends on your data, from applicant matching to marketing sends to weekly reports, is only as good as that data. Old records inflate demand, split histories and risk sending messages to people who should not receive them.
There is also a regulatory reason. The ICO’s accuracy guidance says you must take every reasonable step to erase or rectify inaccurate personal data without delay, and that the more important accuracy is, the more effort you should put in. Its storage limitation guidance says you should not keep personal data indefinitely just in case, and that you must review data and erase or anonymise it when you no longer need it.
Step zero: what should you do before you delete anything?
- Back up. Export the full database and store it securely.
- Write the rules. Define “active”, “dormant” and “closed” for each record type.
- Name an owner. One person approves merges and deletions.
- Test on a sample. Run each rule on 50 records and check the result.
- Keep a log. Record what was changed, by whom and when.
Never delete in bulk without a backup and a sample test. Merges and deletions are hard to reverse in most systems.
Applicant cleanup checklist
Applicants are the largest and fastest-decaying group, so start there.
| Check | What to do | Why |
|---|---|---|
| Duplicates | Match on email, mobile and name; merge keeping full history | One conversation, one record |
| Stale status | Close applicants with no contact or activity past your set period | Honest demand figures |
| Bought or rented elsewhere | Mark closed with a reason | Stops irrelevant alerts |
| Requirements | Update budget, bedrooms, areas, timescale | Better matching |
| Consent | Record marketing consent, date and source | Safe email and SMS |
| Source | Fill lead source on every record | Reporting that means something |
| Next action | Add a date or close the record | No orphaned leads |
Choose your dormancy period yourself. The ICO says there are no fixed time limits under UK GDPR and that you must be able to justify the period you pick. Document the reasoning so it is not an arbitrary number.
Vendor cleanup checklist
Vendor records should tell the next person everything they need before they call. Check each of these.
- Correct names for all owners, including joint owners, and preferred contact method.
- Property linked to the right vendor, with instruction status up to date.
- Valuation history and outcome recorded, including the reason an instruction was lost.
- Terms of business, ID and anti-money-laundering status recorded in the place your process requires.
- Marketing preferences and the date they were recorded.
- Notes written as facts. The ICO says an opinion is not inaccurate just because someone disagrees, but records should show that it is an opinion and whose opinion it is.
Past vendors who sold with you are a valuable list, but treat them as past customers with specific consent rules, not as a free-for-all.
Landlord and tenancy cleanup checklist
Lettings data has more dates and more third parties, so errors cost more.
- Landlord contact details. Including correspondence address and emergency contact where relevant.
- Property links. Each landlord linked to every property, and each property to the right tenancy.
- Key dates. Tenancy start, end and renewal dates, plus certificate expiries, checked against source documents.
- Management status. Let only, managed or fully managed, recorded consistently.
- Former landlords. Closed with a reason and a review date.
- Tenant data. Review what you hold on former tenants against your retention rules and delete or anonymise what you cannot justify.
Certificates, deposits and referencing outcomes are compliance matters. A remote assistant can check that documents exist and dates match, but your property manager decides what is compliant.
What does UK GDPR say about retention and consent?
Three ICO points do most of the work in a cleanup. First, storage limitation: the ICO says you should document standard retention periods for different categories of data wherever possible, review data at the end of each period, and erase or anonymise it unless there is a clear reason to keep it. It also notes that moving data offline is not the same as deleting it, and that deletion from a live system should extend to backups.
Second, data minimisation: the ICO says personal data should be adequate, relevant and limited to what is necessary, and should be reviewed periodically, with anything no longer needed deleted. Third, marketing: the ICO’s guidance on electronic mail marketing says you generally need specific consent before sending marketing emails or texts to individuals, with a limited soft opt-in for your own previous customers, and every message needs a working way to opt out.
A pragmatic retention schedule for an agency might list applicants, vendors, landlords, tenants and completed transactions, with a purpose, a period and a review owner for each. The periods are your decision and may be affected by other legal duties such as record-keeping for money laundering or tax, so confirm them with an adviser.
What mistakes do estate agency CRM cleanups make?
- Deleting before defining. Without a written rule for “dormant”, two people clean to two different standards.
- Merging blindly. Two records with the same email can be a couple, a parent and child, or a landlord and tenant. Check before you merge.
- Cleaning once. A database decays again within months if new records are created sloppily. Fix the entry rules, such as mandatory source and next action, as well as the existing data.
- Triggering automations. Bulk edits can fire alerts, emails or tasks in some systems. Test on a few records and check your automation settings first.
- Forgetting the backups and exports. Spreadsheets of old applicants on laptops or shared drives are still personal data.
How do you know the cleanup worked?
Pick four numbers before you start and compare them afterwards: the count of active applicants, the percentage of records with a lead source, the percentage with recorded consent, and the number of duplicate pairs found in a sample. If the active applicant count falls sharply, that is expected and healthy. It means your pipeline now shows real demand.
Who should do the work?
A trusted team member sets the rules, and anyone, including a remote assistant, can apply them. Rule-based jobs such as deduplication, field completion and status updates suit a CRM virtual assistant. Decisions about consent, retention and what to delete should stay with a named person.
If you use a remote team outside the UK, check the ICO guidance on international transfers and have a written contract. Our guide to offshore assistants and UK GDPR covers the questions.
How often should you repeat the cleanup?
A big clean once, then small checks. Each month, run a duplicate check, a completeness check on key fields and a review of applicants past your dormancy period. Each quarter, review vendors and landlords. Each year, review your retention schedule itself.
For system-specific task lists, see our guides to an Alto CRM virtual assistant, and the wider best CRM for UK estate agents comparison. For the principles of reviving a tidy list, read our post on cleaning and reactivating a database.
To see how a remote assistant could support your UK estate agency CRM, book a free consult.