Chris, I did this very conversion a couple months back. I ran into everyone getting "Natural" parent-child relationships, rather than blank. Reported it, and that has been fixed, so you should have blank parent-child relationships where none is sent from FTM. There are two: father-child and mother-child, as well as a child status. You might want to see how yours imported.
I also ran into my "Source location" values NOT getting put into Legacy's Repository field. I believe Sherry determined it is the fault of the FTM GEDCOM file. It puts it into a NOTE tag, instead of the REPO tag. The result in Legacy was a lot of "Not Given" repository names. Each one had its own list of 'attached' individuals, but it was not very helpful as you couldn't tell which source. Actually, you COULD tell, if you waded through the GEDCOM file matching IDs. Since I had not been meticulous in FTM with repositories, I just deleted mine. (I'm also cleaning up sources, so can get the repositories right at the same time. (Source issues are due to user error, not the import.) I can't remember any other major items. Of course, there may just be something lurking out there. As it was, I found the "Natural" thing too long after having made other data modifications to go back and reimport after the program change was made. Still plodding through those changes as the mood strikes me... Another thing I've heard suggested on this list is to do your imports in chunks. That is, do a few thousand, one line or something, rather than the whole 35,000 (I can't even imagine that). Run all the reports and test the options to seek out any problems with how your data was imported. Best wishes for a successful conversion. --Paula Texas Currently researching: Goodale in Mass., NY, Mich. ----- Original Message ----- From: "Chris Schultheis" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, August 28, 2004 2:26 PM Subject: [LegacyUG] FTM ver 10 to Legacy 5 > I have been using the free version of Legacy 5. I have imported a gedcom > from FTM ver 10 of 35,000 invididuals to experiment and play with. The task > of converting all of the non-standard info from FTM into Legacy seems very > daunting. Some of the things I have found that did not import correctly are > some of the non-standard facts that I created in FTM. Of particular concern > are duplicate entries for "facts" in FTM that had multiple sources. For > example: What was one occupation (farmer) with several different sources > in FTM is now numerous occupations of farmer with each having an individual > source in Legacy. > > I have read and reread previous suggestions on importing. Does anyone have > any advice before I make the big plunge of the master import? Otherwise I > see many, many hours, days, weeks, months and maybe years of updating data. > > Chris..... > > > Legacy User Group Etiquette guidelines can be found at: > http://www.LegacyFamilyTree.com/Etiquette.asp > > To find past messages, please go to our searchable archives at: > http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ > > To unsubscribe please visit: > http://www.legacyfamilytree.com/LegacyLists.asp > Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
