Export Gedcom File ~ (MYH) MyHeritage Family Tree

Introduction

MyHeritage offers website Family Trees synchronised with the Family Tree Builder Windows program both as free and premium products. There are also iOS and Android apps in support of the website. Visit https://www.myheritage.com/ for details.

See the Import Details for migrating the exported GEDCOM into any MyHeritage products.

The Character Set Encoding works for UTF-8 and all Unicode characters are supported.

Some Media conversion modes allow images to be imported to Family Tree Builder and uploaded to the website as explained in the Import Details below.

See both the (MYH+) Full Data Export Details and (MYH-) Brief Data Export Details below.

(MYH+) Full Data Export Details

All the (Std+) Full Data Standard GEDCOM 5.5 rules apply except as defined below.

Header Record (HEAD)

★ Named List Entry (_LIST, _FLAG, _NOTE, _IDS)

See Extra Options tab Named List Entry 1 _LIST:

The details of each Named List are placed in a synthesised Source Record whose TITLe starts with Ω Named List:, and each associated Record has a link to the Source Record either directly or via a local Note (except for Submitter & Submission records that disallow such links).

★ File Root (_ROOT)

See Extra Options tab File Root 1 _ROOT:

The File Root details are placed in a synthesised Source Record whose TITLe starts with Ω File Root:, and the associated Individual Record is linked to this record.

The Individual Record itself is moved to just after the HEADer record to become the Root Person.

★ Other Tags (FILE, _VAR, _UID, SUBM)

These tag lines are all removed.

Individual & Family Records (INDI, FAM)

★ Name Fields (GIVN, SURN, _USED)

See Other Options tab Name Given 2 GIVN: & Surname 2 SURN:
See Extra Options tab Given Name 2 _USED:

Some Individual Name fields are moved to avoid being ignored:
2 GIVN is moved to a Name Given: label in the Record local Note.
2 SURN is moved to a Surname: label in the Record local Note.
2 _USED is appended to the Nickname (2 NICK) field.

★ Media (OBJE)

All links to Media Records and local Media Objects are converted according to the Basic Options chosen.

For each Individual record, the most preferred Media tab item without Exclude from Diagrams set, gains the _PRIM Y, _PRIM_CUTOUT Y, and related tags to identify the Associated Personal Photo, but only for the Media conversions (PART/FULL/ALL~LMO) via Local Media Objects.

★ Fact Cause (CAUS)

The Cause field is moved to a Fact local Note with a Fact Cause: label, except for Death Events.

★ Individual/Family Tags (AFN, ALIA, ANCI, DESI, RIN, RFN, SUBM)

Each tag is converted to a synthetic custom Event using the EVEN tag with any value on the same line.

★ Associated Person (ASSO)

Each ASSOciated Person is converted to a custom Event using the EVEN tag with a Fact local Note with an Associate: and Relationship: label.

★ Address Fields (ADDR, ADR1, ADR2, CITY, STAE, POST, CTRY)

See Extra Options tab Fact Address 2 ADDR:

All Address fields are appended to the Fact local Place field following the word at.

★ Fact E-mail, Website, Phone (_EMAIL, _WEB, PHON)

See Extra Options tab Fact E-mail 2 _EMAIL: & Fact Website 2 _WEB: & Fact Phone 2 PHON:

Any Fact E-mail or Website or Phone field is converted to a Fact local Note with an E-mail Address: or Website Address: or Phone Number: label.

★ Source Note (SOUR)

Any Source Note is converted to a synthesised Source Record where the TITLe starts with Ω Source Note: and followed by the original Source Note text.

Source Records (SOUR)

★ Source Record (ABBR, _TYPE)

Each Source Record Short Title (ABBR) is converted to a full TITLe, unless that already exists, whereupon it is converted to a Record local Note with a Short Title: label.

See Extra Options tab Source Type 1 _TYPE:

Each Source Type (_TYPE) field is converted to a Record local Note with a Source Type: label.

Repository Records (REPO)

★ Record E-mail, Website (_EMAIL, _WEB)

See Extra Options tab Record E-mail 1 _EMAIL: & Record Website 1 _WEB:

These fields are converted to Gedcom Draft 5.5.1 tags as follows:
1 _EMAIL becomes 1 EMAIL
1 _WEB becomes 1 WWW

Custom Id Field (REFN)

Every Custom Id is moved to the record Note with a Custom Id: label.

(MYH-) Brief Data Export Details

All the (Std-) Brief Data Standard GEDCOM 5.5 rules apply together with the (MYH+) Full Data Export Details defined above, except that all the Header Record (HEAD) tags mentioned are removed.

Import Details

Family Tree Builder

Use File > Import GEDCOM and Browse for the Project…MYH UTF8.ged file in the fh Plugin Export folder, then click Next to progress through the dialogues.

Ensure the Primary Language is set correctly, adjust the Project name as required, and View Issues before clicking Finish.

After all the media Photos, etc, have loaded, use File > Close Project to allow them to be adjusted by the program, which may take a while and say (Not Responding). Use File > Open Project and all the media should have imported with correct record Associations and Personal Photo selections. The media all appear online when synchronised with the website.

The Residence (RESI) facts and Physical Description (DSCR) facts do not appear anywhere in the Edit Details tabs, but do appear online when synchronised with the website.

Website Family Trees

Login to MyHeritage.com, select Family tree > Import GEDCOM and Browse for the Project…MYH UTF8.ged file in the fh Plugin Export folder, then click Upload and wait for a confirmation E-mail.

No media Photos, etc, are automatically uploaded by this direct import.

The Residence (RESI) facts appear in the Events list and Contact info, and the Physical Description (DSCR) facts appear in the Personal info.

The fact tags ADOP and BLES are displayed instead of the names Adoption and Blessing.

These Website Family Trees can synchronise with the iOS and Android apps.

CC Attribution-Noncommercial-Share Alike 4.0 International
Runs using DokuWiki Recent changes RSS feed www.rjt.org.uk