1 September 2026 · Michael Filipsen
The three early signs a cloud migration is about to stall
Most stalled cloud migrations don’t fail suddenly. By the time a program is officially “at risk,” the warning signs have usually been visible for months. Here are the three I see most often.
1. The migration wave plan stops shrinking
Early in a migration, the backlog of remaining workloads should shrink steadily, wave by wave. The first sign of trouble is when it stops shrinking — new discovered dependencies get added to the plan at roughly the same rate old items get completed. The total looks stable, but the program isn’t actually making progress toward zero.
If you’re tracking a migration and the “remaining workloads” number has been flat for more than a month, that’s worth investigating before it becomes a budget conversation.
2. Nobody can explain the current architecture end to end
On a healthy migration program, someone can walk you through how a given application actually runs in its new environment — the network path, the data flow, the failure modes — without needing to pull in three other people. When that explanation starts requiring a room full of specialists because no one individually holds the full picture, coordination overhead has quietly become the bottleneck, even if nobody’s called it that yet.
3. “We’ll fix it after go-live” becomes the default answer
Every migration accumulates a list of things that are good enough for now but not built to last — that’s normal. The concerning pattern is when that list stops getting smaller after go-live, because the team that would fix it has already moved to the next wave. A year later, that backlog of deferred fixes has usually become the reason the environment is hard to operate and expensive to run.
What to do about it
None of these three signs mean a migration is doomed. They mean it’s a good time for a focused, outside look at the plan — usually a one-to-two week diagnostic is enough to tell you whether the program needs a course correction or just needs to keep going. Waiting until the budget or the timeline forces the conversation almost always makes the fix more expensive.
If any of this sounds familiar, get in touch and describe where things stand — happy to give you a straight read on it.