Skip to main content
Suitebriar(888) 545-3685Talk to a Google expert
A technician working on a laptop in a data center aisle

Cloud infrastructure
and migration.Plan, compare, build and move, then put Google Cloud to work.

Decide what moves and what it would cost, compare it with AWS or Azure, build a landing zone and move servers and databases with Google's own tools, then put your data to work in Looker or start from a ready-made solution pack.

Talk to a Google Cloud expertStart with a migration plan

Trusted by teams at

  • Reddit
  • Cloudflare
  • Okta
  • Zapier
  • Dialpad
  • Prezi
  • Century 21 Canada
  • Berkshire Hathaway HomeServices Homesale Realty

Where should a move to Google Cloud start?

With a plan: an inventory of what you run today, what depends on what, and what it would cost on Google Cloud. The landing zone and the moves follow from it.

Google splits a migration into four phases: assess, plan, deploy and optimize. Planning covers the first two, with Google's Migration Center doing the discovery and producing total cost of ownership reports. Then the landing zone is built, before the first workload arrives: the organization, folders, projects, access controls and network your workloads will run in. Google's tools move the VMs and databases, and resources are tuned for cost and performance once they run.

Two colleagues planning with sticky notes on a glass wall in a bright office

Plan, compare, build and move, then use

Six services along one path, from deciding what moves to putting Google Cloud to work.

Plan: decide what moves

An inventory of your workloads and what depends on what, a cost of ownership business case and an approach for each workload, with an architecture measured against Google's Well-Architected Framework.

Compare: see the cost

Comparable services on AWS, Azure and Google Cloud side by side. Migration Center prices your own workloads on Google Cloud; your current bills are the other side.

Build and move

A landing zone first, kept as Terraform code. Then VMs from VMware, AWS or Azure and MySQL, PostgreSQL, SQL Server or Oracle databases, moved with Google's own tools.

Use: put it to work

Looker models with each metric defined once and dashboards on BigQuery, or a ready-made solution pack for web apps, online stores, analytics, logs or scanned documents.

How West Liberty Foods built a cloud adoption roadmap

Suitebriar spoke with each team at West Liberty Foods, documented their business processes and the software behind them, and identified 150 process improvements, now a prioritized list West Liberty is working through.

Read the story
150process improvements identified in the roadmap
20 hoursa month saved in accounting, with production reports in Google Sheets that update automatically
“Since this experience, we’ve started a Cloud-first mentality. We’re not going to have platforms on-prem. We’re not going to spin up new projects in-house, in our data center. We’re going to spin up projects in Google Workspace or in Google Compute Engine.”
Joshua WoldDirector of IT, West Liberty Foods

From plan to production

  1. PlanAn inventory, the dependencies and a cost of ownership business case, then an approach and a place in the order for each workload.
  2. CompareComparable services on each cloud, and your own workloads priced on Google Cloud next to your current bills.
  3. Build the landing zoneResource hierarchy, IAM, network, billing and logging in place before the first workload arrives.
  4. Move, then useWorkloads move in batches with Google's tools and are tuned once they run; then data goes to work in BigQuery and Looker.
Two colleagues working together at laptops in a meeting room

Cloud infrastructure & migration FAQ

What IT leads ask before deciding where to begin.

Not sure where to start?

Tell us what you run today and where, and we'll point you to the right first step.

(888) 545-3685Talk to a Google Cloud expert
We're not sure what should move. Where do we start?

With a migration plan. It inventories what you run, maps what depends on what and prices it on Google Cloud, so whether each workload moves, and how, is decided before anything moves.

Do we have to move everything at once?

No. Workloads are grouped into batches and moved in order, with the first movers chosen so your team builds experience. Migrate to Virtual Machines keeps each source VM running until a short cut-over.

Where do Looker and the solution packs fit?

On top of the landing zone, once there's something to run. Looker's SQL runs in BigQuery, where your data lands, and each solution pack is a starting design that's sized for your workload before anything is built.

Talk through your move to Google Cloud

Tell us what you run today, where it runs, and what you'd like Google Cloud to do for you.

  • Google Cloud Premier Partner, working only on Google Cloud and Workspace for more than a decade
  • U.S.-based support team

Free AI starter kit

From your data to your first AI agents, in four steps

Google's AI starter kit for lean teams: your four-step guide from data to agents.

  • Four steps, from a first no-code win to a multi-step agent workflow
  • Use cases with sample prompts, plus the ABCD prompting technique
  • Best practices for data quality, governance and human oversight