How to merge duplicate candidate profiles in Greenhouse: steps for recruiters on Mac

A duplicate candidate record is a second profile for someone who already exists in your applicant tracking system. It often shows up when that person applies again, comes in through a job board, or gets referred by someone on your team. You can fix most of it with admin settings and a short checklist. The rest needs a careful manual merge, and that step is permanent.

What duplicate candidate records cost your team

The best public figure here covers all recruiter admin, not duplicates alone. A 2025 Totaljobs survey of 748 HR leaders found recruiters spend an average of 17.7 hours per vacancy on administrative work. The write-up says that is more than two working days per hire. Across a typical workload, it adds up to 8,450 hours a year.

Duplicates are not broken out in that survey. It does break down the admin time. Reviewing applications takes 3.6 hours per vacancy, scheduling interviews takes 2.5 hours, and processing post-interview notes takes 3 hours. Your own number will differ. Track your cleanup time for a few weeks, and write down how long each pair takes.

The same survey says 61% of respondents cite manual data entry as a common issue that delays recruitment decisions. A duplicate forces you to type or check the same details twice. Each extra profile is one more record to keep in sync. Reports also suffer. Greenhouse says some reports can contain duplicates when one candidate is rejected from two different jobs, and a name can appear more than once.

The worst cost is a split history. Notes sit on one profile, the scorecard sits on another, and the referral source may sit on a third. Whoever asks for the full story gets only part of it. That is why a merge is worth doing carefully, and why a fast merge is risky.

Why duplicate candidate records keep appearing

Most duplicates start at intake, not with one careless recruiter. The ATS vendor Boldats says duplicates get created when job board, referral or re-application intakes make new candidates even though email, phone or LinkedIn match. It also says teams make a second profile just to be safe. That blog cites no studies. Treat it as a pattern to check against your own data.

Matching rules explain the rest. Greenhouse does not merge everything that looks identical. The table covers the cases its help pages describe.

Two rows surprise people. A referral to the same job the person already applied for is not merged automatically. A phone number without a country code will not merge on phone alone. Check the number format on new intakes before you assume the system will catch it.

Changed details cause plenty of misses. A candidate who changed their work email between applications will not match on email. When you add criteria, Greenhouse requires every selected field to match exactly. One changed character can leave two profiles that look like strangers to the system.

A worked example: one candidate, two profiles

Say a candidate applied in March through a job board. The same candidate came back in June through a referral, using a new work email. Email matching misses the link. The referral lands on a second profile, and your team now sees two people.

Now the merge decision matters. Greenhouse keeps the primary profile's data when single-value fields conflict. Those fields include current company, title, source and recruiter. Multi-value fields such as emails, phones, tags, attachments, scorecards and education are combined. So the profile you keep decides which title and source survive.

In this example, the June profile has the referral and the newer title. The March profile has the phone screen notes and the older source. Keep the profile with the most history, then check each single-value field by hand. Do not assume the newer profile is the right one.

Check the profile before you merge candidates in Greenhouse

1. Confirm it is the same person. Compare email, phone, LinkedIn URL and work history on both profiles.
2. Check the single-value fields on each profile: current company, title, source and recruiter.
3. Check permissions. Greenhouse needs equal job-based permissions across all of the candidate's jobs.
4. Note the discarded profile's name, email and open applications in a document you keep.
5. Merge one pair, then open the result and check it before you start the next pair.
6. Log who merged, when and why, so a teammate can trace the decision later.

Job Admins have a limit. On Plus and Pro tiers, they can merge only when a custom permission level grants it. Site Admins can merge by default. If you do not see a merge option, ask your admin whether your role has that permission.

Greenhouse auto-merge and the Duplicate tag: settings to check

These are admin settings, and you need access to Configure in Greenhouse to change them. To turn on auto-merge, go to Configure > Organization, switch Auto-Merge Candidates on, then select Manage criteria. Choose the fields that must match. When you pick more than one, every selected field has to match exactly.

The Duplicate tag lives in a different place. Go to Configure > Organization, find the Auto-Merge Candidates section, then the Duplicate tag row, and choose Configure duplicate tagging. By default the tag checks email, phone and LinkedIn URL. Name is off. The tag is a visual signal, and it does not merge anything.

Phone is a special case. If phone is your only criterion, auto-merge merges only numbers that include a country code. If your intake forms store local numbers, expect fewer automatic merges than you hoped for.

Clean up old duplicate records in Google Sheets or Excel

Settings only help with new records. For the backlog, get a copy of the candidate list you need, then open it in Google Sheets. Sort by email to group exact matches. You can also count unique values to see how many distinct addresses you have. Step-by-step help is in count unique values in Google Sheets and sort data by column in Google Sheets.

If you use Excel for Mac, go to Data > Data Tools > Remove Duplicates. Microsoft says removing duplicate values permanently deletes them. Copy the sheet to a new tab first. Microsoft's help article lists Microsoft 365 for Mac, Excel 2024 for Mac and Excel 2021 for Mac. Outlined or subtotalled data cannot be deduplicated, so clear those first.

Exact matches are easy. Spelling changes are not. A tool compares characters, not people. OpenRefine's clustering method lowercases text, strips punctuation and folds accents. Its docs say it cannot tell that two different spellings are the same entity. Read every near match yourself before you delete anything.

If your candidate contacts live in Apple Contacts on your Mac, use Card > Look for Duplicates, then Merge. You can also select two cards and choose Card > Merge Selected Cards. Apple says the merge keeps all distinct information from each card. Apple's page does not say whether a merge can be undone, so keep a copy of the group before you start.

Stop duplicates at intake

Prevention is cheaper than cleanup. Greenhouse's reporting guidance has three steps. Make Source and Rejection Reason required fields under Permission Policies. Reject all remaining candidates when you close a requisition. Populate a rejection reason every time you reject someone.

Those steps keep reports honest. They do not stop a second profile from being made. Decide which referral route your team uses, and tell recruiters to search for an existing profile before they create one. Search by email first, then phone, then LinkedIn URL. You can also search Gmail for the candidate's name to find an older address. The Gmail guide for recruiters covers that routine.

Mistakes people make with duplicate candidate profiles

• Merging on name alone. Name is off by default in the Duplicate tag, and a shared name is weak evidence.
• Treating the Duplicate tag as a merge. Greenhouse calls the tag a visual signal that does not change auto-merge.
• Expecting new settings to fix old records. Tag changes apply only to people created after the change.
• Cleaning a sheet without a copy. Excel's Remove Duplicates permanently deletes the values it removes.
• Ignoring referrals and agency rows. Auto-merge skips agency submissions, and referrals to a different job need a decision.
• Forgetting permission limits. On Plus and Pro tiers, Job Admins need a custom permission level to merge.

Candidate data, employer rules and AI help

Candidate profiles hold personal information. Follow your employer's rules on candidate data before you copy an export into any tool, including Google Sheets or an AI assistant. If you are unsure, ask your privacy or legal team before you start.

Lazur sees your screen only while you hold the shortcut ⌥⌘. Audio and the screenshot go to AI providers so Lazur can answer you. Those are not stored, and content is never used to train AI models. A screen full of candidate details is still candidate data, so check your rules before you ask about it.

If your ATS is Recruiterflow

Recruiterflow treats profiles that share an email, phone number or LinkedIn URL as one person. New applications from that person go to the existing profile. It flags profiles with the same name, current company and job title as probable duplicates, and shows a Merge button. Its article does not say whether a merge can be reversed, so ask the vendor before you rely on it.

Where Lazur helps, and where it does not

Lazur is a voice assistant for the Mac. It guides and points. It does not click buttons, edit records or operate Greenhouse for you. It is not a plugin, and it has no partnership with Greenhouse. You still make every merge yourself.

Ask how to do something and Lazur guides you one click at a time, waiting for each click. Ask where something is and Lazur draws a circle and a label around it on your screen. Ask what a label means and Lazur explains it out loud.