> ## Documentation Index
> Fetch the complete documentation index at: https://docs.letsconnekt.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Merge Duplicate Candidate Records in Connekt

> Consolidate duplicate candidate records without losing any history — find duplicates, choose a primary record, resolve conflicts, and confirm the merge.

Duplicate records are a fact of life in any busy recruitment database — the same candidate may be added twice from different sources, or re-entered after a gap. Connekt's merge tool lets you consolidate two records into one without losing any of the history, submissions, or documents attached to either. The process takes just a few clicks, but it's permanent, so it's worth taking a moment to choose the right primary record before you confirm.

## Merging Two Candidate Records

<Steps>
  <Step title="Open the record you want to keep">
    Navigate to **Candidates** and open the candidate profile you want to be the **primary record** — this is the record whose ID and URL will be preserved after the merge.
  </Step>

  <Step title="Launch the Find Duplicates tool">
    Click **Find Duplicates** in the candidate detail view. Connekt automatically searches for likely duplicates by matching on name, email address, and phone number.
  </Step>

  <Step title="Select the duplicate to merge">
    Review the list of suggested duplicates and select the record you want to merge into the primary. Click the record to inspect it if you're unsure which one to keep.
  </Step>

  <Step title="Click Merge">
    Click **Merge** to begin the merge process.
  </Step>

  <Step title="Confirm the primary record">
    You'll be asked to confirm which record is the **primary**. The primary record keeps its ID, URL, and core data — make sure you've selected the right one.
  </Step>

  <Step title="Resolve any conflicting data">
    Where both records contain different values for the same field — for example, two different phone numbers or addresses — Connekt prompts you to choose which value to keep. Review each conflict and select your preferred data.
  </Step>

  <Step title="Confirm the merge">
    Review your choices and click **Confirm Merge** to complete the process.
  </Step>
</Steps>

## What's Preserved After the Merge

Everything from the secondary record is transferred to the primary — nothing is lost:

* Submissions and placements
* Work experience, education, languages, and social profiles
* Notes and attachments
* Any linked jobs

The secondary record is removed from your active candidate list, and all the data it held moves to the primary record.

<Tip>
  Before merging, open both records side by side in separate browser tabs so you can compare them and confidently choose the primary record and any conflicting field values.
</Tip>

## Important: Merges Are Permanent

<Warning>
  Merges **cannot be reversed** from the Connekt UI. Once you confirm, the secondary record is gone and cannot be restored. Double-check your primary record selection and your choices for conflicting data before clicking **Confirm Merge**.
</Warning>

## Keeping Your Database Clean

<Accordion title="When should I merge vs. leave records separate?">
  Merge when you're confident both records represent the exact same person. If there's any doubt — for example, two people with the same name at different companies — leave the records separate and add a note to clarify the distinction.
</Accordion>

<Accordion title="Can I find duplicates across my whole database?">
  The **Find Duplicates** tool searches for matches against a specific candidate record. For a broader database cleanup after a bulk import, open each recently imported record and run Find Duplicates to catch overlaps with existing records.
</Accordion>

<Accordion title="What if the duplicate has a more complete profile?">
  You can choose either record as the primary. If the "duplicate" record is actually the richer one, open it first and run Find Duplicates from there — that way it becomes the primary and keeps its data and ID by default.
</Accordion>