The Legacy Family Tree Standard Edition is a free Windows program, whereas the Deluxe Edition offers more features but must be bought. See the Migration Guide for migrating the exported GEDCOM and Media files into any Legacy version. Visit Legacy Family Tree for product details.
Legacy 9 offers one of the more complete GEDCOM implementations and supports Witnessed/Shared Events similar to FH.
Most Multimedia Conversion modes are supported.
The Character Set Encoding option defaults to UTF-8 but many Unicode characters are NOT supported.
The [[private]] Text Option defaults to Include private text but remove the [[ ]].
The Rich Text Formatting defaults to Reduce rich text to «b» «i» «u» «s» «sub» «sup» so basic font styles are retained but other formats become plain text.
After using the FH Plugin, run Legacy and on its File tab use Import > GEDCOM File option to choose the FH Plugin Export folder and Project…LFT UTF8.ged file to import.
Then simply accept all the default options to load the project and its media.
(LFT+) Full Data Export Details
All the (Std+) Full Data Standard GEDCOM Release 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 ZZ 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 ZZ 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.
Individual & Family Records (INDI, FAM)
★ Individual Tags (IDNO, ALIA, 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.
★ Custom Attribute (_ATTR, FACT)
See Extra Options tab Custom Attribute 1 _ATTR: or 1 FACT:
Each custom Attribute is converted to a custom Event using the EVEN tag, with any associated value retained on the tag line instead of a local Note.
★ Fact Witnesses (_SHAR, _SHAN)
See Extra Options tab Witness Role 2 _SHA%u:
Individual Witnesses are retained but Name Only Witnesses are moved to a Fact local Note with a Witness Role: label.
★ 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 (_EMAIL, EMAIL, _WEB, WWW)
See Extra Options tab Fact E-mail 2 _EMAIL: or 2 EMAIL: & Fact Website 2 _WEB: or 2 WWW:
These fields all become GEDCOM 5.5.1 tags as follows:
2 _EMAIL and 2 EMAIL become 2 EMAIL
2 _WEB and 2 WWW become 2 WWW
★ Fact Phone, Fax Number (PHON, FAX)
See Extra Options tab Fact Phone 2 PHON: & Fact Fax No. 2 FAX:
All Phone & Fax Numbers are appended to one PHON tag.
★ Source Citation (SOUR)
Any Source Citation/Note attached to a Note field is deleted, because they upset the Legacy import.
Any other Source Note is converted to a synthesised Source Record where the TITLe starts with ZZ Source Note: and followed by the original Source Note text.
★ Marriage Status (_STAT)
See Extra Options tab Marriage Status 1 _STAT:
The marriage Status custom tag of a Family Record is retained.
Note Records (NOTE)
★ Subsidiary Tags (SOUR, REFN, CHAN)
Any subsidiary tags are moved into the Note Record text.
★ Legacy Note Records
Legacy has three Note record tabs: General, Research & Medical and by default all exported Note records are allocated to the General tab with a Record Id starting with NI.
However, if the Note record text starts with (Research): or (Medical): then they become allocated to the matching tab by using Record Id starting with HI and MI respectively.
Source Records (SOUR)
★ Source Type (_TYPE)
See Extra Options tab Source Type 1 _TYPE:
The Source Type (_TYPE) is converted to a MEDI tag and all other fields retained.
Repository Records (REPO)
★ Record E-mail, Website (_EMAIL, EMAIL, _WEB, WWW)
See Extra Options tab Record E-mail 1 _EMAIL: or 1 EMAIL: & Record Website 1 _WEB: or 1 WWW:
These become GEDCOM 5.5.1 tags as follows: 1 _EMAIL or EMAIL to 1 EMAIL and 1 _WEB or WWW to 1 WWW
★ Record Phone, Fax Number (PHON, FAX)
See Extra Options tab Record Phone 1 PHON: & Record Fax No. 1 FAX:
All Phone & Fax Numbers are appended to one PHON tag.
Submitter & Submission Records (SUBM, SUBN)
★ See Other Options tab Submitter Record 0 @U%d+@: & Submission Record 0 @B%d+@:
Each Submitter & Submission record is converted to a synthetic Source record named ZZ Submitter: or ZZ Submission: plus the record Name and Id, with all details in the local Note.
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 tag to identify the primary photo, but only for the Media conversions (PART/FULL/ALL~LMO) via Local Media Objects.
★ Media Date (_DATE)
See Extra Options tab Media Date %d _DATE:
Each _DATE custom tag is retained.
Place Records (_PLAC)
★ Place Record (_PLAC, STAN, STAT, MAP, LATI, LONG)
See Extra Options tab Place Record 0 @P%d+@: option for Gedcom 5.5.1 Lat/Long.
Each Place record MAP, LATI & LONG plot structure is copied to every associated Place field.
Apart from that, the Place records are removed entirely.
Updated Change (CHAN)
See Extra Options tab Updated 1 CHAN:
The Updated CHANge date/time tags are all removed entirely.
(LFT-) Brief Data Export Details
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.