Move to Google Cloud, with Google funding the work.
We work with Google to fund migrations from AWS and Azure, and aim to get the engagement fully covered. It starts with an assessment, and you know the funding position before you commit to the move.
Straight to a senior GCP architect. No SDR, no slide deck.
Not ready to talk? Check if your migration qualifies for funding
A good fit if
- You run production workloads on AWS or Azure and are considering Google Cloud.
- You want a plan and a cost model for the move before making the decision.
- Your team wants the migration done without pausing product work for a year.
Probably not a fit if
- You want to stay multi cloud with a small footprint on Google Cloud. Funding is aimed at moving workloads, not trialling a service.
Deliverables, not effort.
The assessment is the first deliverable and the one everything else depends on.
Inventory and dependencies
What runs where, what depends on what, and which workloads should move first.
Target architecture
Where each workload lands on Google Cloud, and where it is worth changing the architecture on the way rather than lifting it as is.
Cost model
Projected Google Cloud run cost against what you pay today, workload by workload, with the assumptions written down.
Migration plan and funding position
The waves, the cutover approach, the price, and how much of it Google will fund. You decide from there.
Landing zone
The foundation the workloads move into, built in Terraform in your repositories.
Migrated workloads
Workloads moved in waves, validated before cutover, with a rollback path at each step.
No surprises on the way.
The timeline is set after the assessment, when the size of the estate is known.
- Assessment
Know before you commit
Inventory, dependencies, target architecture and cost model. We apply for funding with Google on your behalf and confirm the position with you.
- Foundation
Somewhere to land
The landing zone is built first, so every workload arrives into the same identity, policy and network setup.
- Pilot
One workload, end to end
A lower risk workload moves first, which proves the approach and the tooling before production is touched.
- Waves and cutover
The rest of the estate
Remaining workloads move in planned waves with data kept in sync, validation before each cutover, and a rollback path.
Not included
- Rewriting applications beyond the changes agreed in the migration plan.
- Cloud usage on either side during the migration.
- Decommissioning contracts or reserved capacity with your current provider.
What we need from you
- Read access to your current cloud accounts for the assessment.
- Engineers who know the workloads, available for the dependency mapping.
- A decision maker for the funding application and the go or no go after assessment.
Questions we get asked
Does Google really fund the whole migration?
Google runs funding programmes for migrations onto Google Cloud, and we aim to get the engagement fully covered. Eligibility and the amount are Google’s decision and depend on the workloads, so we confirm the position after the assessment and before you commit to anything.
What if our migration does not qualify for full funding?
You get a fixed price for the part that is not covered, alongside the assessment, and decide from there. There is no obligation to proceed.
Do you migrate from Azure as well as AWS?
Yes. The approach is the same: assessment, landing zone, pilot, then waves. The service mapping differs, and the assessment covers it for your estate.
Will there be downtime?
The cutover approach is planned per workload in the assessment. Most workloads can move with data kept in sync and traffic shifted, so the switch is brief or invisible to customers. Where a window is needed, we plan it with you.
Fixed price, fixed date, before you sign.
Rapid MVP
4 weeks
A$16,000
Agent MVP
2 weeks
A$25,000
Cloud Foundations
Fixed date, set at scoping
From A$45,000
Managed SRE and Agentic SOC
Ongoing
From A$5,000 / month
Prices are set in AUD; other currencies are fixed conversions as at 15 September 2026, shown for guidance, with the contracted currency confirmed before you sign.
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