Appearance
Migration and emulation are the two main strategies for keeping digital content usable as technology changes. Migration converts a file into a newer, well-supported format and keeps the content, accepting that some properties may shift. Emulation leaves the original file untouched and instead recreates the old software or hardware environment so the file opens exactly as it once did. For most documents and images, beginners should start with migration; emulation earns its keep for software, games and interactive works where exact behaviour is the point.
What does migration mean in plain language?
Migration is "save as a newer format." A WordPerfect document from 1995 becomes a PDF/A; a proprietary camera RAW becomes a TIFF; a Lotus 1-2-3 spreadsheet becomes CSV. The original is superseded (though you should keep it). The appeal is simplicity: the tools are mature, the new format is easy to open today, and you can verify the result by eye. The catch is loss — a conversion may drop formatting, embedded macros, precision, or interactivity. That is why you decide in advance which properties must survive.
What does emulation mean in plain language?
Emulation is "rebuild the old machine." Instead of changing the file, you run software that imitates the original operating system and hardware — DOSBox for old DOS programs, QEMU for whole machines, or a browser-based emulator. The 1995 document opens in a virtual copy of WordPerfect, looking exactly as it did then. Nothing is lost from the file. The cost moves elsewhere: you now have to preserve the emulator, the OS image, and any fonts or drivers, and there are licensing questions around old software.
How do I choose between them?
| Consideration | Lean migration | Lean emulation |
|---|---|---|
| Object type | Documents, images, tabular data | Software, games, interactive media |
| Tooling maturity | Very mature, easy to verify | More specialist setup |
| Loss tolerance | Some property loss acceptable | Exact behaviour required |
| Ongoing effort | Re-migrate as formats age | Maintain the environment |
| Access for users | Opens in everyday software | Needs the emulator running |
If you can express what matters as content in a modern format, migrate. If the experience or behaviour is the artefact, emulate.
A small worked example
You receive a folder of 1990s .wpd WordPerfect files. The text and basic layout are what your readers need.
bash
# Migration path: convert to PDF/A with LibreOffice in headless mode
libreoffice --headless --convert-to pdf:writer_pdf_Export \
--outdir ./pdfa ./*.wpd
# Keep the originals; verify the PDFs render the text correctlyThat is migration done. Now suppose one file is an interactive 1990s teaching program, not a document — migration cannot capture its buttons and branching. There you keep the original and provide an emulation path (e.g. a preserved DOS environment in DOSBox). Same accession, two strategies, chosen by object type.
Can I just do both?
Yes, and mature programmes usually do. A common hybrid: migrate everyday content to open formats for convenient access, and retain the bit-perfect originals so an emulation route stays open if exact behaviour is ever needed. This hedges your bets — you get easy access now without throwing away the option of authentic rendering later. The originals plus good documentation are what make the hybrid possible.
What should a beginner do first?
Pick a low-risk migration: old word-processor files to PDF/A or plain text, or proprietary images to TIFF. Define the must-keep properties first, convert a sample, and verify it. You will learn the verification habit that underpins all preservation. Save emulation for later, when you hit an object — a piece of software, a game, a multimedia CD-ROM — that simply cannot be flattened into a document.
Key Takeaways
- Migration converts the file to a new format; emulation recreates the old environment around the original.
- Beginners should start with migration for documents and images; it is mature and verifiable.
- Every migration can lose properties — define what must survive and check it did.
- Emulation preserves exact behaviour but shifts effort to maintaining emulators and OS images.
- Choose by object type: content-led objects migrate, behaviour-led objects emulate.
- Hybrid approaches keep originals plus a modern access copy, preserving both options.
- A first project: convert old word-processor files to PDF/A and verify the text survived.
Frequently Asked Questions
What is the difference between emulation and migration?
Migration converts a file to a newer, better-supported format while keeping its essential content; emulation keeps the original file unchanged and recreates the old software or hardware environment needed to open it.
Which is better for a beginner to start with?
Migration is usually the simpler starting point for documents and images because the tools are mature and the results are easy to verify; emulation suits complex software, games and interactive works.
Does migration risk losing information?
Yes, every format conversion can lose significant properties such as formatting, embedded behaviour or precision, so you should define what matters and verify it survived the conversion.
Is emulation hard to maintain over time?
Emulation shifts the burden from the file to the environment; you must preserve the emulator, the operating system, and any dependencies, which is more complex but avoids repeated content conversion.
Can I use both emulation and migration together?
Yes, a hybrid approach is common: migrate simple content to open formats for everyday access, and keep the originals plus an emulation path for objects where exact behaviour matters.
What is a good first migration project?
Converting old word-processor documents to PDF/A or plain text, or proprietary images to TIFF, is a low-risk first project with mature, verifiable tooling.