Engagement roadmap
A typical sequence for cloud migration planning consulting. Not every client needs every stage; the roadmap shows how decisions build when you start from an unclear inventory.
-
1. Scope & success criteria
Confirm which programmes are in play, what “done” means for wave one, and which freeze windows are non-negotiable on the United Kingdom calendar.
-
2. Inventory & dependencies
Name systems the way on-call names them. Map shared data stores, batch jobs, and identity couplings that would stall a cutover if left informal.
-
3. Placement decisions
Score what moves, stays, or is replaced using criteria your sponsors can defend — cost, latency, compliance, and ownership — not brand preference alone.
-
4. Wave sequencing
Order cutovers, dual-run periods, and exit checks so wave one finishes with callable abort rules instead of open-ended parallel production.
-
5. Cost envelope & runbooks
Translate the target shape into an informational cost envelope, then write night-of steps, verification checks, and rollback triggers with named roles.
-
6. Advisory while you execute
Optional retainer reviews keep the plan current as schemas and calendars change. Execution remains with your engineers or chosen delivery partners.