Asking if other have this problem (I submitted ticket to Legacy):
When importing a Gedcom file generated by Ancestry.com into Legacy 220.127.116.11, alternative events (such birth and death) seem to be combined with regular events into a single event. Here is what is happening as far as I can tell:
• Legacy keeps a single birth event. I am not sure how it determines which of the regular or alternate events to keep, but it does keep one. Legacy seems to keep the event with the latest date, but I am not sure. Legacy does not seem to distinguish between regular and alternate events when deciding which one to keep.
• The places and dates for the other alternative or regular events which are not kept are lost.
• The Ancestry.com descriptions for the alternative birth events are all appended to the notes of the single event which Legacy keeps.
• The Ancestry.com sources for the alternative birth events are all assigned to the single event Legacy keeps.
I know that Ancestry.com is writing all the events to the Gedcom file because when I import the same Ancestry generated Gedcom file into RootsMagic, Roots Magic will create regular birth events for each alternate event. That is, RootsMagic creates multiple regular (not alternate) birth events from both the regular and the alternate events.
If I then create a gedcom file from the resulting RootsMagic file, Legacy will import all the birth events as “Alt. Birth” events with the same associated date, place, description, and sources which were in the original file. Except, Legacy will select one of the “Alt. Birth” events (I think it is the earliest one) and assign it as the regular event keeping its associated date, place, and sources, but moving its description to the notes for the regular event.
This did not use to be the case. I have looked back through my backup files. In May 2017, using a previous version of Legacy, when importing gedcom from Ancestry, Legacy did import the alternative birth events as separate “Alt. Birth” events with associated date, place, and sources. I need to get that functionality back.