The main purposes for exporting a Family Tree GEDCOM, an acronym for GEnealogical Data COMmunication, is a specification for exchanging genealogical data between different genealogy software. It is a file format that most genealogical programs and online trees recognise. file with or without Media are:
- To create a subset A Project is a Windows folder, created by Family Historian, which contains all your Family Tree information recorded in Family Historian. Normally located in the Documents\Family Historian Projects folder. using Project Window > New Project.
- To create a set of records for use with Merge/Compare File.
- To transfer a set of records to another person or genealogy product or website.
- To upload records to a website such as Ancestry or FindMyPast with sensitive private data removed.
They have some common pitfalls. The set of records may include everything, or just a partial family branch. A number of tools and Plugins are small programs that allow new features to be added without upgrading Family Historian itself; some plugins are written by Calico Pie and others are written by users. are available to help with the task. Also see how to Delete Data For Living People.
Export GEDCOM File Command
Whether exporting a GEDCOM file to create a New Project, Merge into another Project, or to transfer elsewhere, the initial process is the same.
Use File > Import/Export > Export > GEDCOM File, and to include all Every person in your tree will have a single Individual Record, which holds all the information about that individual that you have entered. You can view and edit Individual records in the Property Box Dialogue. click Add All.
Otherwise, click Select to invoke the Select Records dialogue and choose a subset of Individual records:
- Manually select any records from left-hand pane and click > Add to Selection button.
- Click Add using Querying is a very powerful feature that allows you to specify and save criteria for identifying a set of records of a given record type. button and choose any Query, such as All Relatives, Ancestors, or Descendants.
- Click Named Lists are a way in FH to group related items — which can be records of any type(s) — so that you can easily find them to work with. tab to choose any member records that must have been populated in advance, such as in how to Create an export Gedcom based on a diagram.
Review the Exclude records and Family Historian version 6 and below supports two types of Notes: Local notes (associated with a single person, record, or fact); and Shared Notes or Note Records, that can be linked to multiple records and/or facts. Version 7 introduced Research Notes. options, that usually should all be unticked, except perhaps Unconnected Records.
For the Media Records option select Use Full File Paths for External File Links such that the Media folder & file paths are retained. Otherwise, select Exclude to eliminate all the Media records & files.
The subsequent steps depend upon the purpose of the export as explained below.
Note that the Split Tree Helper has options to delete Notes, Facts are one of the key concepts at the heart of Family Historian; they are how you record the things that happened to, or described, each ancestor (Individual)., and Flags, etc, not provided by the Export > GEDCOM File command, but involves a rather more complicated process. See Export to Website Without Sensitive Data below.
There is an All Pool Relatives Except Partner Ancestors Plugin to populate a Named List of specific ancestral branches as discussed in this thread:
Export to Create/Merge Projects
When exporting a GEDCOM file with associated Media files to create or merge into another Project, it is desirable if the Media folder & file paths are retained.
When the File > Project Window > New Project > Import a GEDCOM file or the File > Merge/Compare File  command is used, the GEDCOM file to select will be the one saved as described below.
Use the Export GEDCOM File Command options (as described above) to choose the records, and leave the other options at default values. After clicking OK, do NOT use the Public folder offered by default. Instead Save the GEDCOM file in the ….fh_data folder adjacent to that Public folder, so that the exported file sits next to the Project master GEDCOM file.
When this exported GEDCOM file is used to create or merge into another Project, its linked Media folders & files should get copied across automatically and retain the original folder hierarchy.
If the above technique is NOT employed, then the linked files will all get copied directly into the target Project Media folder, losing the original folder structure.
The GEDCOM file MUST be in the same folder as the Media folder containing the media folders & files.
The discussion thread below led to the solution given above.
Export to Another Person or Product
When exporting to another person or genealogy product, there are several pitfalls due to the various dialects of GEDCOM in use.
Use the Export GEDCOM File Command options as described above to choose the records, but set the other options as described below.
Many online products such as Ancestry, FindMyPast, MyHeritage, and ZoomPast do not automatically upload Media files, so there is usually little point in retaining them, and this section can be skipped. However, there are some Special Media Cases described below.
When exporting a GEDCOM file with associated Media files it is important that the file path links are retained.
Strangely, GEDCOM 5.5 specifies a FILE path link for Local Media files, but NOT for Media Records, so to remain compliant Family Historian uses a custom _FILE path link in Media Records. However, several genealogy programs use the GEDCOM 5.5.1 FILE path link in Media Records as a de facto standard, and do NOT recognise custom _FILE path links.
One workaround would be to post-edit the exported GEDCOM file and replace every _FILE with FILE.
Since ƒh V5 the File > Import/Export > Export > GEDCOM File command offers a solution. For Destination: choose Family Tree Maker and not only are useful default settings suggested, but also FILE path links are used in Media Records although this is not mentioned in the Help. In ƒh V6.2 a Destination: of Default similarly uses FILE path links. The Export Gedcom File Plugin has similar options.
As an alternative workaround, a user was trying to use Local Media instead of Media Records, but found Merge/Compare File insisted on converting one to the other. The discussions below explained how to thwart that behaviour and revealed the solution given above.
- Leave local multimedia on Merge/Compare File June/July 2013
With the advent of ƒh V6, its GEDCOM file uses Unicode UTF-16 encoding, which makes it unrecognisable to many other genealogy products, and it includes Place (_PLAC) records and A Witness is somebody who played an important role in an event (or rarely, attribute) but were not a Principal, e.g. they could have been a bridesmaid at a wedding, rather than one of the individuals getting married. (_SHAR) links that are not even recognised by ƒh V5 or earlier.
There is a Tools > Preferences > File Load/Save option to Save in UTF-8 file format, or the File > Import/Export > Export > GEDCOM File command Format also offers UTF-8, but neither solve the problem of ƒh GEDCOM Extension List custom tags (such as _PLAC and _SHAR) being unrecognised by most other products.
In ƒh V6 or later the File > Import/Export > Export > GEDCOM File command does allow Place records to be excluded along with all their Media, Lat/Longitude, etc.
The solution is to use the Export Gedcom File Plugin. That can be preceded by the Export GEDCOM File Command if a subset of records is required, and when it asks Do you wish to open another instance of Family Historian to view the exported file? answer Yes and run the Plugin on the exported file.
Export to Website Without Sensitive Data
This process involves more steps & tools with different options than those above in order to remove all private or sensitive data especially for living people. If it is known in advance that this will be an objective, then it is beneficial to use the [[private]] text notation in Note and other text fields, and set the Living record Flag appropriately by using the Flag Living Query.
Export > GEDCOM File Command
Follow the Export GEDCOM File Command advice given above, but choose to Exclude all unwanted records, and when it asks Do you wish to open another instance of Family Historian to view the exported file? answer Yes and run the steps below on the exported standalone GEDCOM file.
Clean Unwanted Fields Plugin
This step is only needed if there are particular unwanted data fields.
Use the Clean Unwanted Fields Plugin to globally remove any fields. It is easily edited for any required Data References, but defaults to a useful set for Ancestry.
Alternatively, create Custom Queries to show the unwanted fields in a Result Set. Then for each field, sort their Column, select all the cells, and hit the Delete key. It may be necessary to create Individual, Family, Fact, and Source type Queries to handle all the fields.
Clean Living Persons Plugin
Use the Clean Living Persons Plugin to privatise the Name of all Living people, and remove their Fact, Note, Media, Source, or other details. See the plugin’s Help & Advice.
Trim Date and Text Fields Plugin
Use the Trim Date and Text Fields Plugin to reduce the details in Date, Note, Address & Place fields so that visitors to the online tree are encouraged to contact the owner to confirm matches and obtain the details. See the plugin’s Help & Advice.
File > Split Tree Helper Command
Optionally use the Split Tree Helper to delete Note, Media, Source & Repository records with no links to them, delete all Submitter & Submission records, delete all Note fields or [[private]] text within records, delete all record Flags, delete all Named Lists, and delete any specified Facts.
In some cases, such as using delete all Note fields, not all records with no links are deleted, so the command should be used twice with the same settings.
Export Gedcom File Plugin
Use the Export Gedcom File Plugin for the chosen target website such as (ANC) Ancestry Family Tree, (FMP) FindMyPast Family Tree, (MYH) MyHeritage Family Tree, (ZPG) ZoomPast Genealogy, etc.
This offers another opportunity to remove When you add a picture, video, sound recording, document file etc into a Family Historian project, a Media record is created to represent that media item within the project; the Media record includes a link to the actual Media file. and exclude [[private]] text.
On the Extra Options tab the following settings may be beneficial, especially for Ancestry, and are mostly selected by choosing the (-) Brief Data mode on the Basic Options tab:
- Name List Entry 1 _LIST: Remove entirely ~ (unnecessary if Named Lists deleted in Split Tree Helper)
- File Root 1 _ROOT: Remove entirely
- Given Name 2 _USED: Remove entirely
- Record Flags are a way of marking an Individual record. 1 _FLGS: Remove entirely ~ (unnecessary if record Flags deleted in Split Tree Helper)
- Marriage Status 1 _STAT: Remove entirely
- Witness Role 2 _SHA%u: Remove entirely
- According to GEDCOM, a Place should hold “The jurisdictional name of the place where the event took place…” 0 @P%d+@: Remove entirely
- To/From Place 2 _PLAC: Remove entirely
- Source: “where information was found”. This could be anything from an archive in a county records office, a book, or even a relative’s recorded recollection. Citing your Sources helps to show how you reached a particular conclusion about an Individual. Type 1 _TYPE: Remove entirely
- Fact “The address structure should be formed as it would appear on a mailing label…”, according to GEDCOM; however, this is capable of a number of interpretations, and Address and Place are best considered together. %d ADDR: experiment with different settings
Many of those are unnecessary if removed by the Clean Unwanted Fields Plugin.
Finally click the Export GEDCOM… button and upload the resultant GEDCOM file from the Export folder to the website as advised by the Export Gedcom File ~ Output Formats for the chosen target product Import Details.
There are some techniques that allow Multimedia to be uploaded to online websites in bulk. Please ask in the Importing and Exporting Forum if you need more detailed advice on these techniques.
FindMyPast Zipped Folder
The plugin’s Help and Advice explains how it may be possible to bulk upload Multimedia using a Compressed (zipped) folder technique.
Ancestry via RootsMagic
A Project with Media can be exported to RootsMagic and use its TreeShare for Ancestry capability to upload the Project with Media images to Ancestry. Note that the RootsMagic Essentials version is free.
ZoomPast via Online Trees
Once a Project with Media exists online in such as Ancestry or FindMyPast, then a GEDCOM can be exported and imported to ZoomPast and any URL links to Media will be honoured.