Migrations go wrong for ordinary reasons: a forgotten scheduled job, a hard-coded address, a backup that was never restored. A calm migration is mostly preparation.
Know what you have
List every application, database, scheduled task and integration, along with who depends on it. The items that cause trouble are the ones no one remembered to write down.
Move in an order that limits risk
Start with something low-stakes to prove the pipeline, networking and monitoring. Move critical systems once the route is well travelled. For each step, define what success looks like and how to go back.
Test the rollback and the restore
A rollback plan that has not been rehearsed is a hope. Restore a backup into the new environment before you rely on it, and practise the cut-over on a copy.
Watch the bill from day one
Tag resources by system, set budget alerts and review spend after the first full month. Right-sizing in the first quarter usually recovers more than any later optimisation project.