The part of a cloud migration nobody plans for
Moving servers is the easy half. Changing how teams work is the rest.

Cloud migration plans are usually precise about the technology: which workloads move, in what order, on which weekend. They are often vague about the people who will run those workloads the following Monday.
The old habits move with the servers
If releases were manual before, they will be manual in the cloud, only faster to break. If nobody owned cost before, the first monthly bill will be a surprise. A migration that copies old habits copies old problems at a new price.
Decide who owns what, in writing
Who approves new infrastructure? Who watches the bill? Who is woken up at night, and with what runbook? These questions take an afternoon to answer and months to fix if they are skipped.
Teach while you move
The safest migrations pair the people doing the move with the people who will inherit it. Every workload that lands is a lesson in pipelines, monitoring and infrastructure as code. By the last move, the team is running the platform, not watching it.
Measure the Monday, not the weekend
Success is not the cut-over going quietly. It is the first ordinary week afterwards: releases shipping, alerts making sense and costs where the plan said they would be. Plan for that week from the start.