Cloud Migration
Move to the cloud without carrying the old problems with you.
A migration is not a lift and shift. It is a decision about which parts of the current estate deserve to survive the trip. We inventory what you run and what depends on it, plan the order so the reversible moves happen first, and switch traffic only once the new path has proven itself.
Tools we work in
- AWS
- Azure
- Google Cloud
- Terraform
- Docker
- PostgreSQL
- Cloudflare
Scope
What this covers
The specific work included when you engage us for this service.
- An inventory of what you run, what depends on it and what can be retired instead
- A migration order planned around risk, starting with the reversible workloads
- Lift and shift for systems that should not be redesigned yet
- Re-platforming where a managed service removes genuine operational work
- Cutover plans with a tested rollback path and a named decision point
- A cost comparison of the new estate against what you pay today
What you receive
- 01A written migration plan covering sequence, owners, downtime windows and rollback steps
- 02The migrated environment running in an account and subscription you control
- 03A decommission list naming every system you no longer need to pay for
Questions
Cloud Migration, answered
How long does a migration take?
Longer than a plan suggests and shorter than leaving it another year, which is the honest answer. Discovery is usually measured in weeks. The moves themselves are staged over weeks or months depending on how many systems are involved and how much downtime each one tolerates. The lowest-risk workload goes first, so the process is proven before anything that matters is touched.
Do we have to rewrite everything to be cloud native?
No, and you should not. Plenty of workloads run perfectly well on a virtual machine and gain nothing from being rebuilt as a distributed system, which only adds failure modes to understand. We re-platform the parts where a managed service removes real work, managed databases, queues, object storage, autoscaling, and leave the rest intact.
What happens if the cutover goes wrong?
That is decided before the cutover, not during it. Every move has a documented way back, a named person who decides whether to use it, and a time by which that decision has to be made. For the higher-risk moves we run a rehearsal against a copy first. If a migration has no way back, it has not been planned properly.
Most often requested by
Related
More in Cloud, DevOps & Security
Cloud Architecture & Design
Decisions that are cheap now and expensive to reverse later.
Cloud Cost Optimisation
Most cloud bills contain spend that nobody decided to make.
CI/CD & Release Engineering
Deploys that are boring, which is exactly the point.
Kubernetes & Container Platforms
Containers are quick to adopt and slow to master.
Tell us where the manual work is
A 30-minute call. We map the process, tell you what we would automate or build first, and what it costs. No retainer before you agree the scope.
- No retainer before scope is agreed
- Written plan you can act on alone
- Worldwide delivery, on your hours