With that in mind, can there be a specific link to the Importing topic, so that the Compendium of Conversion Plugins, Handling Uncategorised Data Fields, and related advice is easier for newcomers to find?
The Import from Legacy Family Tree (LFT) accordion, 'On the Options tab:' bullet list needs an extra final 5th bullet point:Introduction
Importing a GEDCOM into Family Historian (ƒh) may be as simple as opening the GEDCOM file in ƒh, but it is advisable to create a Project by using the File > Project Window… command and New Project… button.
Each of the sections below gives advice for importing from various other genealogy products. A few allow direct import from other product database files avoiding GEDCOM altogether.
• The first time you open a GEDCOM file, ƒh will check for errors and produce reports of data it does not understand such as Uncategorised Data Fields. Save any report files to a new name using the File/Save As option.
When a Project is created, similar reports are produced and automatically saved for review via the Window > Log Files… command.
• Work through the error reports to check for any erroneous tags. These are normally caused by the program the GEDCOM file came from. However, you may be able to identify the errors and correct them either directly in ƒh or in the other program or by using a text editor to do a search and replace for the tags in the GEDCOM file but that is only advisable for experts. There is a compendium of plugins designed to correct many of the common errors that have been experienced by users migrating from other products.
• Custom Facts imported from another product will have no Fact definitions, so are not listed by default in the Tools > Fact Types… command dialogue. To reveal them, tick the Show Hidden option, and click the Visible column heading to sort the <undefined> Custom Facts to the bottom. Select each one in turn and click the Edit… button to create a definition. Alternatively, the Change Any Fact Tag plugin can convert Custom Facts to Standard Facts where appropriate.
• Do NOT tick the Export Shared Events as regular Events option so that Shared Events are migrated as Fact Witnesses