Know what the move will take before it starts.
Get a practical plan for moving the right systems to the cloud, with estimated costs, dependencies and likely disruption made clear. We build on decisions you've already made and investigate what is still uncertain.
When it helps
When a move needs a clearer cost, sequence or view of the risks before you set it in motion.
The real cost is unclear
A cloud estimate gives you one number, but the cost of the move and the work to run it are harder to see.
- Estimate the migration work and likely running costs.
- Account for temporary overlap with the current setup.
- Show the assumptions and decisions that could change the figures.
The business cannot stop for the move
Customers and staff rely on these systems. You need to understand when a move could interrupt their work.
- Identify services that need careful changeover timing.
- Plan checks for working services and complete data.
- Define feasible fallback steps and their limits.
Moving one system affects several others
Applications, data and external services depend on each other, making it hard to tell what can move first.
- Map dependencies around the systems in scope.
- Identify what should move together and what can stay.
- Set out a sequence with clear checks between stages.
The direction is set. The details keep waiting.
You know where you want to go, but product work and daily demands leave little time to turn that decision into a workable plan.
- Build on your existing choices and documentation.
- Resolve missing detail with your team or provider.
- Turn the agreed approach into steps someone can carry out.
A clear route from the current setup to the next.
We plan the move for an agreed set of systems, showing the decisions, costs and checks each stage depends on.
The detail behind a workable move.
- Review of the agreed systems, dependencies, existing plans and business constraints.
- Proposed destination setup, including which systems should move or stay.
- Estimates for migration work, running costs and any period of overlap.
- Migration stages, expected interruptions, validation checks and feasible fallback steps.
- Planning discussions and a walkthrough with the people involved in the move.
A plan your team can act on.
- A map of the systems and dependencies covered by the plan.
- A proposed destination with the reasoning behind the main choices.
- Cost estimates with assumptions, exclusions and unresolved questions.
- A phased migration plan with responsibilities, decision points, checks and fallback arrangements.
Not part of this planning work.
Any further work is optional and agreed separately.
- Building the destination or transferring systems and data.
- Rewriting applications or fixing the issues identified during planning.
- Ongoing cloud management, monitoring or incident response.
How it works
We gather the detail and develop the plan with your team or provider, keeping business priorities and existing decisions in view.
Agree what to plan
We discuss the reason for the move, decisions already made and the systems involved. We agree the planning scope, required access, price and timing before work begins.
Check the current setup
We review the systems and available documentation, working with your team or provider to identify dependencies, constraints and missing information.
Build the migration plan
We define the proposed destination, estimate costs and work through the move in stages. Each stage includes checks, likely interruption and what to do if it cannot proceed.
Walk through the decisions
We review the plan with you and the people who may carry it out, explain the tradeoffs and record any decisions or checks still needed before implementation.
Need a clearer plan for the move?
An informal 30-minute call to discuss the move you're considering and see whether Cloud Migration Plan is the right fit.