All the Ancestry websites support a Family Trees option to upload GEDCOM files as described in the Import Details below. Visit https://www.ancestry.co.uk/ for details.
The Character Set Encoding options for ANSI & UTF-8 and all Unicode characters are supported.
By default all Media are excluded because Ancestry does not upload them.
See both the (ANC+) Full Data Export Details and (ANC-) Brief Data Export Details below.
All the (Std+) Full Data Standard GEDCOM 5.5 rules apply except as defined below.
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 Individual/Family Record has a link to the Source Record.
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 be treated as the root record.
See Extra Options tab Custom Attribute 1 _ATTR:
Each custom Attribute is converted to a custom Event using the EVEN tag, with any associated value in its local Note with an Attribute Value: label. See ★ Notes (NOTE) below.
Alternatively, the Extra Options tab setting of Custom Fact & Value works well by using the EVEN tag, with its value on the same line.
Each tag is converted to a synthetic custom Event using the EVEN tag with any value on the same line.
See Other Options tab Census Event 1 CENS:
Each Individual Census event is converted to a Residence fact to improved Census hints in Ancestry.
Each ASSOciated Person is converted to a custom Event using the EVEN tag with a Fact local Note with an Associate: and Relationship: label. See ★ Notes (NOTE) below.
See Other Options tab Fact Person Age 2 AGE: & Fact Husband Age 2 HUSB: & Fact Wife Age 2 WIFE:
Each AGE field is moved to the Fact local Note with an Individual's Age: or Male/Lady Partner Age: label. See ★ Notes (NOTE) below.
See Extra Options tab Fact Address 2 ADDR:
All address fields are converted to a Fact local Note with a Fact Address: label. See ★ Notes (NOTE) below.
Alternatively, the Extra Options tab setting of Move to Event Value or Move to Place Field both work well.
See Extra Options tab Record Note 1 NOTE: & Subsidiary Note %d NOTE:
Every Individual/Family Record level Note and every local Note and Note Record is moved to a synthesised Source Citation named Ω Note.
Where necessary a synthesised custom Event is created such as Ω Individual Record Note or Ω Family Record Note or Ω Individual Parent Note or Ω Individual Spouse Note to hold the Source Citation.
Every Individual/Family Record level Citation is moved to a synthesised custom Event named Ω Whole Record Citation.
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.
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.
Any Publication Info (PUBL) or Text From Source (TEXT) or Source Type (_TYPE) fields are converted to a Record local Note with a Publication Info: or Text From Source: or Source Type: label respectively.
See Extra Options tab Update 1 CHAN:
The Updated CHANge date/time tags lines are removed entirely.
If the primary purpose of using Ancestry is to obtain Hints & Hits, then many of the above details are superfluous and may be removed to minimise the number of Note items under Other Sources.
All the (Std-) Brief Data Standard GEDCOM 5.5 rules apply except as defined below.
See Extra Options tab Custom Attribute 1 _ATTR:
Each custom _ATTRibute tag is converted to the EVEN tag with its value on the same line.
Each ASSOciated Person is converted to a custom Event using the EVEN tag with a Fact local Note with a Relationship: label.
See Extra Options tab Fact Address 2 ADDR:
All Address fields are appended to the Fact local Place field following the word at.
All other rules are as for (ANC+) Full Data Export Details above except that Source record _TYPE tag lines are remove entirely.
Sign in to Ancestry and use Family Trees > Upload a GEDCOM.
Then Browse to choose the fh Plugin Export folder and the Project…ANC UTF8.ged file.
Optionally, enter a Tree Name & Description, and untick Allow others to see my tree.
Tick I accept the Submission Agreement before clicking Upload.
Scroll down to the green We have finished processing… section and click the Go to… link.
Optionally, choose a different Home Person, then click Select.
Choose alternative trees via the Family Trees drop-list.
For particular tree options, use Tree pages > Tree Settings where you can Export tree or Delete your tree.
Return to Export Gedcom File ~ Output Formats.
Return to Export Gedcom File Plugin Introduction.
