Skip to content

Service · Cloud

Cloud Migration Services

Commission us to move running systems from data centres, colocation or another provider into the cloud, one planned wave at a time. Each move has a rehearsed cutover, a rollback route and a named owner, so the business keeps operating while infrastructure changes underneath it.

Dependency map before any move

Rehearsed cutover for every wave

Rollback route agreed in advance

Deliverables

What a cloud migration engagement delivers.

01Delivered

Workload inventory and assessment

Every server, database and scheduled job catalogued with owner, dependencies, data volume, licence terms and a treatment: rehost, replatform, refactor, retire or retain.

02Delivered

Wave plan

Workloads grouped into waves by dependency and risk, with lower-stakes systems first so the process is proven before critical ones move.

03Delivered

Target environment

Destination accounts, networks and connectivity back to systems staying on-premises, ready before the first wave starts.

04Delivered

Cutover runbooks

Step-by-step plans per wave covering data sync, freeze windows, DNS changes, smoke tests, go/no-go criteria and who makes the call.

05Delivered

Decommissioning record

Confirmation that source systems are shut down, retention obligations met and licences or contracts ended, so you stop paying twice.

Early decisions

Technical decisions we settle early in cloud migration.

01Decided

Treatment per workload

Rehosting is fastest but carries old inefficiencies across; replatforming onto managed databases or containers costs more effort but removes upkeep. We decide per system, not per estate.

02Decided

Data synchronisation method

Native replication, change data capture or offline transfer, chosen by data size, acceptable downtime and available bandwidth.

03Decided

Downtime tolerance

The longest acceptable outage per system, agreed with the business, which decides between a weekend window and near-continuous replication.

04Decided

Licensing after the move

Whether existing database and operating system licences can be brought across, or whether licence-included cloud services work out cheaper.

05Decided

Hybrid connectivity

VPN or dedicated links such as Direct Connect, ExpressRoute or Cloud Interconnect, sized for replication traffic and for systems left behind.

Engagement

How a cloud migration engagement runs.

  1. 01Phase 1

    Discovery and dependency mapping

    Agent-based or network-flow discovery reveals which systems talk to each other, including undocumented connections that break cutovers.

  2. 02Phase 2

    Pilot wave

    A small, low-risk group moves first, testing tooling, runbook format and the communication plan with real users.

  3. 03Phase 3

    Wave execution

    Each wave follows rehearsal, freeze, sync, cutover and hypercare, with lessons from the previous wave written into the next runbook.

  4. 04Phase 4

    Rightsizing and exit

    Once workloads settle, we rightsize against observed usage, retire the source environment and close with a before-and-after cost comparison.

Fit

When a planned cloud migration is the right choice.

01Good fit

A data centre contract or hardware refresh is due

A fixed exit date makes sequencing essential, because rushed final waves carry the most risk.

02Good fit

Dependencies are tangled

Where nobody is sure which applications share a database, discovery and wave planning prevent outages.

03Good fit

You want to move first and modernise later

Migrating with minimal change, then improving workloads once in the cloud, spreads risk across two smaller steps.

Treatments, and why each workload gets one

Each workload can be rehosted, replatformed, refactored, repurchased as SaaS, retained or retired. Assigning a treatment per system, with the reason recorded, keeps the programme honest about effort.

Retiring unused systems before migration is often the cheapest saving on offer.

Finding what the documentation missed

Configuration databases rarely match reality. A reporting job that reads a production database nightly, or a file share mounted by three applications, will break if moved in the wrong order. Discovery tooling and network flow data give us a dependency map that waves are planned against.

Rehearsal makes cutovers dull

Every cutover is rehearsed against a copy of production data before the real window, with timings recorded. Rehearsal finds the slow export, the missing firewall rule and the hard-coded IP address while there is still time to fix them.

Hypercare, then switch the source off

After each cutover, a hypercare period watches error rates, performance and user reports closely. Once agreed criteria are met, the source is decommissioned. Leaving it running for months doubles cost and blurs which system holds the truth.

FAQ

Questions to resolve before the build.

01Should we move everything at once?

Almost never. A single big cutover concentrates every risk into one window. Waves let you learn from early moves and keep trading if one system has to roll back.

02How do you move databases that cannot go offline for long?

We replicate continuously into the target using native replication or a service such as AWS Database Migration Service, then switch during a short window once the replica has caught up.

03What if a cutover goes wrong?

Each runbook has go/no-go checkpoints and a rollback route returning traffic to the source, which stays intact until the new environment has run cleanly through hypercare.

04Will costs fall after migration?

Not automatically. Rehosted servers sized like their on-premises predecessors often cost more. Savings come from rightsizing, managed services and switching off idle capacity, which we address after the move.

Primary sources

References behind this page

Dated official documentation, standards, and research that support the factual claims on this page.

  1. 01
  2. 02

How to read this page

Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.

Next decision

Turn the brief into an accepted product scope.

Define outcomes, constraints, evidence, rights and handover before delivery begins.

Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.