Profile Keys

GDAT currently supports data from a number of pre-determined sources. Each Profile needs a Profile Key for each relevant source to import that data.

Accuracy of the data entered for each the Profile Key is critical; validate and then re-validate.

Profile Keys are used when Imports need to “Find Profile in File”. Without valid keys entered into the profile set up, imports can fail, and time can be wasted.

The following is to provide help in locating and accurately identifying the different Profile Keys.

Ideally, you should only have one Profile Key for each source. The example shown is to show the format of the currently supported sources profile keys.

It is best if you can pick a download method and stick with that as you move forward in time to avoid potential duplication, however most source profile keys are identical regardless of download method. Only FTDNA needs careful consideration going forwards.

To enter a new Profile Key

  1. Select a profile from the left hand side of the screen

  2. Click the dropdown at the bottom of the Profile Key area and select a source.

  3. The new Profile Key is entered in the space to the right. Check the sections below to ensure you are entering a valid profile key.

  4. Click "Save Key" to save the key to the profile, and click "Okay" to continue.

When complete, clicking on a profile in the Profile tab will populate the Profile Keys that were previously entered as profile values. This area will look something similar to what's shown above.


This is typically a 16 character alphanumeric string, can contain both letters and numbers, or numbers only.

  1. Click on your name in the top right of the screen, and select “View Your Profile”

  2. In the address bar, your needed ID is the portion at the end.

This match key is the same regardless of your download and importation method.


There are two possible keys for FTDNA depending on your download method. It is preferable that you pick one download method and stick to it, as duplicates will occur if both methods are used.

The DNAGedcom Client method is preferred due to the downloaded files containing a unique key for each relative record.

via DNAGedcom Client

This is a string that does not contain any letters. It is not the same as the kit number you use to log in to FTDNA.

Data gathered before 30 June 2021 will have had a match key of a numerical string of between 3 and 7 (or more) numbers. Data gathered after July 1 2021 will have a match key that is an Alphanumeric string of 24 characters, typically ending with == .

If you have collected data prior to and after the July 1 2021 date, please review the "Add New FTDNA Unique Keys on the Database Routines page.

When using the DNAGedcom Client, the FTDNA Kit ID is shown in the client window after successful logon to FTDNA. If it is not shown immediately, it should show after the first run has been completed.

via FTDNA Website

Strictly speaking, you won't need a key if you are downloading direct from FTDNA, however, you may choose to use the name in Cell A2 of the Chromosome Browser file downloaded from the website as your Profile Key in GDAT, but it is not recommended to collect and import FTDNA matches via the direct download method due to there being no unique key. The biggest risk with direct download is, if you have two matches at FTDNA with the same name, it is very possible to have these inadvertently merged into a single relative on import. There is nothing that GDAT can do to avoid this when using the Direct Download method.

You would also need to create your own import templates if you choose to obtain FTDNA data via this method.

Note: If you set up with one method and then switch to the other method at a later time, you will get duplicates. It is possible to merge duplicate records one at a time (a very time consuming process) and then proceed as normal.


The MyHeritage key is a 38 character alphanumeric string embedded at the front of what is a dual key, that of your kit and of the match you are viewing. It is not the very short code listed on the Manage DNA Kits page. Nor is it the full string

Note: If your MyHeritage imports do not work, please check that your match key is set up correctly as this will be the prime suspect for an import fail.

On the MyHeritage website, go to your DNA matches page, then select any match and click “Review Match”

The URL on this page should have the format of:

The portion in bold and highlighted in grey is your needed Profile Match Key. Take care not to capture any extra characters when copying it.

If you have linked profiles at MyHeritage and therefore have access to the match lists, but for some reason can not locate the Match Key for the other profiles, try this:

  1. Locate the key for the primary MH profile and enter it into the corresponding GDAT profile

  2. Load the MH data for that Profile

  3. In the resulting Match List, find the second MH profile as a match

  4. Copy the MH match key from the Relative Notes view

  5. Add this match key to the correct GDAT profile

  6. Repeat for any other MH profiles as needed.


Depending on when you transferred to Gedmatch, your kit number may be a single letter followed by 6 numbers, or it may be two letters followed by 7 numbers. Both are accurate.

Your Gedmatch ID is the same for both Basic access and Tier 1 access.

On the left hand side, under “Your DNA Resources” you will find your GedMatch Kit IDs. These kit numbers are the same numbers needed for GMPro.

Other Sources

The "Archived" match key field is left over from Genome Mate Pro as a courtesy to those who have converted their database from GMP to GDAT and have data imported from sources that are not supported by GDAT.

If you have added a custom source within the Preferences area, your custom source names will appear in the drop down list. The format of your match key will rely on your source, and you will need to determine this format for yourself.

Hidden Characters

Match Keys can be obtained from a variety of locations. If your match key is coming from a csv file downloaded from a testing company, then you may be able to enter this by a simple copy/paste of the relevant cell. However, there are times when “hidden characters” are needed, or incorrectly captured, resulting in failed imports. The following example shows how to capture just the required information.

Put the cursor on your chosen cell - in this example I’ll use cell A2

Press F2 on the keyboard, or double click on the cell. You should now see the cursor blinking at the end of the cell’s data.

Press Shift and Home on the keyboard to ensure that all of the cell contents are highlighted.

This also catches extra spaces that may not otherwise be easily seen.

Copy this and paste it into the Match Key field, or where ever else it is needed.

This process can be repeated for any field that needs data from an Excel CSV file.