How to stop duplicate records in your recruitment CRM
Duplicates split one person's history across two records, so two recruiters call the same candidate and a client gets the same CV twice. How to stop them at the door, find the ones already in, and merge without losing a note.
You stop duplicate records by checking for the person before a record is created and merging the duplicates that get through anyway. Recruitly checks every new candidate, contact, lead and company for an existing match on email, mobile or name and keeps the Create button locked while one stands. For duplicates already in your database, the Duplicate candidates filter lists every candidate who shares an email address with another, and Merge combines them into the record you choose, moving notes, files, jobs and history across.
How do duplicate records get into a recruitment CRM?
Duplicates get in whenever a person reaches your database by a second route and nothing checks for the first. Recruitment has more routes than most businesses: applications, job boards, LinkedIn, referrals, imports, events and every consultant's own inbox.
| How it happens | Example | What catches it |
|---|---|---|
| The same person applies twice | A candidate applies in March from a work address and in October from a personal one | The create check if the name or mobile matches; a merge if not |
| A recruiter adds someone without searching first | A consultant adds a LinkedIn profile as a new candidate | The create check, the Chrome extension's "already in Recruitly" panel |
| Imports and job board feeds | A spreadsheet from an old system loaded on top of the live data | Bulk CV import's skip or update option; the Duplicate candidates filter afterwards |
| Two people add the same lead the same week | Two consultants meet the same hiring manager at an event | The create check on email, mobile or name |
| The person changed name or email | A new surname after marriage, a new personal address | Nothing automatic; a recruiter who spots it merges them |
The last row is the hard one. When a person changes both their name and their email, no rule can be sure they are the same person, and a recruiter who knows them is the best judge.
What do duplicate candidate records cost an agency?
A duplicate splits one person's history across two records, and every part of the business that reads the record gets half the truth.
- Two recruiters work the same candidate. One calls about a role on Monday and another calls about a different one on Wednesday, neither knowing about the other. The candidate notices.
- A client receives the same CV twice. Once from each record, sometimes from two consultants. At best it looks careless. At worst it starts an argument about who introduced the candidate, which is an argument about the fee.
- Search shows the worse record. The record with the old CV and the old title is the one that matches the search, and the one with the latest conversation is missed.
- Data requests miss a record. When a person asks what you hold or asks to be deleted, a second record under another email is easy to miss, and a GDPR request answered from half the data is not answered.
- Reports count people twice. Candidate numbers, activity per candidate and campaign audiences are all inflated, and the same person gets your campaign email twice.
How does Recruitly stop duplicates being created?
Recruitly checks for the person at every door a record comes through, so most duplicates never get in.
- Adding a record by hand. As the details are typed in, Recruitly looks for an existing candidate, contact, lead or company with the same email, mobile or name. If it finds one, an amber "Possible duplicates found" banner names them with a link to open each, and Create stays blocked while the match stands. There is no "create anyway".
- Bulk CV import. Up to 20 CVs or a zip at a time, with a choice to skip duplicates or update the existing record's CV.
- The Chrome extension. On any LinkedIn profile the side panel says straight away whether the person is already in Recruitly, or shows possible matches to link, before anyone adds them.
- People who contact your team. Simi's Auto-create records checks for an existing record before adding someone who emailed, messaged or phoned.
- Claude and ChatGPT. When you ask your assistant to add someone through the Recruitly MCP server, it looks for them by email, LinkedIn profile or name and employer first, and opens the existing record if there is one.
How do I find duplicates already in my database?
For candidates, apply the Duplicate candidates system filter. In the Candidates module, search the system filters for Duplicate candidates and apply it. It lists every candidate whose email address, main or alternate, is also on another candidate, which is the surest sign of the same person twice.
For companies, open Data Health for companies. Its Duplicate Domains tile counts companies that share a website domain, the usual sign of one client entered twice with different spellings of its name.
For contacts and leads, and for candidates who share no email, sort a grid by name or search for a name you suspect. Two people with the same name are often different people, so check the employer, the phone and the history before merging.
How do I merge duplicate records in Recruitly?
Select the records, choose Merge, pick the record to keep and confirm. Merge works on candidates, contacts, leads and companies.
- Tick two or more records in the grid, for example from the Duplicate candidates filter.
- Click More and choose Merge.
- Choose the destination: the record that will remain. When merging candidates, each one shows whether it has an email, a phone, a CV and how many tags, so the fuller record is easy to spot.
- Confirm. The merge runs in the background and the duplicates leave the list when it finishes.
A record that has been anonymised for GDPR cannot be merged, because its identifying details are gone, and Recruitly sets it aside with the reason. Emma shows the whole thing in 48 seconds in how to find and merge duplicate candidates.
What happens to notes, CVs and job history when you merge?
All of it moves to the record you keep. The only thing that does not survive is a field value on the duplicate where the record you keep already had a different one.
| What | What happens in a merge |
|---|---|
| Field values | The destination keeps every value it has. Empty fields are filled from the duplicate |
| Jobs and pipelines | The duplicate's places on jobs move to the destination. Where both were on the same job, the destination's place is kept and the duplicate's is removed |
| Notes, tasks, meetings | Moved to the destination |
| Files and CVs | Moved to the destination |
| Emails, calls, SMS and the timeline | Moved, so the destination shows the whole history |
| Custom activity forms | Moved, unless the destination already has that form filled in |
| GDPR consent | The destination's consent stands; consent requests still open on the duplicate are removed |
| The duplicate record | Deleted once everything has moved |
Which record should I keep when I merge duplicates?
Keep the record whose details you trust most, because its values win wherever the two disagree. That is usually the one with the latest CV, the current job title and the most recent conversation. Notes, files and jobs come across whichever you pick, so history is not a reason to choose one over the other.
If the duplicate has one better value, such as a newer mobile number on a record that already has an old one, copy it onto the record you keep before merging, or update it afterwards from the LinkedIn tab.
Can a merge be undone?
No. The duplicate is deleted once its history has moved, so check the two records are the same person before you confirm. Name alone is not enough. Look at the employer, the phone, the email and the last conversation.
Can software find duplicates that share no email?
Partly. Recruitly's check at creation also matches mobile and name, which catches the same person arriving with a new email. What it cannot be sure of is a person who changed email, phone and name at once, and an automatic merge would be wrong often enough to do real damage, joining two different people's histories and sending one person's details to a client as the other's.
That is why Recruitly finds the likely pairs and leaves the decision to merge to someone who knows the candidates. It takes a recruiter seconds to recognise a person they have spoken to, and the merge does the rest.
A different kind of duplicate lives inside a single record: the same job listed twice in the work history, or a skill spelled three ways. The Data Agent's clean-up tidies those while it works through your records.
What routine keeps duplicates out?
| When | What | Who |
|---|---|---|
| Every time someone adds a record | Recruitly checks email, mobile and name, and blocks Create on a match | Automatic |
| Every import | Choose skip or update for duplicates in a bulk CV import | Whoever imports |
| Monthly | Apply the Duplicate candidates filter and merge what it lists | A super user or a named owner of data quality |
| Monthly | Check Duplicate Domains on Data Health for companies | The same person |
| Whenever a recruiter spots one | Merge it on the spot, choosing the fuller record | Any recruiter |
Name one person as the owner of data quality. Duplicates are everyone's problem, which in most agencies means nobody merges them. Twenty minutes a month with the filter and the Data Health tile keeps a database clean. The rest of a data routine is in how to keep candidate data up to date.
Why did Recruitly stop me creating a candidate?
Because a candidate, contact, lead or company with the same email, mobile or name already exists. The banner names the match with a link to open it. Open the existing record and update it instead.
Does merging duplicate candidates lose any notes?
No. Notes, tasks, meetings, files, emails, calls and the timeline all move to the record you keep. Only conflicting field values on the duplicate are dropped.
Can I merge contacts and companies, not just candidates?
Yes. Merge works the same way for candidates, contacts, leads and companies: select them, More › Merge, choose the record to keep.



