May 2025 Data quality

Merge Candidates and Contacts

ATZ CRM made it easier to merge duplicate candidates and contacts so recruiters can keep the database cleaner and reduce scattered relationship history.

Merge duplicate candidate records

Merge duplicate contact records

Reduce fragmented notes and communication history

Keep the recruitment database easier to trust

Quick answer

What changed for recruiters?

Merge Candidates and Contacts helps teams clean duplicate candidate or contact records inside ATZ CRM. Recruiters can combine true duplicates more easily, keep the primary record organized, and reduce confusion caused by split notes, communication history, ownership, or profile details.

What changed

What this update changes

ATZ CRM improved duplicate cleanup for candidates and contacts. When the same person has been created more than once, recruiters can merge records instead of leaving the team to choose between competing profiles.

Duplicate records usually appear after imports, manual entry, old spreadsheets, alternate email addresses, or shared sourcing work. This update gives teams a cleaner way to maintain one reliable record when the duplicates truly represent the same person.

Merge actions should still be used carefully. Recruiters should confirm identifiers before merging, because cleanup is helpful only when the selected records are genuinely duplicates.

Why it matters

Why it matters to recruiters

Recruiters are often measured on speed, quality, and follow-through. This update is designed to reduce manual work, protect useful context, and help teams keep hiring activity moving with fewer handoffs.

Cleaner candidate and contact data

Teams can reduce duplicate records that split activity, notes, communication, and ownership across profiles.

More reliable searching

A cleaner database makes it easier for recruiters to find the right person and trust the profile they open.

Better reporting confidence

Removing true duplicates helps stage, activity, and relationship reports reflect the real database more accurately.

Less confusion during handovers

Recruiters spend less time asking which duplicate profile is current when one maintained record is available.

Before and after

How the workflow changes

Before

Two candidate or contact records for the same person could split notes, emails, tasks, and ownership.

After

True duplicates can be merged so the team works from a cleaner primary record.

Before

Recruiters sometimes contacted the same person twice because duplicate profiles looked unrelated at first glance.

After

Database cleanup reduces duplicate outreach risk and makes record review clearer.

Before

Imported lists could introduce repeated contacts that stayed in the CRM indefinitely.

After

Teams can merge duplicates during cleanup after imports, sourcing pushes, or manual record creation.

How recruiters use it

How the workflow works

The exact setup depends on your workspace and permissions, but the core workflow is built to keep recruiters closer to the record, the next action, and the right team context.

1

Identify a likely duplicate

Use names, emails, phone numbers, company details, or history to decide whether two records are truly the same person.

2

Choose the primary record

Select the profile your team wants to keep as the main record before starting the merge.

3

Review the duplicate carefully

Confirm the duplicate profile belongs to the same candidate or contact before completing the action.

4

Clean up remaining details

After the merge, check ownership, key fields, notes, and follow-up activity so the maintained record is usable.

Feature-specific details

Extra context for this update

Some releases affect more than one recruiting workflow. These notes explain the practical details recruiters, admins, or managers may want to review before rolling the update out to the team.

Duplicate cleanup

What to check before merging records

Merging helps clean duplicates, but recruiters should confirm that the records truly belong together before combining them.

  • Compare email, phone, resume, company, and activity history before merging.
  • Keep the most accurate details when duplicate fields conflict.
  • Use merge carefully when one person has both candidate and contact context.

Quick answers

Common questions

When should recruiters merge records?

Merge only when the records are true duplicates of the same candidate or the same contact, not merely people with similar names.

Is merging different from linking?

Yes. Merging cleans duplicate records of the same type. Linking connects separate candidate and contact records when the same person has two legitimate workflow roles.

Why does duplicate cleanup matter?

Cleaner records reduce repeated outreach, make search results easier to trust, and keep reporting from being distorted by duplicate profiles.

Why do duplicate candidates and contacts happen?

Duplicates can come from imports, job applications, email parsing, sourcing, manual entry, or multiple teammates adding the same person.

What should teams review before merging?

Teams should review contact details, activity history, ownership, linked jobs, company context, and any notes that may be lost or combined.

See it in context

Review this update inside your recruiting workflow

Book a walkthrough with the ATZ CRM team to see how this update supports your jobs, candidates, and shortlist process.

Book a demo