I suggest you click the View Report button, which will open the list in Notepad, and save the list for future reference. A list of issues is opened this is the log that I was expecting.Once the GEDCOM is imported, a summary is presented click the View Issues button (Fig 2). The actual log file is created in a later step. The option to “Write import execution log file” merely creates a copy of the GEDCOM file rather than the log file I expected.Leaving the encoding set to Auto-detect is probably a good idea, since a file might be marked one thing but actually encoded another, and applications can often detect the actual encoding.

After beginning the GEDCOM import, make sure “Convert to Notes” is selected for “Handling of Unrecognized Tags” (Fig 1).

Importing a GEDCOM file into FTB is straightforward, but MyHeritage has a web page, “FTM Users: Join MyHeritage and get Family Tree Builder with an Unlimited Size Family Site for Free.” However, here are a few tips I’d like to highlight: Fig 1 Configure GEDCOM Import References to the GEDCOM standard are to version 5.5.1 unless stated otherwise. Portions of text in all capital letters that are not acronyms are GEDCOM tags, with the rest of the plain text field name in lowercase. Version tested: Family Tree Builder 7.2 (build 7155) for Mac using the CrossOver bridge provided by MyHeritage (note: FTM 8 is still not available for Mac 2 years after its release) Price: Free (basic edition), $6.88 – $14.65 per month (Premium MyHeritage account), Free mobile apps Mobile Apps: iPad/iPhone/Android (MyHeritage for mobile) Supported OS: Windows, Mac (bundled with CrossOver)

My family heritage tree builder