Migration vs emulation for preserving digital records: which one keeps a file readable long-term?
Both migration and emulation are recognized strategies for keeping digital records usable over time, but they solve the problem in opposite ways. Neither is a one-time fix, and many programs use them together. The deeper challenge is the same in both cases: file formats, software, and hardware all become obsolete faster than records need to be retained.
What migration does
Migration moves the content of a record from an aging or obsolete file format into a current, well-supported one. A document in a proprietary word-processing format might be migrated to PDF/A; a spreadsheet might be re-saved in an open, widely readable format.
Migration keeps the file itself readable because you are continually refreshing it into formats that today’s software can open. The trade-offs:
- Each migration risks small losses of formatting, structure, or embedded features.
- It must be repeated over the years as formats age again.
- It works best for stable, well-documented formats and simpler record types.
What emulation does
Emulation leaves the original file untouched and instead recreates the old computing environment — the operating system or application — on modern hardware, so the record opens exactly as it originally did.
Emulation preserves the authentic look, behavior, and interactivity of complex records (databases, multimedia, software-dependent files) that migration may flatten. The trade-offs:
- It requires maintaining or rebuilding old software environments, which can be technically demanding.
- Licensing and dependency issues can complicate long-term use.
Which one keeps a file readable long-term
If the goal is simply keeping the file openable with mainstream tools, migration is the more direct answer, because it continually moves content into current formats. Emulation keeps the original bitstream readable in its native environment, which matters most when exact rendering and behavior are essential to the record’s value.
In practice, sound preservation programs combine both: normalize to open, durable formats where possible, retain originals, document everything, and revisit the plan on a regular cycle. Choosing well depends on the record’s retention period, complexity, and how much of the original experience must survive.
For broader context on managing records across their lifecycle, see the federal records hub.
Sources & further reading
Authoritative government and non-profit references.
- Digital preservation (Library of Congress) — Library of Congress
- Records management (NARA) — National Archives (NARA)
How to cite this page
APA
RM University Editorial. (2026). Migration vs emulation for preserving digital records: which one keeps a file readable long-term?. Records Management University. https://www.recordsmgmt.org/questions/migration-vs-emulation-for-digital-preservation/
MLA
RM University Editorial. "Migration vs emulation for preserving digital records: which one keeps a file readable long-term?." Records Management University, 16 June 2026, www.recordsmgmt.org/questions/migration-vs-emulation-for-digital-preservation/.
Related questions
- Are records created by federal contractors considered federal records?
- Big-bucket vs item-level retention schedules: how do I decide which approach to use?
- Can a federal employee be personally fined or jailed for deleting government records?
- Can federal employees conduct official business on personal devices or apps?
- Can I delete old federal records to free up storage space when our shared drive gets full?