My reason for having my family tree in Legacy AND Family Tree Maker (FTM) AND ancestry.com: 1. I first received family data from my cousin who was using FTM before I knew anything about genealogy software (Feb/ 2000). 2. After using FTM for several years, I learned about Legacy (in 2008) and found I liked it better. By then, our family tree had been uploaded to myfamily.com which later interfaced with ancestry.com. So the only way I could keep our tree public (by the time myfamily.com went away, my cousin had died and I had become the 'keeper' of our tree) I had to move it to ancestry.com, where I was already a member. Later, when FTM added the sync feature, I upgraded FTM and synced the tree. All along, I kept a master (a combined tree of my husband and myself) in Legacy and continued to buy upgrades and kept current with updates. 3. Problems with ancestry.com, i.e. the inability to clean-up place names; lost data when their host crashs, duplications with sync feature, etc. lead me to keeping 2 trees: 1) a master with Legacy, and 2) ancestry.com synced with FTM. 4. When I first started using FamilySearch sources/documentation I found it contained a lot of mistakes (typos) and limited actual images of documentation where ancestry.com most often had the jpg; and up until mid 2000's neither hand much from Southern United States, which was my area of origin. For the past 5 years I have my master tree in Legacy 8 Deluxe, latest update. I have a duplicate on ancestry.com that is synced with FTM. I do most my research in ancestry.com, also using FamilyResearch. I only makes changes in ancestry.com (never in FTM). From time to time when I want to create a chart, I will run the sync feature so I have the latest data in my FTM 2011 tree. (I do not plan to upgrade FTM) FTM and Legacy have different type charts and grafts that have their own uniqueness. I also have Charting Companion by Progeny Genealogy for both Legacy and FTM, (mostly for the descendant pie chart). Yes, all this is a pain sometimes, but, for the way I use the programs, I found this works for me. Fortunately, I do have a lot of time to spend working on my trees. If that changes, I am sure I will need to make a change, but until them, this set up works for me. Hope this is of value and welcome questions and comments and suggestions to improve. Elizabeth Verchio
On 1/2/2015 3:03 PM, Roy G. Jackson wrote: > I am new to the list. I've had Legacy for a loonnnng time, but have > been inactive for a number of years. Am I understanding from all this > discussion that Legacy does not sync with Ancestry.com? I must be > missing something. Why would I use Legacy, but transfer everything to > FTM? Sorry if this has been discussed before. > > Roy > > On 01/02/2015 11:35 AM, David Abernathy wrote: >> >> 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 > > -- > Roy G. Jackson > Naples, Florida USA > > > 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
