0

Export Gedcom File (MYH) MyHeritage Family Tree Builder

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 MyHeritage for product details. See the Migration Guide for migrating the exported GEDCOM and Media files into the MyHeritage products.

Some modes of Multimedia Conversion allow images to be imported to Family Tree Builder and uploaded to the website as explained in the Migration Guide below.

The Character Set Encoding defaults to UTF-8 with all Unicode characters supported.

The [[private]] Text Option defaults to Include private text but remove the [[ ]].

The Rich Text Formatting defaults to Change rich text into HTML 5 format so most text formatting is retained but only in Notes.

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

Migration Guide
Family Tree Builder

After using the FH Plugin, run MyHeritage Family Tree Builder and use File > Import GEDCOM to 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.
Use the Reports > Open Reports Folder command to reveal an Import Issues – …txt file.
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.

(MYH+) Full Data Export Details

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

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.

★ 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, ADR3, 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 Cause (CAUS)
The Cause field is moved to a Fact local Note with a Fact Cause: label, except for Death Events.

★ Fact E-mail, Website, Fax, Phone (_EMAIL, EMAIL, _WEB, WWW, FAX, PHON)
See Extra Options tab Fact E-mail 2 _EMAIL: or 2 EMAIL: & Fact Website 2 _WEB: or 2 WWW: & Fact Fax No. 2 FAX: & Fact Phone 2 PHON:
Any Fact E-mail, Website, Fax or Phone field is converted to a Fact local Note with an E-mail Address: or Website Address: or Fax Number: 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.

Repository & Submitter Records (REPO, SUBM)

★ Record E-mail, Website, Fax (_EMAIL, EMAIL, _WEB, WWW, FAX)
See Extra Options tab Record E-mail 1 _EMAIL: or 1 EMAIL: & Record Website 1 _WEB: or 1 WWW: & Fact Fax No. 2 FAX:
These become GEDCOM 5.5.1 tags as follows: 1 _EMAIL or EMAIL to 1 EMAIL and 1 _WEB or WWW to 1 WWW and 1 FAX to 1 FAX

Media Records & Local Media Objects (OBJE)

★ 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.

Custom Id, Date Field (REFN, DATE)

★ Custom Id, Automated Id (REFN, RIN)
Every record Custom Id is moved to the record Note with a Custom Id: label.

★ Date Field (DATE)
See Extra Options tab Date Field %d DATE:
Any Interpreted Date Phrase is moved to the local Note with just the actual Date retained.

(MYH-) Brief Data Export Details

All the (Std-) Brief Data Standard GEDCOM Release 5.5 rules apply together with the (MYH+) Full Data Export Details defined above.

Return to the GEDCOM Export Mode advice help page.

Return to the Export Gedcom File main help page.


Plugin Export Gedcom File

Help content on this page is owned and provided by Mike Tate, the plugin's author, Calico Pie takes no responsibility for its content.