What it means
Common approaches include retiring, retaining, relocating, rehosting, replatforming, repurchasing, and refactoring. The best choice depends on business value, risk, dependency, time, cost, and the desired level of modernization.
Why it matters
Migration is not complete when data and workloads move. Identity, monitoring, backup, security ownership, support, and financial management must also transition.
Practical focus
- Inventory dependencies before selecting a migration pattern
- Define success measures and rollback conditions
- Move security and observability with the workload
- Retire old assets and access paths deliberately
Common mistakes
- Using rehosting as a permanent architecture by accident
- Migrating unknown data and technical debt
- Leaving duplicate environments running indefinitely
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: