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

> Merge duplicate candidate profiles in Greenhouse carefully. Check the primary profile, set auto-merge rules, and clean old records on a Mac.

URL: https://www.lazur.app/for/recruiters/problems/merge-duplicate-candidate-profiles-greenhouse
Updated: 2026-11-09

To merge duplicate candidate profiles in Greenhouse, open the profile you want to discard, choose the record to keep as primary, then run the merge. Site Admins can merge by default. Greenhouse says merges cannot be undone, so check both profiles first. Below you will find what duplicates cost, why they keep appearing, and fixes you can start with Greenhouse settings and a short checklist.

## Quick answer

- Greenhouse says merges cannot be undone, so confirm the primary profile before you merge.
- Auto-merge is stricter than the Duplicate tag, so some true duplicates may stay separate.
- The Duplicate tag only applies to people created after you change its settings.
- Most duplicates start at intake: re-applications, job boards, referrals and agency submissions.
- Turn on the settings first, then clean the old backlog in small batches from a copy of the data.

## What duplicate candidate records in ats costs you

- **Recruiter time spent on admin.** The 2025 Totaljobs survey of 748 HR leaders puts recruiter admin at 17.7 hours per vacancy. Duplicates are not broken out in that figure. Read it as context for the admin load, not as a bill for duplicate records. Your own count of cleanup time will tell you more.
- **Decisions that wait on data entry.** In the same survey, 61% of respondents cited manual data entry as a common issue delaying recruitment decisions. Every extra profile adds another record to check, update and keep in sync. The delay grows when the same person has two open files.
- **Reports that count one person twice.** Greenhouse warns that some reports can contain duplicates when one candidate is rejected from two different jobs. A name can appear more than once. Pipeline counts and source reports then look busier or worse than they really are.
- **Split history and merges you cannot undo.** One profile may hold the interview notes, another the scorecard, and a third the referral. Greenhouse says merges cannot be undone. A rushed merge with the wrong primary profile can replace a field you needed, and you cannot restore the original that way.

## Why it happens

1. **Re-applications and job board intakes.** The ATS vendor Boldats says duplicates appear when job board, referral or re-application intakes create new candidates even though email, phone or LinkedIn match. That is a vendor view with no cited study. Check where your own duplicates came from before you assume the cause. Your intake channels tell you which fix to start with.
2. **Referrals and agency submissions.** Greenhouse's auto-merge does not merge when an agency recruiter submits a candidate. A referral for the same job the person already applied for is not merged automatically. A referral to a different job needs a decision from a user. Each rule leaves a second profile for a person to review.
3. **Details that changed or do not match exactly.** When you add auto-merge criteria, every selected field must match exactly. A new work email, a typo, or a phone number without a country code can block the match. The person has not changed, but the record looks new to the system.
4. **Name-only matches are off.** Greenhouse's Duplicate tag checks email, phone and LinkedIn URL by default. Name is off. A candidate who changed both email and phone may look new even to a careful recruiter. Search the candidate's name in Gmail to find the address they used before.
5. **A second profile made just to be safe.** Boldats says some teams create a second profile just to be safe, instead of checking for a match first. The vendor cites no study on how often this happens. The fix is a written rule: search first, then create.

## How to fix it

- **Turn on auto-merge for exact matches.** Go to Configure > Organization, switch Auto-Merge Candidates on, then select Manage criteria. Pick only the fields you trust. Greenhouse says auto-merge is stricter than the Duplicate tag, so expect some pairs to stay separate. Greenhouse also says information is never deleted in an auto-merge. This setting needs an admin, so ask one to test it on a few records first.
- **Turn on the Duplicate tag.** Go to Configure > Organization, find the Auto-Merge Candidates section, open the Duplicate tag row, and choose Configure duplicate tagging. Keep email, phone and LinkedIn URL on. Keep name off unless your team has a clear reason to turn it on. The tag only shows a visual signal, so a person still decides every merge.
- **Merge by hand with a written rule.** Write one rule for the primary profile. Keep the profile with the most history, then check each single-value field before you merge. Remember that multi-value fields such as emails, phones and tags combine. Confirm your permissions cover every job on both profiles. Greenhouse says merges cannot be undone, so record the discarded profile first.
- **Clean the backlog in a copy.** Copy the candidate list into Google Sheets and sort by email. Use count unique values to see how many addresses repeat. In Excel for Mac, use Data > Data Tools > Remove Duplicates only on a copy. Microsoft says removed duplicate values are permanently deleted, so the copy is your safety net.
- **Merge contacts on your Mac.** If your candidate contacts live in Apple Contacts, use Card > Look for Duplicates, then review each pair before you choose Merge. For a pair you picked yourself, select both cards and use Card > Merge Selected Cards. Apple says the merge keeps all distinct information from each card. Keep a copy of the group first, since Apple does not say whether a merge can be undone.
- **Make intake fields required.** Under Permission Policies, make Source and Rejection Reason required fields. When you close a requisition, reject all remaining candidates. Fill in a rejection reason every time someone is rejected. Greenhouse's guidance says these habits keep hiring data accurate when one candidate appears on two jobs.
- **Search before you create a profile.** Before you create a profile, search by email, then by phone, then by LinkedIn URL. Then search Gmail for the candidate's name to find any older address. This habit catches a second profile before it exists, which is cheaper than merging one later.

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.

- **17.7 hours** Average recruiter admin time per vacancy, all tasks combined, not duplicates alone ([source](https://www.peoplemanagement.co.uk/article/1929340/uk-recruiters-lose-two-days-per-hire-admin-report-finds))
- **8,450 hours** Admin time a year across a typical workload, per the same Totaljobs survey ([source](https://www.peoplemanagement.co.uk/article/1929340/uk-recruiters-lose-two-days-per-hire-admin-report-finds))
- **61%** Of HR leaders cite manual data entry as a common issue delaying recruitment decisions ([source](https://www.peoplemanagement.co.uk/article/1929340/uk-recruiters-lose-two-days-per-hire-admin-report-finds))
- **748** HR leaders surveyed in the Totaljobs research behind these admin figures ([source](https://www.peoplemanagement.co.uk/article/1929340/uk-recruiters-lose-two-days-per-hire-admin-report-finds))

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.

| Situation | What Greenhouse does |
| --- | --- |
| Same email, phone or LinkedIn URL | The Duplicate tag matches these by default. Auto-merge applies only if you enable it and the criteria match. |
| Same name only | Not matched by default. Name is off in the Duplicate tag. |
| Phone number without a country code | Auto-merge on phone alone does not merge it. |
| Submission by an agency recruiter | Auto-merge does not merge it. |
| Referral to the same job the person already applied for | Not merged automatically. |
| Referral to a different job | Needs a decision from a user. |

_Matching cases from Greenhouse's auto-merge and Duplicate tag help articles._

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.

> **Merges are permanent:** Greenhouse says you cannot un-merge candidates. Treat every merge as final. The notes you save before the merge are your only written record of the discarded profile.

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.

> **Old records stay as they are:** Greenhouse applies Duplicate tag changes only to people created after the change. Last year's duplicates keep no tag. You still need a manual pass for the backlog, covered below.

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.

![Recruiter reviewing duplicate candidate profiles on a laptop at a desk](https://images.lazur.app/content-images/problem/merge-duplicate-candidate-profiles-greenhouse/merge-duplicate-candidate-profiles-in-greenhouse-1-f72554.jpg)

## 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](https://www.lazur.app/how-to/count-unique-values-in-google-sheets) and [sort data by column in Google Sheets](https://www.lazur.app/how-to/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.

![Person working on a Mac while checking a candidate list for duplicates](https://images.lazur.app/content-images/problem/merge-duplicate-candidate-profiles-greenhouse/merge-duplicate-candidate-profiles-in-greenhouse-2-d7f9df.jpg)

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](https://www.lazur.app/for/recruiters/gmail) covers that routine.

![Hiring team in an office discussing candidate profiles and applications](https://images.lazur.app/content-images/problem/merge-duplicate-candidate-profiles-greenhouse/merge-duplicate-candidate-profiles-in-greenhouse-3-0cd559.jpg)

## 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.

## With Lazur

Lazur is a voice assistant for the Mac that lives in the notch. Hold ⌥ ⌘ and ask; it sees your screen, answers out loud, points at buttons and walks you through apps. Hold fn to dictate. Free for 3 days, then $18/month: https://www.lazur.app/download

- “Walk me through turning on auto-merge in Greenhouse.”: Lazur circles each menu in Chrome and waits for your click before the next step. (Walks you through it)
- “Walk me through the Auto-Merge Candidates setting in Greenhouse.”: Lazur guides you one click at a time in Chrome and waits for each click before the next step.
- “Where is the Duplicate tag setting on this screen?”: When the option is on your screen, Lazur draws a circle and a label around it so you can find it.
- “What does probable duplicate mean on this screen?”: Lazur reads the banner or help text on your screen out loud and explains it in plain words.
- “Hold fn and dictate your merge notes.”: Hold fn to dictate clean text at the cursor in any app. Snippets and a personal dictionary help with repeat phrases.
- “Draft a note to my admin about changing auto-merge criteria.”: Lazur drafts the message and types it where your cursor is. You read it and send it yourself.

## A plan you can start this week

- **Day 1: Pull the backlog into a copy.** Get a copy of the candidate list you need and open it in Google Sheets. Sort by email, then flag pairs that match on email, phone or LinkedIn URL. Change nothing in Greenhouse yet.
- **Day 2: Write the merge rule.** Write one page. Name the primary profile rule, the fields you check, who may merge, and where you log decisions. Ask your admin to agree before anyone merges a pair.
- **Day 3: Set auto-merge and the tag.** Ask a Greenhouse admin to open Configure > Organization. Review Auto-Merge Candidates, Manage criteria and Configure duplicate tagging. Save a note of every choice and why you made it.
- **Day 4: Merge in small batches.** Merge a small batch of pairs that pass your checklist. Open each merged profile and check the single-value fields and open applications before you move to the next pair.
- **Day 5: Fix intake fields.** Make Source and Rejection Reason required under Permission Policies. Add the search-first rule for new candidates, including a Gmail search for the candidate's name.
- **Weekly: Review probable duplicates.** Each week, check the probable duplicates and any tagged profiles. Merge only the pairs that pass your checklist. Log what you merged and why, so the next person can follow it.

## FAQ

### Can I undo a merge in Greenhouse?

Greenhouse says you cannot un-merge candidates. Write down the discarded profile's name, email and open applications before you start. Greenhouse also says information is never deleted in an auto-merge, and replaced fields stay in the Activity Feed.

### Who can merge candidates in Greenhouse?

All Site Admins can merge candidates. Job Admins can merge only if a custom permission level grants it, on Plus and Pro tiers. They also need equal job-based permissions across all of the candidate's jobs.

### Why didn't auto-merge combine my two profiles?

Auto-merge is stricter than the Duplicate tag. When you add criteria, every selected field must match exactly. Phone-only rules need a country code. Agency submissions are not merged, and referrals to a different job need a user decision.

### Does the Duplicate tag merge profiles?

No. Greenhouse calls the tag a visual signal, and it does not change auto-merge behavior. It applies only to people created after you change its settings, so old records keep no tag.

### How do I find duplicates in a candidate spreadsheet?

Copy the list into Google Sheets, then sort by email to group exact matches. Use count unique values to see how many addresses repeat. Spelling variations need a human check, because a tool compares characters, not identities.

### Can Lazur merge candidates for me?

No. Lazur does not click buttons or operate other apps. It guides you one click at a time, or points at the control on your screen. You make the merge yourself.

### Can I use Lazur with candidate data?

Check your employer's rules first. Lazur sends audio and a screenshot to AI providers to answer you while you hold the shortcut. Those are not stored, and content is never used to train AI models.

### Does Lazur plug into Greenhouse?

No. Lazur is not a plugin or add-in for Greenhouse, and it has no partnership with Greenhouse. It works from what is on your Mac screen while you hold the shortcut. Lazur has a 3-day Pro trial with no credit card. Check the [pricing page](https://www.lazur.app/pricing) for current plan terms.

## Sources

1. [Merge duplicate candidate profiles](https://support.greenhouse.io/hc/en-us/articles/115004506466-Merge-duplicate-candidate-profiles), Greenhouse Software, checked 2026-11-09
2. [Auto-merge](https://support.greenhouse.io/hc/en-us/articles/208063316-Auto-merge), Greenhouse Software, checked 2026-11-09
3. [Configure the Duplicate tag](https://support.greenhouse.io/hc/en-us/articles/49207850415003-Configure-the-Duplicate-tag), Greenhouse Software, checked 2026-11-09
4. [Identify and correct inaccurate hiring data](https://support.greenhouse.io/hc/en-us/articles/16711979322907-Identify-and-correct-inaccurate-hiring-data), Greenhouse Software, checked 2026-11-09
5. [How Recruiterflow Detects and Manages Duplicate Candidates](https://help.recruiterflow.com/en/articles/4366865-how-recruiterflow-detects-and-manages-duplicate-candidates), Recruiterflow, checked 2026-11-09
6. [Why every duplicate candidate in an ATS should merge instead of creating a second record](https://boldats.com/insights/why-every-duplicate-candidate-ats-should-merge-not-create-second-record/), Boldats (vendor blog), checked 2026-11-09
7. [UK recruiters lose two days per hire to admin, report finds](https://www.peoplemanagement.co.uk/article/1929340/uk-recruiters-lose-two-days-per-hire-admin-report-finds), People Management (reporting on Totaljobs research), checked 2026-11-09
8. [Merge contact cards (Apple Contacts User Guide for Mac)](https://support.apple.com/guide/contacts/merge-contact-cards-adrbk1456/mac), Apple Support, checked 2026-11-09
9. [Filter for or remove duplicate values](https://support.microsoft.com/en-us/excel/filter-for-or-remove-duplicate-values), Microsoft Support, checked 2026-11-09
10. [Clustering Methods In-depth](https://openrefine.org/docs/technical-reference/clustering-in-depth), OpenRefine, checked 2026-11-09