Context
- An enterprise SaaS company had to move entirely from AWS to GCP, and a maintenance window was not an option their customers would tolerate. A cost surprise on the far side was just as unacceptable. Both risks had to be engineered out before the first workload moved.
Approach
- Decoupled state, config, and routing so every workload became independently switchable.
- Ran the new environment in shadow with mirrored traffic before any cutover.
- Right-sized and planned commitments as part of the move, not after.
What we built
- Terraform-defined GCP landing zone, segmented and policy-guarded.
- Shadow-then-shift cutover with rollback at every step.
- Spend observability to hold the cost gains.
Results
- Zero downtime across the entire migration.
- 100% of workloads moved.
- 40% reduction in cloud spend, sustained.
Stack & standards
TerraformGoogle CloudAWSKubernetes
Well-ArchitectedSOC 2FinOps
“A migration with no window and a smaller bill. We did not believe both were possible until we saw it.”
AI/ML SaaS engagement
Related work