Key takeaways
- Applicant lists grow fast: Propertymark sales branches registered 69 new buyers each in August 2026 and letting branches 121 new applicants[1].
- UK GDPR requires personal data to be accurate and kept no longer than necessary, so an untouched applicant list is a compliance problem as well as a sales one[2].
- Screen call lists against the Telephone Preference Service and your own objections list before any canvassing campaign[3].
- Audit, merge duplicates with clear rules, refresh or remove stale records, then keep it clean with entry rules and a monthly routine.
How applicant databases decay
Every agency CRM starts clean and slowly fills with clutter. A buyer enquires on two portals and becomes two records. A couple register separately, then together. Someone buys through another agent and stays on your list for years as an active applicant. Phone numbers change, email addresses bounce and notes stop at 'called, no answer'. Negotiators learn not to trust the list and keep their own spreadsheets, which makes the CRM worse still.
The cost shows up in small ways: property alerts sent to people who moved two years ago, matching reports that bury real buyers under stale records, and canvassing calls that annoy past applicants. It also shows up in compliance. Data protection law expects records to be accurate and kept only as long as needed, and marketing rules expect you to know who has objected.
How fast the list grows
In August 2026 a typical Propertymark sales branch registered 69 new prospective buyers and a typical letting branch registered 121 new applicants[1]. On those averages, a branch doing both would add well over 2,000 applicant records a year, before duplicates. Without regular clean-up, a few years of trading produces a database where most records are out of date.
Source: Propertymark, 2026[1]
Show the data
| Item | Value |
|---|---|
| Buyers (sales branch) | 69 registrations |
| Tenant applicants (letting branch) | 121 registrations |
The legal reasons to clean up
UK GDPR requires personal data to be accurate and, where necessary, kept up to date, with every reasonable step taken to erase or correct inaccurate data without delay[2]. It also requires that data be kept in a form that identifies people for no longer than necessary for the purposes it is processed for[2]. An applicant record from a buyer who completed elsewhere three years ago is hard to justify on either count.
Marketing rules add a second layer. Under regulation 21 of PECR, businesses must not make unsolicited direct marketing calls to numbers registered with the Telephone Preference Service or to people who have told them not to call[3]. A call to a TPS-registered number is not a breach if the number has been on the register for less than 28 days[3], which is why screening must be repeated before each campaign rather than done once. Security matters too: 43% of UK businesses reported a cyber breach or attack in the latest survey year[4], and a bloated database is simply more data to lose.
Step 1: audit before you touch anything
Export a snapshot
Take a full export of applicant records and keep it securely for a short, defined period in case a merge goes wrong.
Count the obvious problems
Records with no phone or email, duplicate emails, duplicate mobiles, and bounced or invalid addresses.
Age the records
Group records by date of last meaningful contact: under 6 months, 6 to 12, 12 to 24 and over 24 months.
Check marketing status
Count records with a recorded consent or soft opt-in for email and text, objections, and numbers never screened against the TPS.
Write the baseline down
These counts are your before picture and help you decide where to start.
Step 2: merge duplicates with clear rules
| Match rule | Confidence | Action |
|---|---|---|
| Same email address | High | Merge automatically, keeping the most recent contact details and all notes |
| Same mobile number, similar name | High | Merge automatically and log the merge |
| Same name and postcode, different contact details | Medium | Review queue: a person checks before merging |
| Same mobile, different names | Low | Do not merge; often partners or a shared family phone |
| Joint applicants registered separately | Medium | Link the records rather than merging, so each person keeps their own consent |
Keep the history when you merge. Notes, viewings, offers and objections must all survive, and an objection to marketing on either record should apply to the merged one.
Step 3: refresh or remove stale records
Decide what an active applicant means for your agency, for example someone who has had a meaningful contact in the last six months. For records older than that, try one short, polite re-engagement message where you are allowed to send it, and archive or delete the record if there is no response.
Script: 'You registered with us while looking for a two-bedroom flat in the area. Are you still looking? Reply YES and we will keep sending matching homes, or STOP and we will remove your details. If we do not hear from you within a fortnight, we will close your search.'
Only send that message by email or text where you have consent or a valid soft opt-in from the original enquiry, and include an easy way to opt out. If in doubt for a group of records, do not message them; simply close the search and apply your retention rule.
Step 4: set retention periods
- Applicants with no meaningful contact: a fixed period your policy sets, then delete or anonymise for statistics.
- Applicants who bought or rented through you: move them to a client record with its own retention rule.
- Customer due diligence and transaction records for money laundering purposes: five years from the end of the business relationship or completion of the transaction[5].
- Complaints and disputes: until the matter is closed and any redress or court deadline has passed.
- Call recordings and transcripts: a shorter period, unless linked to an open complaint.
Write these into your privacy notice and your CRM settings. Many CRMs can archive or anonymise automatically; switch that on once the rules are agreed.
Step 5: keep it clean at the point of entry
- Search before you create: staff search by mobile and email before adding a new applicant.
- Required fields: at least one working contact method, search criteria and source.
- Picklists, not free text, for property type, area and position.
- Record marketing permissions at the moment they are given, with the wording shown.
- Close searches when an applicant buys or rents elsewhere, and note it.
Integrations cause many duplicates, so check how portal leads are matched to existing records. Our guide to connecting CRM, portals and phones covers lead matching in more detail.
Worked example: a branch clean-up
Example: a fictional single-branch sales and lettings agency audits 9,400 applicant records. It finds 1,150 duplicates by email or mobile, 2,300 records with no meaningful contact for over two years, and 640 numbers never screened against the TPS. After automatic merges and a review queue for medium matches, the list falls to 8,100 records.
Example, continued: it sends a re-engagement email to 1,900 stale records with valid email permission; 210 confirm they are still looking. The rest are closed and deleted under the new retention rule, along with stale records it cannot lawfully contact. The live database ends at about 4,200 applicants. Property alert open rates rise, and negotiators start using the CRM's matching list again instead of their spreadsheets.
Who owns data quality
Clean-ups fail when everyone is responsible and nobody is accountable. Name one person per branch, often the administrator or branch manager, who owns the applicant list. They run the monthly routine, clear the review queue and raise problems with the CRM supplier. Negotiators own the quality of what they enter and close searches for their own applicants.
Make it visible. Share a short monthly figure with the team, such as the number of duplicates created and records missing a contact method, and celebrate when it falls. Data quality improves fastest when people can see that their care at the point of entry is noticed.
A monthly data quality routine
- Run the duplicate report and clear the review queue.
- Close searches for applicants with no meaningful contact past your active threshold.
- Screen any call list against the TPS and your objections list before use.
- Check bounced emails and invalid numbers, and fix or remove them.
- Spot-check ten new records for required fields and correct source.
- Confirm automatic retention and deletion ran as expected.
An hour a month keeps the database useful. If you plan to use it for canvassing, our page on database marketing for estate agents explains how to approach past applicants properly.
Frequently asked questions
How long can an estate agent keep applicant data?
No longer than necessary for the purpose. Set a defined period for applicants with no meaningful contact, state it in your privacy notice, and delete or anonymise records when it ends. Money laundering records follow their own five-year rule.
Can we phone old applicants about valuations?
That is marketing, so screen the numbers against the Telephone Preference Service and your own objections list first, and respect anyone who has asked not to be called. Repeat the screening before each campaign.
Should we merge duplicate records automatically?
Only where confidence is high, such as an identical email address. Send medium matches to a review queue and never merge records that share a phone but have different names.
How often should we clean the CRM?
Do one full clean-up, then run a short monthly routine for duplicates, stale searches, bounces and screening. Small regular checks are far easier than a big cleanse every few years.
References
Propertymark (2026). Housing Insight Report, August 2026 (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2026). UK GDPR, Article 5: Principles relating to processing of personal data (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) ↑
legislation.gov.uk (The National Archives) (2017). The Money Laundering Regulations 2017, regulation 40: Record-keeping (opens in a new tab) ↑