Manage DNAGedcom Files EAP

Overview

Manage DNAGedcom Files copies the gathered data for the kits you choose from one DNAGedcom database into another. Use it to bring kits from an old database into your current one, to combine databases kept on two computers, or to split one family's kits out into a database of their own.

The page is in the Client under Data > Manage DNAGedcom Files. It does not need a subscription level.

It copies; it does not move. Nothing is removed from the database you copy from. After a copy the kit is in both.

Copying Kits

Copy from starts as the database the Client is using. To copy from a different one, click Browse… and choose it. The kits found in it are listed.
Set Copy into to the database that should receive the kits. It must already exist and be a DNAGedcom database; this page does not create one.
Every kit starts ticked. Untick the ones you do not want.
Click Copy selected kits. The copy starts straight away, and each kit is reported in the log as it finishes.

The two paths on this page are only for the copy. They do not change which database the Client works with; that is set in Settings.

What Is Copied

Company	Copied for each kit
A*	Matches, shared matches, match groups, and the trees gathered for the matches.
FTDNA	Matches, shared matches, chromosome segments, and match trees.
MyHeritage	Matches, shared matches, chromosome segments, and match trees.
GEDmatch	Matches, shared matches, and chromosome segments.
23andMe	Relatives, shared matches, and chromosome segments.

What Is Not Copied

GEDCOM files you loaded in My Trees, and which tree is assigned to which kit. Load the GEDCOM again in the other database.
Anything from the People pages. People are kept in your GDAT database, not in the DNAGedcom database, so they are not affected by a copy.

Copying a Kit Again

Copying a kit that is already in the target is safe. That kit's data in the target is replaced with what is in the source, so nothing is duplicated. Other kits in the target are left alone.

Because the kit is replaced, copy from the database that has the newer gather into the one with the older, not the other way round.

If Something Goes Wrong

Message	What to do
Set the target database path first (Browse…).	Copy into is empty, or the file does not exist. Choose an existing DNAGedcom database.
Source and target are the same database. Choose two different files.	Both boxes point at the same file.
The target file does not look like a DNAGedcom database…	The file you chose is some other kind of database. To make a new, empty DNAGedcom database, create one in Settings first.
No kits with gathered data were found in the source database.	The source has no gathered kits, or is not the file you meant.
… warning(s), see the log.	Part of a kit could not be copied, usually because one database is from a much older version of the Client. The log names what was skipped. The rest of the kit, and the other kits, were still copied.

Each kit is copied as a whole. If one kit fails, it is left as it was in the target and the others continue.

Database — where the Client keeps its data and how to switch databases.
Push to GDAT — send kits to a GDAT database.