FamilySearch import issues: incorrect marriage assignment, duplicate processing, and failure to expand existing imports (RM10/11)

RootsMagic
, , ,
1

I’m experiencing multiple issues importing from FamilySearch into RootsMagic which appear to be related and started approximately one month ago.

These issues occur regardless of import options/settings and did not happen previously.

1. Incorrect marriage assignment

For individuals with multiple spouses:

  • The latest marriage date is being applied to earlier spouses

  • Marriage facts are not staying attached to the correct couple

This occurs consistently, even on small imports, and results in incorrect data immediately after import.

2. Same individual processed multiple times during import

During import:

  • The same person’s name appears multiple times (flashing more than once)

  • This behaviour did not occur previously

Important:

  • No duplicate individuals appear in the final database

  • However, this repeated processing seems to coincide with incorrect relationship mapping

3. Cannot expand an existing import

If I:

  • import ~3 generations → completes

  • then try to increase to ~6 generations or add more descendants

:backhand_index_pointing_right: The import reports complete but shows 0 people added, so no additional data is brought in.

This used to work — I was previously able to expand an existing import without issue.

Also, even when the smaller import completes, the marriage assignments are still incorrect.

4. Additional notes

  • Occurs in both RM10 and RM11

  • Happens with both ancestor and descendant imports

  • Data appears correct on the FamilySearch side

  • Importing from the standard FamilySearch Family Tree (not Family Group Trees)

5. Workflow impact

This is currently blocking my workflow:

  • I work primarily in FamilySearch

  • Import into RootsMagic → export GEDCOM → import into Ancestry

  • Identify new ancestors/descendants/facts → update FamilySearch

  • Repeat periodically

This has been an efficient way to build out a large, previously incomplete tree, but the current import issues make the process unreliable.

For context, I’m working at scale (FamilySearch reports ~3.8k contributions in 2025, ~970 people added, ~2.8k sources since July), so manual correction is not feasible.

Question

At the moment, I’m seeing incorrect relationship data regardless of import options.

  • Is this a known issue or recent regression in the FamilySearch integration?

  • Has anything changed recently that could explain this behaviour?

  • Is there currently any reliable workaround, or is this a known limitation/bug?

1 Like
2

We haven’t made any changes to FamilySearch in quite a while.

I’ve seen over the years it giving the wrong marriage dates when there are multiple spouses. The import also freezes if people are already in the database. If the import is in a blank database and giving 0 people then open a support ticket so we can test it.

https://support.rootsmagic.com/hc/en-us/requests/new