When FTM 2017 was out, MacKiev removed the earlier export versions in FTM 2017.

The Family Tree Maker 2012 database that you have now, can be directly be imported into RootsMagic, using.

Select added options you wish to include with this export.

Under “Output format” select “Family Tree Maker 2012”.

Export to FTM 2014.1 and Open in that Version to Export Backward to FTM 2012 or 2014 or use a GEDCOMįollow the Steps Importing Mackiev FTM To RootsMagic Software.

You must use another process to direct import in RootsMagic 7

When FTM 2017 was out, MacKiev removed the earlier export versions in FTM 2017.

Follow the Steps Importing Mackiev FTM To RootsMagic Software.

The Importing to Family Historian advice has an entry for Knowledge Base > Defining Imported Custom Facts in which the Custom Facts from other Products explains how to reveal and create their definition. FH does not create a fact definition and just relies on default built-in settings. However, many products ignore that distinction, including RootsMagic, partly because in GEDCOM v5.5.1 that distinction has become blurred.Īny imported custom Events are unlikely to have a matching Tools > Fact Types definition. That is because in GEDCOM v5.5 Events such as Birth, Marriage, Death cannot have a value, whereas Attributes such as Occupation, Possession, Religion can have a value.

The EVEN Event Tag errors are complaining about values, that in some products are called details or references, being moved to the local Note field. I've lost track of how many times I've said it would help if explicit details are provided instead of vague 'a lot of errors' or 'a slightly different format than I expected'. See Knowledge Base > Import from RootsMagic (RM) with advice on Knowledge Base > Defining Imported Custom Facts. Also the fact type that I created new in FH6 imported nicely from the fact type I created in Rootsmagic so that appears to be a viable the route to follow. It appears to follow the path of using a generated fact type but I cannot locate where these generated fact types might be. When I import the GEDCOM file it retains all the data but in a slightly different format than I expected. Other sites have noticed that the documentation shows both methods. When I import from RM I get a lot of error because the EVEN tag does not conform to FH6 but does seem to conform to GEDCOM standards. I created a test project that has several people but one that uses all the new fact types that I created in Rootsmagic.

I created a single fact type in FH6 that exactly matches the fact type that I have in Rootsmagic. I deleted many fact types that I did not need a specialized fact type for. I have several fact types that I have created and want to keep. I have encountered the following situation, among others. I am getting ready to do a full import of my genealogical database from Rootsmagic 7.

Rootsmagic 7 gedcom import