Importing research from another genealogy platform often leaves unexpected gaps in your timelines. Resolving Family Tree Maker missing RootsMagic or GEDCOM import facts ensures all custom tags, census dates, and event descriptions transfer accurately into your tree.
Causes of Dropped Facts During Import
GEDCOM standards vary between software programs. Missing details usually result from tag mismatches rather than lost data:
- Non-Standard GEDCOM Tags: Custom events created in RootsMagic (such as custom military rolls or burial details) often export with application-specific labels that FTM does not map automatically.
- Unsupported Fact Definitions: FTM’s default fact dictionary rejects undefined attributes, converting them into unlinked notes or ignoring them entirely.
- Version Tag Divergence: Older GEDCOM specifications (e.g., 5.5 vs. 5.5.1) handle geographic coordinates and source citations with different record syntax.
Direct Fixes to Recover Missing Import Data
1. Re-Map Custom Fact Tags During Import
Do not use the automated default import wizard without checking the mapping table:
- Go to File > Open and select your .ged or RootsMagic export file.
- When the import dialog opens, click Advanced Options or check the Review Fact Mapping box before finalizing the tree creation.
- Scroll through the unmapped tags column. If a field shows as Unknown or Drop, click the dropdown and reassign it to an existing standard FTM category (such as Custom Event, Description, or Fact).
2. Inspect the Undefined Facts Report
If the tree is already imported:
- Switch to the Publish workspace.
- Select Person Reports from the left panel and double-click Undocumented/Undefined Facts.
- Run the report to generate an index of every imported line item that failed to attach to a profile. This shows exactly which ancestors lost data and lists the raw text for manual reassignment.
3. Add Custom Fact Definitions
If specific fields (like “Census 1851” or “Medical Condition”) vanished across hundreds of ancestors:
- Navigate to Tools > Manage Fact Types.
- Click New and create a fact label that matches the exact tag name used in your source program.
- Re-import the original file into a new temporary tree. FTM will now recognize the custom tag and populate the field across all profiles.




