Workload Migration and Modernization
Workload Migration and Modernization tests how you assess a portfolio, choose a migration pattern, and modernize without breaking dependencies or compliance.
Assess before you move
Inventory applications, owners, dependencies, latency, data volume, and licensing. Map each workload to one of the six Rs: rehost, replatform, refactor, repurchase, retire, or retain. Sequence migrations into waves so shared dependencies move together.
Pick the landing zone
Rehost VMware workloads with IBM Cloud VMware Solutions; move AIX, IBM i, and Linux on Power workloads to Power Virtual Server; replatform containers to ROKS; refactor event-driven functions to Code Engine. IBM Cloud Satellite extends IBM Cloud services to on-premises or edge locations when data cannot move. For large datasets, use IBM Cloud Mass Data Migration or high-speed transfer over Direct Link rather than internet upload.
Worked example
A retailer has 150 VMs, a latency-sensitive inventory system, and a five-year-old Java app. Reasoning: first migrate the Java app rehosted to VPC in an MZR, then replatform it into containers on ROKS once dependencies are mapped. Keep the inventory system near its database and use Direct Link for stable latency. Do not refactor everything in wave one.
Traps
Migrating without dependency mapping; assuming lift-and-shift automatically cuts cost; forgetting egress, licensing, and refactoring effort; treating Satellite as a quick fix for every on-premises requirement.