90 days
Median time to first wave in production
38%
Median run-cost reduction post-migration
0
Production downtime on cutover (target)
What we do

Capabilities under one accountable team.

01

6Rs migration discovery

Application inventory, dependency mapping, workload classification (rehost / replatform / refactor / repurchase / retire / retain), business-case modelling.

02

Wave planning & cutover

Risk-balanced wave plan, infrastructure-as-code blueprints, runbooks, rollback drills. Zero-downtime cutovers using blue-green and database replication patterns.

03

Database & data migration

Oracle → PostgreSQL, SQL Server → Aurora, mainframe DB2 → cloud, with continuous replication, validation, and audit-grade evidence.

04

Post-migration FinOps & SRE

Right-sizing, reserved-capacity planning, autoscaling, observability, SLOs — turn migration into a sustained run-cost reduction, not a one-off.

What to expect

Outcomes you can hold us to — by horizon.

0–90 days

Foundations

Outcome tree, baseline metrics, and a working pilot in production by day 90 — defensible with finance, signed off by risk.

3–12 months

Scale

Squad expansion across the next 2–3 value pools. Live-parallel cutovers. Capability uplift inside the client team.

12+ months

Run & optimise

Managed run with named SLOs, quarterly value reviews, and a continuous-improvement budget reserved for innovation, not toil.

How we deliver

Five steps. One accountable team.

Discover

2–4 weeks

Inventory, dependencies, workload classification, business case with TCO model.

Foundation

4–8 weeks

Landing zones, network, identity, security, observability — the paved road every workload migrates onto.

Wave 1

6–8 weeks

5–10 low-risk workloads end-to-end. Patterns proven, runbooks refined, team trained.

Scale

Q2–Q4

Subsequent waves on monthly cadence with quarterly cost reviews.

Optimise

Continuous

Right-size, reserve, modernise — turn migration into a run-cost-reduction programme.

Anchor case study

Airline operator migrates 220 workloads from on-prem to AWS in 11 months — 41% run-cost cut.

Aviation · APAC
Problem
220 workloads across 4 data centres. Three failed migration attempts. CFO had lost faith.
Solution
Re-baselined inventory + business case, AWS landing zone, 14-wave migration plan, blue-green cutovers for tier-1 workloads, FinOps from week one.
Impact
11-month migration · Run-cost −41% · Zero customer-facing downtime · USD 12.4M annualised savings.
How we engage

Three commercial models. One outcome standard.

We avoid open-ended retainers. Every model names its outcome and its measurement window in the contract.

01 · Diagnose

Fixed-price diagnostic

2–4 week engagement. Outcome tree, baseline metrics, prioritised value pools, and a board-ready 18-month roadmap. Stop-go decision in week 4.

From USD 80k · 2–4 weeks
02 · Pilot

Outcome-linked pilot

8–12 week engagement to ship one value pool, end-to-end, with a measurable KPI commitment. Joint squads with the client team. Live-parallel before cutover.

Outcome-linked + capped fee · 8–12 weeks
03 · Scale & run

Programme + managed run

Multi-quarter scale-out with managed services on top. Quarterly value reviews. SLO-tied annual incentive. Capability transfer by design.

T&M + outcome incentive · Multi-quarter
FAQ

Frequently asked questions

Lift-and-shift or refactor? +

Both. We classify per workload — most enterprises end up with a mix. Lift-and-shift first, modernise once stable, retire what nobody uses.

How do you guarantee zero downtime? +

Blue-green deployments, database replication, traffic shadowing, and rollback drills. We can’t guarantee zero on every workload, but we minimise it explicitly per cutover.

What about data residency? +

In-region migrations across all major hyperscalers. Sovereign-cloud destinations supported. Data classification done up-front so we know where each dataset legally can sit.

Migrating from VMware / Hyper-V? +

Common. We use VMware Cloud on AWS, Azure VMware Solution, or GCP VMware Engine for like-for-like, then refactor in place when ready.

How long for a 200-workload estate? +

Median 11–14 months. Driven by application complexity, business-cycle constraints, and how many workloads can be retired or repurchased.

Can you take over a stalled migration? +

Yes. Recovery diagnostic in 4 weeks with a stop-go recommendation in week 5. We have rescued 20+ stalled cloud programmes.

Talk to a partner

Book a cloud migration briefing.

A senior partner will respond within one business day with a tailored agenda.