Cloud Migration
Moving applications and data from on-premise systems to the cloud, frequently paired with retiring legacy infrastructure.
What Is Cloud Migration?
Cloud migration is the process of moving applications, workloads, and data from on-premise infrastructure to cloud environments. In an archiving and decommissioning context, it often creates a second question: what historical data actually needs to move with the application, and what can be preserved independently in an archive?
A well-planned cloud migration separates active operational data from historical information that does not need to remain in the live application. Historical records can be extracted, structured, validated, and retained in a governed archive before legacy infrastructure is shut down. This can reduce the volume moved into the cloud and keep the target environment focused on data that supports current operations.
The alternative is to lift every record into the new environment simply because it exists in the old one. That approach can increase migration scope, cloud storage requirements, testing effort, and the time needed to validate the new system. Archiving gives the migration team a controlled path for retaining historical data without carrying the full legacy footprint forward.
Key Points
- No legacy footprint by default. Historical data can be retained independently while the old servers, databases, and application infrastructure are retired.
- Separates active from historical data. Data required for daily operations can move to the target application while older records remain in a governed archive.
- Reduces migration scope. Excluding unnecessary historical volume can simplify extraction, transformation, testing, reconciliation, and cutover activities.
- Supports compliance after migration. Archived records remain available for retention, audit, legal discovery, and historical reporting after the source environment is shut down.
- Works across migration approaches. Whether the project uses rehosting, refactoring, replatforming, or application replacement, archival planning can be treated as a distinct workstream.
Common Use Cases
☁️ Cloud ERP migration
Organizations moving from on-premise ERP platforms can archive historical transactions before moving active workloads to a cloud ERP.
🏢 Data center exit
Teams closing a data center can preserve required historical application data without relocating every legacy server or database to the cloud.
🔄 Application modernization
Modernization programs can separate historical data from the application being redesigned, reducing the amount of legacy information carried into the modern platform.
Cloud Migration vs. Related Concepts
Cloud migration sits next to related terms it’s often mistaken for.
REHOSTING
Moving an existing application and its data to cloud infrastructure with limited change. Archiving may reduce the historical footprint before the move.
DATA CENTER CONSOLIDATION
Reducing physical infrastructure and application footprint. Cloud migration can be one enabler, while archiving helps remove systems that do not need to move.
APPLICATION DECOMMISSIONING
Retiring an application after its business and compliance data has been preserved. Cloud migration and decommissioning can occur together when legacy applications are replaced.
See Also
Ready to put this into practice?
See how Archon helps organizations with compliant archiving and legacy decommissioning.