Prerequisites You need baseline observability, a defined rollback strategy, and agreement on which environments must stay compliant with existing controls. Phase 1 — Stabilize delivery Introduce CI/CD and infrastructure-as-code on the current stack before moving workloads. Phase 2 — Migrate high-change modules Move services with frequent releases first to prove the pipeline and monitoring model. Phase 3 — Data and integration cutover Plan cutovers around business quiet periods with rehearsed rollback paths. Common pitfalls • Migrating low-change legacy first because it feels 'easy'. • Skipping observability until after migration. • Treating cloud migration as purely infrastructure instead of an operating model change.