Skip to content
Aviato Consulting
#GoogleCloud • • 6 min read

Choosing a Google Cloud Migration Partner in Australia

How to compare Google Cloud migration partners in Australia: RaMP funding, Essential Eight, data residency, code ownership and handover, with a scorecard.

Short answer: A good Google Cloud migration partner for an Australian mid-market business can show you how they access Google funding (RaMP), prove they build to the ACSC Essential Eight and keep data in Australian regions, name the engineers who will do the work, and hand over all code and pipelines from the first sprint. Score every shortlisted partner against the five areas below and the scorecard further down.

Comparing day rates or brand names tells you very little. What matters is who builds the platform, what they leave behind, and whether your own engineers can run it after cutover. This guide is written for teams migrating roughly 50 to 500 virtual machines or databases to Google Cloud.

For background on the migration process itself, see our Google Cloud migration service.


1. Access to Google migration funding (RaMP)

Google’s Rapid Migration and Modernization Program (RaMP) can help offset the cost of larger migrations. Eligibility, funding levels and minimum expected cloud spend are set by Google and change over time, so treat any figure a partner quotes as something to confirm in writing.

What to look for:

  • Experience with funding applications. Ask how many RaMP-backed migrations the partner has delivered and what share of fees the funding covered. A partner that has never claimed it is guessing.
  • Proper discovery tooling. The partner should use Google Cloud Migration Center (which now includes the StratoZone discovery capability) to produce a total cost of ownership estimate based on your actual estate, not a rough rule of thumb.
  • Billing labels in the code. Required tagging and labelling should be written into your Terraform from the start. Missing labels can make it harder to evidence consumption later.

You can run a first check yourself with our migration funding check.


2. Australian compliance and data residency

Many mid-market companies inherit obligations from their customers, such as APRA CPS 234, the Privacy Act or supply chain security clauses. A partner should turn those requirements into working infrastructure code, not a slide.

  • ACSC Essential Eight. Ask for tested Terraform modules that enforce multi-factor authentication, restrict application execution and automate operating system patching.
  • Data residency. Confirm that resources are restricted to australia-southeast1 (Sydney) and australia-southeast2 (Melbourne) using the Organization Policy constraint constraints/gcp.resourceLocations, so a developer cannot create a resource overseas by accident.
  • Identity and keys. Avoid partners who leave static service account JSON keys on virtual machines. Look for Workload Identity Federation and customer-managed encryption keys (CMEK) in Cloud KMS.

Our Google Cloud landing zone page shows how we set these controls up.


3. Who actually does the work

A common pattern is that principal architects sell the project and junior teams deliver it.

  • Named people in the contract. Require the lead architect and senior engineers to be named.
  • Time zone overlap. If delivery is blended onshore and offshore, technical leads should work Australian Eastern time (AEST or AEDT) during cutover windows so problems get fixed while your business is awake.
  • Engineers, not coordinators. For estates of 50 to 500 workloads, check that platform engineers outnumber project managers and scrum coaches.

4. Ownership of the infrastructure code

A migration should leave you with automated pipelines and readable code, not a system that only the partner can change.

  • Open tooling. Look for standard Terraform or OpenTofu, using Cloud Foundation Fabric modules or patterns from the Google Cloud Well-Architected Framework.
  • No proprietary wrappers. Be wary of closed management portals or abstraction layers that need a paid licence to edit.
  • Repository handover from day one. Code, CI/CD pipelines (Cloud Build or GitHub Actions) and documentation should live in your repositories from the first sprint, not arrive in a zip file at the end.

5. Commercial structure

Separate migration delivery from ongoing operations in the proposal.

  • Fixed milestones for defined work. Price discovery and the landing zone as fixed milestones tied to a clear deliverable, for example “production landing zone deployed and verified”. Use time and materials for application refactoring, where scope is harder to fix.
  • No bundled lock-in. Treat a low migration quote that requires a 12 to 36 month managed services contract with caution. If you want help running the platform, that is a separate decision (see managed services).

Partner evaluation scorecard

Score each shortlisted partner during discovery and proposal review.

Dimension3 points2 points0 points (disqualifying)
FundingHas delivered RaMP-backed projects and can show the fee offsetHelps with basic credits but has no RaMP track recordQuotes full rates without looking at co-funding
Code ownershipTerraform or OpenTofu pushed to your Git repositories during deliveryCode handed over only at the endBlack-box tooling or manual console builds
Australian complianceTested modules for Essential Eight and region locksControls added manually with custom scriptsUnfamiliar with ACSC guidance or data residency
ArchitectureUses GKE Autopilot, Cloud Run and managed databases where they fitStraight lift and shift of VMs to Compute EngineProposes multi-cluster service meshes with no technical need
HandoverPair programming and training for your engineersStatic runbooks and one handover sessionNeeds a multi-year retainer to support what it built

Three screening questions for technical interviews

  1. “Can you show us a sanitised Terraform repository from a landing zone you delivered for an Australian client?” Look for modular design, consistent variable typing, separate state per environment and no hardcoded credentials.

  2. “How will you migrate our database with minimal downtime?” Look for hands-on experience with Database Migration Service, a clear cutover plan, and a documented fallback if replication lags.

  3. “How many hours of pair programming are written into the contract?” Look for a specific number of hours where partner engineers build alongside your staff, not runbooks written in isolation.


The bottom line

The partner you choose decides whether you finish the migration able to run your own platform or tied to a retainer. Favour partners who bring funding experience, write code in your repositories and train your team as they go. If you want a second opinion on a proposal, see how we work as a Google Cloud Premier Partner.


Planning a Google Cloud migration?

If you want help assessing migration feasibility, checking RaMP eligibility or building a landing zone that meets Australian requirements, talk to us.

Tags: #Google Cloud #Cloud Migration #Google Cloud Partner #RaMP #Australia
Written by

Google Cloud Specialists

Engineering consultant at Aviato Consulting specializing in cloud infrastructure, security, and agentic AI systems on Google Cloud.

Keep Reading
#GoogleCloud

Governing AI at Scale in Financial Services

Banks and insurers have proven AI works. The next question is whether they can run thousands of agents and still show a regulator exactly what each one did. A seven control framework and a 90 day plan for APRA, MAS, RBI and BNM expectations on Google Cloud.

FAQ

Frequently Asked Questions

What is Google's Rapid Migration and Modernization Program (RaMP)?

RaMP is a Google Cloud programme that provides funding, tooling and guidance for customers migrating workloads to Google Cloud. Funding is usually delivered as services credits through a qualified partner. Eligibility and amounts are set by Google and depend on the size of the project and the expected cloud consumption, so ask a partner to confirm your position in writing before you sign.

How do I check that a partner can meet Australian data residency requirements?

Ask to see the Terraform that sets the Organization Policy resource locations constraint (constraints/gcp.resourceLocations) to australia-southeast1 (Sydney) and australia-southeast2 (Melbourne). A partner who has done this before will show you the code and explain which services are exempt.

What should I own at the end of a Google Cloud migration?

You should own the Terraform or OpenTofu code, the CI/CD pipelines, the documentation and the runbooks, all in repositories under your control from the first sprint. If a partner deploys through a closed portal or a paid abstraction layer, you cannot change your own environment without them.

How many people and which time zones should a migration partner cover?

Ask for named senior engineers in the contract and confirm that technical leads work Australian business hours during cutover windows. For estates of 50 to 500 workloads, check that platform engineers outnumber project managers on the team.

Should a migration partner require a managed services contract?

Not as a condition of a low migration quote. A migration should leave your own engineers able to run the platform. Managed services can be a sensible separate decision, priced and scoped on their own.

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.

Book a 20-min architecture call

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

Call us Book a call

Quick navigation