Glossary
Document migration
Also called: content migration
Document migration is the movement of documents, their metadata and their version history from one system to another. The transfer is rarely the difficult part; deciding the destination taxonomy, mandatory fields and retention rules is where migrations succeed or fail.
Document migration explained
The work is upstream of the transfer
Moving files is a solved problem. What takes the time is agreeing the folder structure, deciding which metadata becomes mandatory, settling the retention triggers, and establishing what counts as a record worth moving at all. Organisations that treat migration as a technical exercise discover these decisions mid-project, when they are most expensive.
Migrate less than you think
Most repositories contain a large volume of material nobody has opened in years. Migration is the natural moment to apply retention rather than to move everything and defer the problem — a decision that is far easier before content arrives than afterwards.
Version history rarely survives intact
Source systems trim versions by policy, store them in proprietary formats, or expose only the current one through an API. Establish what actually exists before promising a full history in the destination, and record the limitation rather than discovering it during an audit.
Reconciliation before cutover
Count documents at source and destination, sample metadata values, and verify a set of known documents open correctly. Retain the reconciliation report as a record — it is the evidence that the migration was complete, and it is what you produce when someone claims a document is missing.
Run in parallel briefly
Leave the source read-only for a period rather than switching in one step. It costs a little and removes the pressure that causes bad decisions during cutover.
FAQ
Document migration: common questions
Should we clean up before or after migrating?
Clean the metadata model and value lists at source, where the tooling exists for it. Reshape the folder structure after, once you can see how people actually use the new system.
How long does a migration take?
The transfer scales with volume; the decisions do not. A single-department move with a clear scope is usually weeks, and what extends it is agreeing taxonomy and retention rather than moving bytes.
Related terms
- Check-in / check-outCheck-out locks a document for editing by one person and shows others who holds it; check-in releases the lock and creates a new version.
- Common data environmentA common data environment is the agreed single source of information for a project, through which all information is collected, managed and shared.
- Contract lifecycle managementContract lifecycle management covers the whole life of an agreement: request, drafting, negotiation, approval, signature, storage, obligation tracking and renewal.
- Document management systemA document management system is software that captures, stores, versions, secures and retrieves an organisation's documents from one repository.
- Document numberingDocument numbering assigns each document a unique identifier, generated by the system according to rules configured per document type.
- Document typeA document type classifies what a document is — a contract, a policy, an invoice, a batch record.
Última revisión: 28 de agosto de 2026. Browse the full glossary.