Plan your move off AWS with a funded assessment
Google funds the discovery assessment for qualifying workloads. We plan the migration, run it with zero-downtime cutover as the target, and for eligible estates our AWS cost guarantee backs a saving of at least 20%.
Where the savings come from
The structural differences that lower the bill on Google Cloud.
Custom machine shapes
AWS instance sizes step up in fixed increments, such as m5.xlarge to m5.2xlarge. Compute Engine lets you set vCPU and memory to what each workload uses, so you stop paying for the gap.
GKE Autopilot and Cloud Run
GKE Autopilot bills for the resources your pods request rather than for idle nodes, and Cloud Run scales to zero when there is no traffic.
BigQuery vs provisioned Redshift
Provisioned Redshift clusters bill around the clock. Serverless BigQuery bills for the queries you run, so a quiet night costs close to nothing.
Right-sized replatforming
Your AWS footprint reflects years of past decisions. Migration is the time to remove unused instances, right-size databases and rebuild the platform in Terraform.
How Hapana moved from AWS to Google Cloud with zero downtime
99.999%
Production SLA
10 Mos
vs 2.5 Yr Estimate
0 min
Cutover Downtime
10,000
Containers in 10s
Hapana, a global fitness and wellness platform, was held back on AWS by rising infrastructure overhead, slow deployments and fragmented backend services. Previous estimates put the replatforming at 2.5 years.
Aviato built a Terraform landing zone on Google Cloud, moved the backend microservices to Cloud Run, and kept member billing in sync with physical door controllers worldwide. Production cutover was delivered in 10 months with zero minutes of customer downtime.
How an AWS migration runs
Three phases, with production untouched until cutover.
Google-funded discovery and cost model
Agentless scanning of your AWS environment to map dependencies and calculate your Google Cloud run-rate. Google Cloud funds the assessment for qualifying workloads.
Terraform landing zone and pilot
We deploy a Google Cloud foundation with project hierarchy, VPC networking and security guardrails, then migrate a pilot workload with no production impact.
Production cutover
Continuous data synchronisation, pre-cutover validation and automated traffic shifting, using the same playbook we ran for Hapana.
Choosing a Google Cloud database for your AWS workloads
Moving from RDS, Aurora, DynamoDB, ElastiCache or Redshift? Use the database decision tree or the database selector and query simulator to compare Spanner, AlloyDB, Cloud SQL, Firestore and Bigtable, and avoid the DynamoDB to Bigtable JSON trap.
Google funds the upfront assessment
For qualifying workloads, Google Cloud's migration programs fund a discovery of your AWS environment, dependency mapping and cost modelling at no cost to you.
Questions we get asked
How does the Google-funded AWS migration assessment work?
For qualifying AWS estates, Google Cloud funds the upfront discovery and TCO assessment delivered by Aviato Consulting. We inventory your EC2, RDS, EKS and S3 workloads, map dependencies, and produce a target Google Cloud architecture and wave migration plan at no cost to you.
How do you migrate production databases from AWS RDS or Aurora without downtime?
We use Google Cloud Database Migration Service (DMS) and Datastream for continuous Change Data Capture (CDC) replication from RDS or Aurora to Cloud SQL or AlloyDB, validating parity in parallel before a sub-minute DNS or proxy cutover.
Where do the savings on Google Cloud come from?
Custom Compute Engine machine shapes (avoiding the over-provisioning that fixed AWS instance sizes force), automatic sustained use discounts, GKE Autopilot pod-level billing, and serverless BigQuery in place of always-on Redshift clusters.
Can we keep our existing Terraform and GitHub Actions pipelines?
Yes. We deliver your target Google Cloud landing zone and workload infrastructure as modular Terraform and authenticate your existing GitHub Actions or GitLab CI pipelines via keyless Workload Identity Federation.
Talk to an architect who has done this before.
Bring your current setup and the outcome you need. You will get a view on the approach, the risks and roughly what it costs.
Straight to a senior GCP architect. No SDR, no slide deck.
Not ready to talk? See how we migrated Hapana off AWS →
Or call +61 2 8359 9507 · Hello@aviato.consulting