How do we handle it when scanned images and their index metadata get separated or mismatched during a system migration?

When scanned images and their index metadata drift apart during a migration, the underlying problem is almost always a broken link between two things that were stored separately: the image file (the content) and the index record (the data that describes and locates it). Restoring trust means re-establishing that link and proving it held.

Why separation happens

Mismatches typically arise when the source system stored images and metadata in different tables, folders, or repositories and the migration moved them on independent paths. Common triggers include changed file naming or pointer values, records re-ordered during extract, duplicate or missing identifiers, character-encoding shifts, and partial loads that complete the metadata side but not the image side (or vice versa).

Stop the bleeding first

If a live migration is producing mismatches, pause it. Continuing to load against a flawed mapping only multiplies the errors and makes root-cause analysis harder. Preserve the source system and a verified backup so you always have an authoritative point of reference to reconcile against.

How to reconcile

• Anchor on a stable identifier. Reconnect images to metadata using a persistent key (a unique document ID or checksum), not a positional guess like row order or sequence number.
• Verify with counts and hashes. Compare record counts and file checksums between source and target. A matching count plus matching hashes is strong evidence that content and description stayed paired.
• Sample and inspect. Pull a representative sample and confirm the displayed image actually matches its indexed fields. Statistical sampling catches systemic offsets a count alone will miss.
• Quarantine exceptions. Route unmatched images and orphaned metadata to a hold area for manual review rather than guessing at links.

Prevent the next time

• Map fields and identifiers explicitly before any data moves, and test the mapping on a small pilot batch.
• Migrate content and metadata as linked units, validating the pairing at each step.
• Keep a migration log and reconciliation report as evidence the transfer preserved integrity, accuracy, and usability — qualities that determine whether a digitized record remains trustworthy and admissible.

Treat verification as part of the migration, not an afterthought. For broader guidance, see the digitization and imaging hub.