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

# Merging Duplicates

> Find and combine duplicate members and contacts, review what will change, and undo a merge

Duplicates accumulate. Someone registers twice with two email addresses, a
contact imported from a spreadsheet already exists as a member, or an event
attendee signs up again the following year without logging in.

Merging combines two records into one, keeping the history attached to both.

***

## Finding duplicates

**Administration** → **Merge**. Orgo suggests likely duplicate pairs it has
found in your organisation, so you do not have to hunt for them yourself. You can
also merge a specific pair you already know about.

<Note>
  If the suggestion list looks empty when you expect matches, check whether you are
  looking at contacts or at members. They are searched separately, and a member
  duplicated as a contact is a common case worth checking on its own.
</Note>

***

## Reviewing before you merge

Every merge shows a preview first. The preview is the point of the feature: it
tells you which record survives, which values are kept where the two disagree,
and what history moves across.

<Steps>
  <Step title="Pick the two records">
    Choose the pair from the suggestions, or select them yourself.
  </Step>

  <Step title="Read the preview">
    Check the surviving record, and check each field where the two disagree. An
    email address or a phone number that differs is exactly the kind of thing
    worth a second look before you commit.
  </Step>

  <Step title="Confirm">
    The merge runs, and history from both records is attached to the survivor:
    event registrations, payments, and memberships.
  </Step>
</Steps>

***

## Undoing a merge

A merge can be rolled back. Every merge is logged, and the log is what makes the
undo possible.

**Administration** → **Merge** → **History**, find the merge, and roll it back.

<Warning>
  Roll back promptly if a merge was wrong. The longer the merged record stays in
  use, the more new activity attaches to it, and new activity created after the
  merge is not part of what the rollback restores.
</Warning>

***

## What merging does not fix

Merging combines records that represent the same person. It is not the tool for
tidying up people who should not be in your database at all. To remove someone
entirely, delete the record rather than merging it into another one, so their
history is not silently attached to somebody else.