When making all of these NEW Ancestry trees, PLEASE delete the old ones. There are way too many junk trees on the internet because people do not remove their old trees when uploading new ones.
Thanks, David C Abernathy Email disclaimers ---------------------------------------------------------------------------- This message represents the official view of the voices in my head. ---------------------------------------------------------------------------- http://www.SchmeckAbernathy.com == All outgoing and incoming mail is scanned by F-Prot Antivirus == From: Crauswell_Verchio [mailto:[email protected]] Sent: Thursday, January 01, 2015 6:45 PM To: [email protected] Subject: Re: [LegacyUG] Updating from Legacy to FTM for Ancestry Methodology Question Been there - got the T-shirt! :-} After several attempts and ending with pretty much the same results as you. My main tree is in Legacy 8.0 Deluxe, (42,339 individuals) I determined that when dealing with Ancestry.com and FTM sync: Legacy export to Gedcom Create new ancestry.com tree with that Gedcom. FTM create a NEW tree by downloading the ancestry.com tree just created. Make chances/addition/deletions, etc. in ancestry.com ONLY. Periodically run sync process. Never change data in FTM. When ready to create reports, run sync process to have newest date in FTM; create charts, reports etc. If you find mistakes, data that needs changes, etc. make the changes in ancestry.com ONLY. This is the only way I have found to keep the duplicates to a minimum. I don't know about the DNA links. Place names cannot be 'cleaned up' in Ancestry.com. If you fix them in FTM then run a sync, you will get duplicate Events with the 'new' Place name. Other users of these 3 programs (Legacy, ancestry.com and FTM) may have a better methods, if so, I too would be most grateful to hear. Hope something I have offered helps. Elizabeth Verchio ancestry.com: crauswell_verchio. UnionMBCCemetery, Shiloh Methodist Church Cemetery - public trees On 1/1/2015 11:25 AM, Jessica Morgan wrote: ALL of my work is in Legacy, I've been using it since 2007ish, and many versions ago. But I want a decent tree on Ancestry.com without having to keep two trees. My methodology was: Keep tree in Legacy Export Gedcom for Ancestry Import Gedcom to FTM Sync with Ancestry The very first time it worked like a charm, because there was no data in FTM. The second time however, there were 1050 people in my tree. When I did the merge, it managed to duplicate 200, as my end count was 1250. It was a nightmare to manage and fix. So my question is this... if any of you transfer to FTM for Sync to Ancestry, what's your methodology? I thought of creating a tag of some sort to determine who HAS been uploaded, and then only exporting those whom I've added since the last sync, but I don't know how to add that to both databases without redoing the entire thing. The last time I did this, a few days ago, I did resort to deleting all but my anchor person from the FTM database and then importing everyone new again, merging him with himself. That works, but I have about ten people linked to the file on the DNA side, and I have to redo those every time. Any help and insight is appreciated. Jessica Morgan Sr Engineering Technologist, Black Stone Minerals Chair, SPE GCS Petro-Tech Study Group ****************************************************************** GedMatch kits: A064089 (SMK), A276959 (JRK), A608610 (TJ), A798429 (Jo), A817318 (JRKM), M399320 (JKM), M918651 (MM), several phasing kits as well FTDNA kits: B12555 (SMK), B12524 (JMM), B13031 (JKM), 368036 (CJ) Ancestry.com: jrkmorgan - all trees private Hometown Cotton Valley, Louisiana. Ratcliff/Lockey and Allen/Morgan decent. Researching Allen, Bandy, Basinger, Bethune, Beshea, Cruthirds, Kaylor, Lockey, Morgan, McGarity, Ratcliff, Striplin, Teague, Umphries, Urquhart, Wilkins - Current generations Louisiana, Arkansas areas; Migratory from Alabama, North Carolina Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
