Zhivko Todorov
ALL CASE STUDIES

CASE 53 · KINDRED · 2024

DATACENTRE EXITMGN6RTRANSIT GATEWAY

Forty workloads out of one data centre, before the lease ended.

A logistics tech company had a single colo with 40 production workloads, six months left on the lease, and no extension option. We ran the assessment, built the landing zone, and migrated everything with thirteen days of slack at the end.

INDUSTRY

Logistics tech

DOMAIN

MIGRATION

DELIVERED

2024

STACK

AWS MGN·DMS·TRANSIT GATEWAY·DIRECT CONNECT·EKS·AURORA POSTGRES·CONTROL TOWER

RESULTS

What changed, by the numbers.

WORKLOADS MIGRATED

40

IN 5 MONTHS

SLACK AT DEADLINE

13d

BUFFER PRESERVED

CUTOVER DOWNTIME

< 4h

AGGREGATE, WORST CASE

POST-MIGRATION COST

−14%

VS COLO TCO

HOW IT WENT

The brief was non-negotiable: lease ends June 30, no extension. The team had been planning the migration for eight months and not migrating anything because every plan got bigger when reviewed. We started by drawing a line through workloads — rehost where we could, replatform where it made sense, retire where nobody could explain the workload’s purpose.

AWS Application Migration Service did the bulk of the rehost work. Twelve workloads got the lift-and-shift treatment first to de-risk the schedule. DMS handled the database tier with continuous replication and tight cutover windows. Direct Connect bridged the colo to the AWS landing zone during the transition.

The last workload cut over thirteen days before the lease ended. The colo team did the physical decommissioning under contract. Total downtime across all 40 workloads, aggregated: under four hours. Run-rate cost on AWS came in 14% under the colo total cost of ownership.

READY WHEN YOU ARE

Let's get your AWS bill (and architecture) in order.

The discovery call is free. You walk away with at least one concrete idea — even if we never work together.

Or email directly →