Skip to content
10 · service

Cloud migration without the big bang weekend.

Move from VMs, a single server or another cloud onto Azure or AWS, service by service, with rollback plans and no long outage window. You end up on infrastructure as code, not a copy of the old mess.

Get a quote
the problem

The old setup is holding you back.

  • One server does everything

    App, database and cron jobs share one machine, and a reboot is a planned outage.

  • Fear of downtime

    The migration keeps getting postponed because nobody wants to risk a long outage.

  • Unknown dependencies

    Nobody is sure what talks to what until something breaks after the move.

  • Lift and shift regret

    A previous move copied the problems across instead of fixing them.

what I do

What the engagement covers.

  1. 01

    Discovery and plan

    Map services, data and dependencies, then plan the order of the move with rollback points.

  2. 02

    Landing zone

    Networking, identity, logging and guardrails in the target cloud, all in Terraform or Bicep.

  3. 03

    Containerization

    Package applications in Docker so they run the same way everywhere.

  4. 04

    Data migration

    Database replication or staged cutovers so data moves without long write freezes.

  5. 05

    Incremental cutover

    Move traffic service by service with DNS and load balancer weights, not a single switch.

  6. 06

    Decommissioning

    Shut down the old environment cleanly once everything is proven in the new one.

deliverables

What you get at the end

  • A migration plan with order, risks and rollback points
  • Landing zone in the target cloud defined as code
  • Containerized applications with CI/CD
  • Data migrated with verification checks
  • Cutover runbook and post migration monitoring
  • Old environment decommissioned and documented
stack

Tools I use

  • Azure
  • AWS
  • Terraform
  • Bicep
  • Docker
  • Kubernetes
  • Azure Database Migration Service
  • AWS DMS
  • PostgreSQL
  • Azure Front Door
  • Route 53
  • GitHub Actions
faq

Migration questions.

Will there be downtime?
The goal is none or a few minutes for the final data cutover. The plan names every window in advance so nothing is a surprise.
Do we have to move to Kubernetes?
No. Containers on a managed service like Azure Container Apps or ECS are often a better first step. We choose based on your team.
How is the price decided?
After a short call I send a written scope and a fixed quote. No hourly surprises, and nothing starts until you have agreed the scope.
Can you migrate between Azure and AWS?
Yes. I run production on Azure today, built AWS environments with Terraform before that, and hold the AWS Solutions Architect Associate certification.

related services

Let us plan your move.

Tell me what you run today and where you want to be. We will plan the order of the move together.

Get a quote