{"id":10475,"date":"2020-06-30T13:17:09","date_gmt":"2020-06-30T13:17:09","guid":{"rendered":"https:\/\/fhug.org.uk\/kb\/?post_type=kb_article&p=10475"},"modified":"2024-04-07T08:22:41","modified_gmt":"2024-04-07T08:22:41","slug":"importing-to-family-historian","status":"publish","type":"kb_article","link":"https:\/\/www.fhug.org.uk\/kb\/kb-article\/importing-to-family-historian\/","title":{"rendered":"Importing to Family Historian"},"content":{"rendered":"

Introduction<\/h2>\n

When importing data from other family history applications, more complete and reliable import is usually achieved by reading the source file directly, rather than relying on GEDCOM.<\/p>\n

Prior to version 7, \u0192h<\/span><\/span> had only limited ability to import directly from other products. Calico Pie now provide detailed information<\/a> on the \u0192h<\/span><\/span> website about which files can be read directly by the latest version of the product.<\/p>\n

Version 7.0.8 of \u0192h<\/span><\/span>, released in September 2021, provided a major enhancement of import capabilities, with RootsMagic and Legacy files now being read directly. This is available as a free upgrade for all registered users of \u0192h<\/span><\/span>7, by following this link<\/a> to the \u0192h<\/span><\/span> download site.<\/p>\n

Where direct import is not available, GEDCOM provides a universal fallback option. Different implementations by different suppliers means that some tweaking of the import process is usually required.\u00a0 Version 6.2 of \u0192h<\/span><\/span> provided a major upgrade of its GEDCOM import, so users of \u0192h<\/span><\/span>6 wishing to import a new database should ensure that they have applied the free upgrade to version 6.2<\/a>.<\/p>\n

GEDCOM export is usually available in the originating application as either a Save As.. or Export.. option in the File menu.\u00a0 If you have the option of GEDCOM formats, select 5.5 for import into \u0192h<\/span><\/span>6 and 5.5.1 for import into \u0192h<\/span><\/span>7.<\/p>\n

General Import Process<\/h2>\n

Getting Started<\/h3>\n

The best way to import a GEDCOM file, and the only way to do a direct import, is to start of by selecting File > Project Window…<\/a> from the main \u0192h<\/span><\/span> menu.\u00a0 Click on the <New Project> button, and select either “Import a GEDCOM file” or “Import from another family tree file”.\u00a0 Enter or browse for the file name, and \u0192h<\/span><\/span> will present a conventional Open File dialogue window to select the relevant file.<\/p>\n

The menu recommends selecting “Copy any linked multimedia files into the new project folder”.\u00a0 This is certainly the easiest option for beginners, but if you are used to managing media files separately from your main database (e.g. in RootsMagic, where media must be kept separately), and have an existing backup procedure to safeguard your media, you may find it easier and more familiar not to select this option.<\/p>\n

Common GEDCOM errors, such as incorrect handling of word-wrapping, are checked during import, and you will be presented with a menu to select the most appropriate option from an analysis of your source file.<\/p>\n

Reviewing Reported Log Files<\/h3>\n

When importing a file, particularly a GEDCOM file, \u0192h<\/span><\/span> will check for errors and produce reports of data it does not understand such as Uncategorised Data Fields, or comment on actions it has taken to covert data.\u00a0 These reports are saved automatically for review via the Window > Log Files…<\/a> command.<\/p>\n

Work through the error reports to check for any erroneous tags. These are normally caused by the program the GEDCOM file came from.\u00a0 It may be possible to identify the errors and correct them either directly in \u0192h<\/span><\/span> or in the source program.\u00a0 Using a text editor such as Windows Notepad to search and replace tags in the GEDCOM file directly may be possible, but seek expert guidance on the Forum unless you are confident that you know exactly what you are doing.\u00a0 It will be very easy to corrupt your GEDCOM file, and this can crash \u0192h<\/span><\/span> completely, causing potential data loss.<\/p>\n

Custom Facts<\/h3>\n

Custom facts (both events and attributes) can be transferred between applications using GEDCOM, but \u0192h<\/span><\/span> cannot assign custom facts that it does not recognise to specific Fact Sets. It is recommended that you either create a definition for each custom fact after import, or convert undefined custom facts to standard \u0192h<\/span><\/span> facts.\u00a0 This makes it easier to manage the facts within the imported project, and also makes the facts portable, so they can be used in other \u0192h<\/span><\/span> projects.<\/p>\n

To view undefined custom facts, select Tools > Fact Types…<\/a> from the main \u0192h<\/span><\/span> menu.\u00a0 Select the \u201cShow Hidden\u201d option, where they are displayed with a Fact Set of <none>.<\/p>\n

From here, you can create a \u0192h<\/span><\/span> definition for the custom fact and assign it to an individual Fact Set (usually Custom) by selecting the fact and clicking on <Edit>.\u00a0 Alternatively, if there is a standard \u0192h<\/span><\/span> that could be used instead, you can convert all examples of that fact using the Change Any Fact Tag<\/a> plugin.\u00a0 An exception to this general advice is the direct RootsMagic import, which creates its own project-specific fact set.\u00a0 More details on how to process this are provided in the Importing From RootsMagic<\/a>\u00a0guidance.<\/p>\n

Other Conversions<\/h3>\n

There are a number of issues that are often faced by users converting data from other products.\u00a0 Many of these have been addressed with custom plugins, and relevant links are collected together in the\u00a0Knowledge Base Importing Contents Page<\/a>.<\/p>\n

The following sections provide more detailed guidance on most of the popular family history applications, and are a mixture of direct import and GEDCOM transfer.<\/p>\n

Import from Family Tree Maker (FTM)<\/h2><\/summary>

Introduction<\/h3>\n

Different versions of Family Tree Maker (FTM) have different database formats. Use the export to GEDCOM option, and from FTM 2012 image data is also exported, but prior to FTM 2012 scrapbook images are not exported. Note that any “source” images from Ancestry are not exported, so ensure all such images are saved to your PC while your Ancestry subscription is active. The FTM 2017 version by MacKiev is more GEDCOM compliant than previous versions, so follow any specific advice below for this version.<\/p>\n

Export GEDCOM from Family Tree Maker<\/h3>\n

File Export Dialogue<\/h4>\n
    \n
  1. \"\"In FTM open the file you wish to export to GEDCOM.<\/li>\n
  2. Choose File > Export to open the Export dialogue.<\/li>\n
  3. In the Output Format dropdown list select GEDCOM 5.5.<\/li>\n
  4. Select items to include such as private facts, private notes, or media files.<\/li>\n
  5. Press OK.<\/li>\n<\/ol>\n

    Versions prior to FTM 2012\/2014 may have other options, so ensure Indent records is NOT ticked, and that Abbreviate tags is ticked.<\/p>\n

    Export to GEDCOM Dialogue<\/h4>\n
      \n
    1. \"\"The Export to GEDCOM dialogue should now be open.<\/li>\n
    2. Select Destination as Other.<\/li>\n
    3. Select Character set as ANSI.<\/li>\n
    4. Press OK.<\/li>\n
    5. Decide on a location to store your GEDCOM file so that you can easily retrieve it later. A reasonable place to store your file might be your Desktop or My Documents. You can access these by clicking on the box next to Save in and scrolling all the way to the top. You will find both the Desktop and My Documents in that list.<\/li>\n
    6. Next to where it says File name type a file name such as MyData.ged.<\/li>\n
    7. Press Save.<\/li>\n<\/ol>\n

      Export Status Dialogue<\/h4>\n
        \n
      1. The Export Status window should indicate the file exported successfully.<\/li>\n
      2. Press OK.<\/li>\n
      3. Your file has now been exported and is ready to be used to create a Project or opened directly in \u0192h<\/span><\/span>.<\/li>\n<\/ol>\n

        See Understanding Projects<\/a> for more information on creating Projects from GEDCOM files using the File > Project Window<\/a>.<\/p>\n

        Import GEDCOM into Family Historian<\/h3>\n

        This is generally straight forward in \u0192h<\/span><\/span> versions 6.2 and 7.\u00a0 However, a number of issues arose in previous versions of \u0192h<\/span><\/span>.\u00a0 These notes have been retained for reference, but are now largely obsolete.<\/p>\n

        Media Images<\/strong><\/p>\n

        For \u0192h<\/span><\/span> V6.0 or earlier, any Media attached to Citations may appear to vanish, but they are just being coy. They can be discovered on the All tab of the Individual’s Property Box, but can also be revealed by using the toolbar camera icon View Media for selected Individual, and choose just the Source and Citation Media option. If you cannot find them ask for help in the Forums.<\/p>\n

        If you are using \u0192h<\/span><\/span> V5.0.8 or earlier, and need to migrate your Media files, then the GEDCOM file must be changed using a plain text editor such as Windows Notepad to replace every occurrence of 1 FILE with 1 _FILE , whereas later \u0192h<\/span><\/span> versions do not require this edit.<\/p>\n

        General Advice<\/strong><\/p>\n

        In \u0192h<\/span><\/span> V6.2 many of the problems below have been resolved without the need for Quick Fix Plugins<\/a>. A special Fact Set named Extended Set has been added to support the extended FTM facts.<\/p>\n

        Prior to FTM 2017, the Cause of Death was appended to the DEAT event tag, and when imported to \u0192h<\/span><\/span> automatically moved to the Death event local Note, but any existing Note hidden, except on the All tab. Thereafter, the Note can be manually moved to the Death event Cause field, and deleted. A similar problem may affect other facts with an FTM Description. Alternatively, use the Quick Fix Plugins method below.<\/p>\n

        If a Source Citation has both an Entry Date and Text From Source then an extra 3 DATA tag is produced. \u0192h<\/span><\/span> may convert these to 3 _DATA Uncategorised Data Fields. To correct the problem, use a plain text editor such as Windows Notepad on the exported GEDCOM file to find and delete the redundant 3 DATA tag lines, or use the Quick Fix Plugins below.<\/p>\n

        Source and Repository record 1 RFN tags are treated as Uncategorised Data Fields and fixed by Quick Fix Plugins<\/a> below.<\/p>\n

        Some fact tags might be treated as Uncategorised Data Fields and may include:<\/p>\n