Recruiting Basics

Candidate Merge

Candidate merge is the operation that resolves duplicate records by combining them into one surviving profile. It sets which values win field by field, moves applications, notes, interview feedback and attachments onto the survivor, and retires the other record. Merging follows candidate deduplication, the separate detection step, and in many systems the result cannot be reversed cleanly.

How do you choose which candidate record survives a merge?

Pick the record carrying the most hiring activity, not the newest one. A profile holding live applications, interview feedback and email history is expensive to rebuild, whereas a thin record created last week by an import usually holds nothing but contact details. Where both carry activity, most teams keep the one linked to the open requisition so that nothing in flight breaks. Contact details are the exception to the general rule: the freshest email and phone number should win even when the older profile survives, because reachability is the point. Write the choice down as a policy rather than leaving it to whoever happens to be looking. Without one, two recruiters resolve identical situations differently, and six months later nobody can explain why one profile has a full history and its twin has none.

What happens to applications, notes and interview history when records are merged?

The intent is that everything attached to the retired record moves to the survivor, but behavior differs by system and deserves testing before you trust it. Applications normally transfer, which can leave one person holding two applications to the same job and needing manual tidying. Notes and scorecards usually carry across with their original authors and timestamps intact, and that provenance matters, since feedback loses meaning if it is silently reattributed. Attachments such as resumes and portfolios generally survive, sometimes as duplicate copies. Email threads are the least predictable part: some systems relink the whole conversation, others leave it tied to the original address where it becomes hard to find. Run a test merge on two throwaway records in your own [applicant tracking system](/ats) and inspect each of these before letting the wider team loose on real profiles.

Can a candidate merge be undone?

Often not, or not cleanly. Once fields have been overwritten and child objects re-pointed, reversing the operation means reconstructing which value came from which record, and many products simply do not retain that. Some offer an unmerge that restores the shell of the retired record without reliably returning every note and application to it. Assume irreversibility unless a vendor demonstrates otherwise on live data. Two habits reduce the damage. Confirm the match before merging rather than after, using an identifier the two records share instead of a name that merely looks similar. Make sure every merge writes an entry to the system log recording who ran it, when, and which records were involved, so a mistake can be investigated even if it cannot be rolled back. Log coverage varies, so check it when comparing [ATS features](/ats-features).

Who should be allowed to merge candidate records?

Restrict it. Merging is destructive in a way that most recruiting actions are not, and the people most likely to encounter duplicates are not always the people best placed to judge whether two records describe the same person. A workable split gives everyday users the ability to flag a suspected duplicate, and gives a smaller group, typically recruiting operations or a system administrator, permission to execute the merge. That group also owns the policy on which fields win and works the queue on a schedule instead of merging ad hoc. Where agencies or external partners have access, they should never hold merge rights over internal records. Permission design here is worth more than any amount of training, because the mistake is silent and the person who makes it usually has no idea anything went wrong.

See how Pitch N Hire handles candidate merge on your roles

Choosing your recruiting stack

Next step

FAQ

Candidate Merge — FAQs

What happens to email threads on the record that is retired? +
It depends on the system, and this is the detail most teams discover too late. Some products relink the entire conversation to the surviving profile, others leave threads tied to the original address so they vanish from view. Test it deliberately before merging real records, because losing sight of an in-progress conversation with a live candidate is worse than tolerating a duplicate.
Does merging affect a candidate who is mid-process on an open job? +
It can. If both records hold an application to the same requisition, you may end up with two applications on one profile sitting in different stages, and stage automation can fire unexpectedly. Merge active candidates carefully, ideally between stages rather than the day before an interview, and check the pipeline view afterwards to confirm nothing moved or duplicated.
Should merges be done in bulk or one at a time? +
One at a time for anything below an exact identifier match. Bulk merging is defensible only where the rule is unambiguous, such as identical email addresses, and even then it is worth running on a small batch first and inspecting the output. The cost of a wrong bulk merge scales with the batch size, and the errors are rarely obvious afterwards.
What do you do if two merged records turn out to be different people? +
Stop editing the profile and escalate to whoever administers the system, since further changes make reconstruction harder. Pull the system log to identify which records were combined and when, then rebuild from the source documents and original emails. Treat it as a data incident rather than a tidy-up, because mixing two people's histories has privacy implications beyond the inconvenience.
Built for recruiters & hiring teams

See Candidate Merge in action

Pitch N Hire unifies sourcing, screening and hiring decisions on one AI-native platform. Book a quick demo on your real roles.

Prefer to talk? Book a demo · View pricing

Free 1-user plan · No credit card · Talk to a real hiring expert

One Hiring Infrastructure.
Zero Tool Chaos.

Demos are consultative. We respect privacy and enterprise
governance. No lock-ins.

Start free Book demo