Written by Generation Archives. This is a method that works in any tree program. Menu names differ between apps, so we describe the steps in general terms and say so where our own app is different.

How to merge duplicate people in a family tree without losing facts

Published by Generation Archives on November 5, 2026.

Almost every tree that has been alive for a few years contains duplicates. Two entries for the same grandmother, one with a maiden name and one without. A cousin who was added twice from two different imports. A man with the same name as his father, split into two people or merged into one. Merging fixes the first problem and creates the second if you are careless. This guide explains how duplicates arise, how to confirm they are the same person, and a safe order of steps.

How duplicates happen

Importing the same family twice, or importing a file from a tree that already overlaps with yours.
Several people adding relatives without checking whether they exist.
Different spellings. "Catherine," "Katherine," and "Kate" entered by three people.
Married and maiden names. The same woman entered under each.
Missing information. "John Hale, born about 1850" added twice because the first entry had no place.
Remarriage. A person is added once as a child of the first marriage and again as a partner in the second.
Splitting by mistake. A person is added again because a record seemed to describe a different one.

Knowing the cause helps you find the rest. If duplicates came from an import, look for the batch of people the import added.

The risk: merging the wrong people

Merging two entries is easy. Un-merging is hard. If you fold two real people into one, their parents, spouses, and children become tangled, and the mistake can spread to everything connected. Two men named John Hale in the same county may be father and son, or cousins, or unrelated. It is worse to merge two real people than to leave one duplicate unmerged.

So the rule is: merge only when you are confident, and always make a backup first.

Step 0: back up first

Export a GEDCOM and save it with today's date in the name. If you are working in an app that does not let you undo a merge, this is your undo. See how to export a family tree as GEDCOM and how to back up a family tree.

Step 1: find candidates

Look for:

The same name appearing more than once, including variant spellings.
People with the same parents and a similar birth year.
People with the same spouse.
People with a lot of blank fields and a name that matches someone fuller.
Orphans, with no parents or children attached, whose name matches someone in a family.

Many programs have a duplicate finder. If yours does, treat the results as suggestions, not answers.

Step 2: compare, side by side

For each pair, put both entries next to each other and compare:

Check	What to look at
Names	Given names, surnames, birth names, nicknames
Birth	Date and place. Close or identical is a strong sign
Death	Date and place
Parents	Same parents? Same family?
Spouses	Same spouse or spouses?
Children	Same children? Overlapping?
Sources	Does a document or note tie the two together?
Photos	Same face?

Strong evidence: same parents, same spouse, same children, and a birth within a year or two.

Weak evidence: the same name alone. Many people share names, and families reuse names across generations.

A red flag: an entry that would be a parent of itself, or a "father" and "son" whose birth dates are only a few years apart. Those usually mean two different people, or one person entered twice with a wrong date.

If you cannot decide, do not merge. Put a note on both entries, such as "possible duplicate of the other John Hale, not confirmed," and come back when you have more.

Step 3: decide which entry to keep

Pick the entry that:

Has the most sources and notes,
Has the most relationships attached,
Has the cleanest name, and
Is the one other people are most likely to be using, if the tree is shared.

Call this the keeper. The other one is the duplicate.

Step 4: copy over what the keeper lacks

Before you remove anything, go through the duplicate and move useful facts to the keeper:

Alternate names and spellings. Keep them in a note or as alternate names.
Birth, marriage, and death facts that the keeper does not have.
Notes and biographies. Combine them, and label where each came from.
Photos and tags. Attach the photos to the keeper and re-tag the person.
Sources. Preserve every citation.

If the two entries disagree, keep both versions in a note, with their sources. See how to cite a photo, letter, or interview.

Step 5: move the relationships

Next, make sure the keeper has every relationship the duplicate had:

Parents. If the duplicate had parents the keeper lacks, add them to the keeper.
Spouses. Link each spouse to the keeper.
Children. Re-link each child so the keeper is the parent.

This is the step where mistakes show up. A child who ends up with two sets of parents because one link was not removed is usually a sign that the duplicate had an extra relationship that the keeper also has. Check each child.

Some apps move relationships automatically when you merge, and some leave them for you to fix. In Generation Archives, a person can have any number of parents and multiple spouses, so check carefully that you link the right people and do not leave an extra link behind. Look at the family afterward the way a family group sheet would show it: one couple and their children in birth order.

Step 6: remove the duplicate

Once the keeper has everything, delete the duplicate. Then look at the keeper and its family.

Do the parents have the right children?
Is anyone listed twice as a child?
Are the dates consistent?
Are the photos attached?

Step 7: fix the next level

A duplicate person often means duplicate relatives. If both versions of John Hale had a wife named Mary, there are probably two Marys. Work outward from the person you merged, and check their parents, spouses, and children for duplicates too.

Step 8: record what you did

Add a short note to the keeper: "Merged with a duplicate entry on 5 November 2026. Both had the same parents and spouse. Birth year differed (1850 and 1851); both retained in notes." That is useful if someone later asks why a date looks odd.

Merging after an import

If an import created a lot of duplicates, do not merge them one by one if you can avoid it. Consider whether it is easier to start again. In Generation Archives, an import creates a new tree and does not change an existing one, so you can compare the imported tree to your original before deciding what to keep. How to import a GEDCOM lists the checks to run after an import.

When not to merge

Same name, different parents. They may be different people.
A father and a son with the same name. Look for "Sr." and "Jr."
A person and their stepchild or adopted relative with the same given name.
Uncertain dates. If one says 1850 and the other 1880, they are probably different.
When you cannot back up first.

Frequently asked questions

Can I undo a merge?

It depends on the program. Many cannot undo. That is why you export a backup first.

What if the two entries have different birth dates?

Keep both in a note with their sources, and choose the best-supported one as the main date. Do not average them.

What if I think two people are the same but I am not sure?

Leave both, and add a note to each saying they may be the same person and why. Revisit when you have more evidence.

Do I need to merge duplicates at all?

In a very small tree you keep to yourself, a stray duplicate may not matter much. In a shared tree, yes. Duplicates confuse relatives, split photographs, and make errors harder to find.

How do I avoid duplicates in the first place?

Search before you add a person. Use a consistent name format. Decide who adds people if several relatives help, and tell them to check first.

Try the demo Sample tree Create a free account

All guides