Data Migration

What Is Data Migration?

Data migration is the transfer of data from one system, format, or storage environment to another. It’s the broad category that covers moving data into a new application during a platform switch, moving it to the cloud during infrastructure modernization, or moving it into a compliant archive during application decommissioning – the destination differs by project, but the underlying discipline of extraction, mapping, transformation, and validation is largely the same.

What distinguishes a migration destined for an active replacement application from one destined for an archive is the ongoing relationship with the data afterward. Migrating into a new live application means the data will keep being updated, used in transactions, and integrated with other systems going forward. Migrating into an archive means the data becomes read-only and static – its job from that point on is to remain accurate, complete, and retrievable for as long as retention rules require, not to support ongoing operations.

That distinction changes what “success” looks like for the project. A live-application migration is validated primarily against whether users can pick up their work in the new system without disruption. An archival migration is validated primarily against completeness, accuracy, and long-term retrievability – there’s no user picking up daily work in an archive, but there is an auditor, a lawyer, or a records manager who will eventually need to retrieve something specific from it, sometimes years later.

Key Points

• A broad category with two different destinations. Migration can mean moving data into a new live application or into a static, read-only archive – the goals and validation criteria differ significantly between the two.
• Shares a common technical discipline across use cases. Extraction, mapping, transformation, and validation are the same core steps whether the target is a new ERP, a cloud environment, or a compliance archive.
• Archival migration prioritizes retrievability over usability. Data migrated into an archive doesn’t need to support daily transactions – it needs to remain complete, accurate, and findable for as long as retention obligations require.
• The riskiest part of most decommissioning projects. More decommissioning projects fail or get delayed due to migration issues – incomplete extraction, bad mapping, failed validation – than due to the actual infrastructure shutdown step.
• Requires validation regardless of destination. Whether migrating to a live system or an archive, confirming the data landed correctly before the source is retired is a non-negotiable step, not an optional nice-to-have.

Common Use Cases

🔄 Application-to-application migration

Active data is migrated from a legacy CRM or ERP into its replacement platform, with users continuing their work in the new system immediately after cutover.

🗄️ Legacy-to-archive migration during decommissioning

Historical data from a system being retired outright, with no replacement application, is migrated into a compliant, read-only archive rather than a new live system – its only future use is retrieval for audit, legal, or reference purposes.

☁️ Cross-environment migration during cloud adoption

Data is migrated from on-premise storage into a cloud environment as part of a broader infrastructure move, using the same extraction and validation discipline as an application migration even though no application logic is changing.

Data Migration vs. Related Concepts

Migration is the umbrella term for a project that includes several more specific processes.

LEGACY DATA MIGRATION

A more specific term for migration projects where the source system is old, poorly documented, or running on outdated technology – emphasizing the added complexity of extracting from legacy infrastructure specifically.

ETL (EXTRACT, TRANSFORM, LOAD)

The technical pipeline used to execute a migration. ETL describes the mechanics; migration describes the overall project, including planning, validation, and cutover, that ETL supports.

DATA MAPPING

One specific component of a migration project – defining field correspondence between source and target. A migration project can’t succeed without accurate mapping, but mapping alone isn’t the whole migration.