Multiple cloud migrations, up to a full platform architecture

Context

Migrations ran across several years and several engagements, ranging from a handful of servers moving off on-premises hardware to relocating the complete architecture behind a platform serving millions of events a day.

The work spans the three major providers — AWS, Azure and Google Cloud — along with Linode, DigitalOcean and others.

Leadership & decisions

Sequenced by blast radius. Smaller workloads moved first, deliberately, to build the team’s Azure fluency on systems where a mistake was recoverable — before anything business-critical was touched.

Managed services where they earn it. Azure App Service, Azure SQL and Blob Storage replaced self-managed equivalents where the operational saving was real, rather than migrating like-for-like onto virtual machines and carrying the same maintenance burden to a new provider.

Outcome

Production workloads across AWS, Azure and Google Cloud, with the team fluent in each rather than dependent on a single provider.