Skip to content

Cloud Migration & Modernization

Datacenter to cloud, VM to container, cloud to cloud: an honest rehost, replatform, refactor, retain or retire decision per workload.

The problem

A lease is ending, a platform is out of support, or the cost of standing still has become visible. The estate is large, the dependencies are undocumented, and a lift-and-shift of everything would move the problems rather than solve them.

What you receive

  • A migration architecture and wave plan with dependencies resolved
  • A disposition for every workload and the reasoning behind it
  • Landing zone and deployment patterns the migrated workloads use
  • Cutover runbooks and a decommissioning plan for what is left behind

Capabilities

  • Discovery and dependency mapping of the existing estate
  • Per-workload disposition: rehost, replatform, refactor, retain or retire
  • Landing zone, networking and identity ready before the first workload moves
  • VM, container and managed-service migration paths
  • Database migration planning and execution
  • Staged hybrid operation during the migration
  • Cutover planning, rehearsal and rollback

Example engagement

Datacenter exit for a manufacturer with 60 VMs and an Oracle estate

Mapped dependencies, retired a fifth of the estate outright, rehosted the bulk into a new landing zone, replatformed the web tier onto containers, and migrated the database with a rehearsed cutover, finishing before the lease ended.

Representative of the work; client details are not published.

Technologies

  • Azure Migrate
  • AWS Migration Hub
  • Azure Database Migration Service
  • AWS DMS
  • Terraform
  • Kubernetes
  • Site Recovery

Before you write to us

The questions we get asked first.

Answered the way we would on a call. The consulting FAQ covers how engagements work in general.

Is lift and shift ever the right answer?
For some workloads, yes: frozen ones with no cloud dependency problems, where the goal is to vacate a data centre on a date. As a plan for the whole estate it moves the problems with the servers. Each workload gets a disposition: retire, retain, repurchase, rehost, replatform or refactor.
How do you keep the business running during the move?
Waves grouped by dependency, each with a rehearsed rollback and a success measure about the business rather than about servers. Data sets the schedule: a one-time copy, continuous replication or dual-running is decided per stateful workload before its wave.
What access do you need?
Read access to the current estate (an inventory we build with the owners, not a port scan), the target cloud accounts, and the network between them, and a few hours of the team's time. Nothing is run under your production credentials from outside your own tooling, and write access only arrives with an implementation phase, through your pipeline and your review.
What happens after the engagement?
Everything is written down and handed over: the decisions, the code, the runbooks and the reasons. Your team runs it. Where a standing arrangement makes sense, a retainer or a few architect days a month keeps the context without keeping us on the payroll.