How to restart a stalled migration without writing a new plan

The frame

A stalled migration triggers a predictable response: rewrite the plan. The plan is rarely the problem. The original plan was usually fine. What changed is that nobody can name the person who owns each workload, and without a name, every decision becomes a meeting, every meeting produces a follow-up, and the migration backlog grows faster than the migration itself. The fix is shorter than a re-plan. It is a four-week reset that re-sequences ownership before it re-sequences work.

Why ownership stalls migrations

The pattern repeats across Fortune 500 advisory engagements. A workload sits in a backlog because three teams have a partial claim on it and none of them has full authority. The platform team owns the destination. The application team owns the code. The compliance team owns the controls. None of them can move the workload alone, and none of them is willing to be the named owner of the move. The plan does not fix this. Only an ownership decision fixes this, and ownership decisions require a sponsor with the standing to make them stick.

The four-week reset

Week one: catalog the stalled workloads and write the current ownership claim, partial or full, against each one. Week two: convene the platform, application, and compliance leads with the executive sponsor and assign a single named owner to each workload. The owner is accountable for the move; the other parties are inputs. Week three: each owner writes a one-page move plan, including the cutover window, the rollback test, and the named approver for each gate. Week four: the first three workloads cut over, on the new ownership model, against the original plan.

What the reset asks of the in-house team

The in-house team has to accept that the work is not new and the plan is not new. What is new is that every workload now has a name next to it, and the name will be in the weekly report. This is uncomfortable for organizations that have spent six months distributing accountability across a slide. It is also the precondition for the migration to finish. The team that pushes back hardest on named ownership is the team whose workload is most stuck.

What the reset asks of the executive sponsor

The sponsor has to make the ownership decisions in week two and defend them in weeks three and four. Ownership is not negotiable after week two. If the sponsor cannot or will not enforce that, the reset does not work, and a new plan will not work either. The sponsor's job in the reset is small in volume and large in consequence. Twenty minutes a week of explicit defense is the difference between a migration that finishes this quarter and a migration that re-stalls in six weeks.

What does not work

What does not work: rewriting the plan, adding a new tool, hiring a system integrator on top of the stuck program, or running a steering committee that meets every two weeks to review status. These responses look like progress and produce none. They are common because they are easier than naming an owner. Naming an owner is the work. Everything else is the activity that surrounds the work.