- Challenge
- The migration has been on the roadmap for two years. That was how the client put it on the first call.
- Approach
- We grouped workloads by risk, moved them in waves with a rollback for each, and re-platformed the one legacy app that was blocking the rest.
- Stack
- AWS MGN · Terraform · containers · RDS
- Result
- The move finished without unplanned downtime, and the old servers were switched off.
Cloud migration
A planned move to cloud or between clouds, without the long weekend.
Talk to an engineerWhat we do
Cloud migration consultancy
An assessment of your Cloud migration setup, with findings ranked by risk and effort.
Cloud migration delivery
We design and build it with your team, in your accounts, documented as we go.
Cloud migration support
Monitoring, patching and upgrades, with incident response agreed per contract.
Cloud migration training
Workshops and pairing on Cloud migration, built around your own systems.
Tools we work with
Discovery & planning
- AWS Migration Hub
- AWS Application Discovery Service
- Azure Migrate
- Google Migration Center
Servers & VMs
- AWS Application Migration Service (MGN)
- Azure Site Recovery
- Migrate to Virtual Machines
- VMware HCX
Databases
- AWS DMS
- Azure Database Migration Service
- Google Database Migration Service
Files & storage
- AWS DataSync
- AWS Snowball
- AzCopy
- Azure Data Box
- Storage Transfer Service
Re-platforming
- Docker
- Kubernetes
- ECS
- Cloud Run
- App Service
- managed databases
Infrastructure as code
- Terraform
- Terragrunt
- OpenTofu
- Ansible
How an engagement runs
- 1 A call. 30 minutes with an engineer to understand the problem.
- 2 A look. Read-only access or a walkthrough, so we scope from facts.
- 3 A proposal. Scope, deliverables and a price model: fixed scope, day rate or retainer.
- 4 The work. In your accounts and repositories, alongside your team.
- 5 A handover. Documentation and a session with your team, so you’re not dependent on us.
Proof
A recent Cloud migration engagement. We keep client names private, but the problem, the work and the outcome are exactly as they happened.
See our workQuestions
Do you work in our accounts or yours?
Yours. Everything we build lives in your cloud accounts and repositories from day one, so there is nothing to migrate when we finish.
Can you work alongside our own team?
Yes, and we prefer it. We can run a project ourselves, embed engineers in your team, or pair with your people so they pick it up as we go.
How is this priced?
Depending on the work: a fixed-scope price, a day rate or a monthly retainer. We agree it in a written proposal before anything starts.