Tool
Cloud migration planner
Tell us where you run today, where you are going and what you are moving. You get an illustrative checklist in four phases: assess, design the landing zone, migrate in waves, and operate. It is a place to start planning. It is not a plan, a schedule or a quote.
Describe the move
Answer what you know. The checklist adapts to your answers, and the items that apply to every migration always appear.
This tool runs in your browser and needs JavaScript. Without it, contact us and we will walk through the same questions with you.
The six common paths, per application
The planner works from the idea that each application gets its own path. These are the usual choices.
- 1
Retire
Switch it off. A surprising share of an estate is unused once someone asks.
- 2
Retain
Leave it where it is for now, for a good reason such as a contract, a regulation or a pending replacement.
- 3
Rehost
Move it as is. Fastest, least change and least benefit from the platform.
- 4
Replatform
Make small changes so it uses a managed database, queue or runtime.
- 5
Refactor
Redesign it to use cloud services properly. Highest effort, so choose carefully.
- 6
Replace
Swap it for a SaaS product.
Questions people ask
Do you see my answers?
No. The planner runs in your browser and nothing is sent to us unless you copy or download the checklist and send it yourself.
How long will my migration take?
We do not guess. Duration depends on the number of applications, their dependencies, data volumes, the downtime you can accept and the people available. A short assessment gives you a basis for an estimate.
Which cloud should I choose?
It depends on your identity setup, vendor support for your software, skills, data rules and a cost model of your own workloads. If you select Not decided, the checklist starts with those questions.
Do you work on all three clouds?
Our consultants work on AWS, Microsoft Azure and Google Cloud. That does not mean we hold a partner designation with any of them.
What next?
Take the checklist to your team, assign owners and dates to the Assess items, and talk to us if you want help with the assessment or the landing zone.
Related
-
Cloud
Cloud strategy, readiness assessments, migration, landing zones, governance, FinOps and operations on AWS, Azure and Google Cloud.
-
Cloud and infrastructure operations
Monitoring, patching, backup, cost review and incident handling for cloud accounts, infrastructure and delivery tooling.
-
Project readiness check
Thirty-one planning questions across ten areas. See which ones you have answered, which are still open, and what to do about each.
-
Data migration
Plan, extract, cleanse, map, load and reconcile data between systems, with business owners signing off every object.
Tell us which of these is you
I need a technology project delivered
Describe the system, the change and the timeline. A technical lead replies to talk about scope.
Discuss a projectI need to hire technical talent
Send the role, headcount and start date. A recruiter confirms the details before sourcing starts.
Request talentMy systems may be at risk
Ask for an assessment, a penetration test or help fixing findings. Under attack now? Call.
Speak with a security expert