Zhivko Todorov
ALL CASE STUDIES

CASE 05 · NORTHWIND · 2024

MIGRATION6RVMWAREDMS

Twenty-eight workloads off on-prem, in fourteen weeks.

A logistics SaaS with a single data centre lease ending in five months. Twenty-eight production workloads. Half of them critical, half of them undocumented. We assessed every one with the 6R framework and shipped the migration in four phased waves.

INDUSTRY

Logistics SaaS

DOMAIN

MIGRATION

DELIVERED

2024

STACK

MGN·DMS·AURORA POSTGRES·EKS·EC2·S3·TRANSIT GATEWAY·DIRECT CONNECT

RESULTS

What changed, by the numbers.

WORKLOADS

28

PRODUCTION, MIGRATED

TIMELINE

14w

KICKOFF → DC DECOMMISSION

CUTOVER DOWNTIME

< 2h

AGGREGATE, ALL WORKLOADS

RUN-RATE COST

−18%

POST RIGHT-SIZE

HOW IT WENT

The discovery phase took two weeks and produced a spreadsheet nobody had bothered to make before: twenty-eight workloads, their owners, their dependencies, their compliance scope, and their realistic 6R disposition. Twelve rehosted, ten replatformed, three refactored, two retired, one retained.

AWS Application Migration Service did the heavy lifting on the rehost workloads. DMS handled the database migrations with continuous replication so cutover windows could be tight. The replatform set moved to EKS or ECS Fargate depending on whether they were already containerised.

Wave four was the rollback wave we never had to do. The data centre handover was uneventful. The bill came in 18% lower than the on-prem TCO; the team got their Saturday afternoons back.

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 →