Migrating to Google Workspace: The Complete 2026 Guide for Every Source and Size

Migrating to Google Workspace comes down to two questions: what are you moving from, and how big is your organization. Google publishes a table on its own admin documentation that answers exactly that, naming the right tool for every combination, and this guide puts it in front of you, then walks each path.

Almost everything you will find when you search for this is written by someone with something to sell you: Google sells Workspace, migration vendors sell tools, consultants sell hours. This page sells none of those, so it can tell you what they cannot: for most small and mid-sized companies, Google's free built-in tools are enough, and this guide says exactly when that stops being true. If you are starting fresh rather than migrating, setting up a business Gmail account is the shorter road.

Which migration path is right for you?

Google's own answer to "how do I migrate" is a table on its admin documentation, last updated July 22, 2026, that names the right tool for every combination of source system and company size. Here it is, with every cell taken from Google's page.

Google documents a cap on the built-in path for Microsoft: "You can import data for up to 1,000 Exchange Online users at a time."

Read your row, and the rest of this guide walks your path. Two things Google's table implies but does not say: the size bands matter because the tools genuinely differ in setup weight, not because bigger companies need to spend money, and the busiest cell by far, small organizations leaving Outlook or another provider, is served by tools built into the Admin console at no cost.

Migrating from Outlook or Microsoft 365

This is the most-traveled path, and for organizations up to a few hundred users it is genuinely a built-in feature: Google's data import handles Exchange Online mail, and Google documents a default cap of importing 1,000 users at a time, which tells you where the comfortable limit sits. Larger Microsoft estates move up Google's table to Google Workspace Migrate, which is a heavier, admin-installed product for a reason.

The step-by-step, from prerequisites through DNS cutover, lives in our dedicated guide to migrating from Outlook to Gmail, which covers the path this section routes.

Migrating from IMAP and other email providers

If your current email lives anywhere that speaks IMAP, a hosting provider's mail, an older suite, most anything with an inbox, Google's data import connects to it directly: point it at the server, authenticate the accounts, and it pulls mail across. The practical prerequisites are unglamorous and decisive: know your current server's address, make sure IMAP access is enabled on the source, and migrate before you cancel the old service, not after, because the tool needs a live source to pull from.

Migrating from a personal Gmail account

Moving from a personal Gmail into Workspace is the path Google makes gentlest, and the one where the word "migration" oversells the job: for one account, Google's Mail Importer and takeout tooling move mail and contacts, and for merging or moving between personal accounts the dedicated guides on migrating Gmail to Gmail and merging Google accounts cover the variants. One warning this page used to get wrong: setting up forwarding is not a migration, it is a redirect, and the old mail stays where it was.

Migrating from another Google Workspace

This is the least-explained migration on the internet, and the searchers looking for it get vendor listings and guesswork. Google's own documentation actually covers it, and the distinction that decides everything is one Google draws but never explains in plain terms: Domain Transfer moves an entire domain from one Workspace organization to another, users, domain and all, while data import moves mailbox contents between organizations that each keep their own domains.

So the question is whether the domain itself is moving. Company acquired, domain coming along: Domain Transfer. Consolidating two organizations that keep separate identities, or moving people between tenants: data import, mailbox by mailbox. Both paths are Google's own tooling, both are on Google's table, and neither requires the third-party migration tools that dominate this search.

What the migration actually looks like, step by step

Whatever your source, every migration to Google Workspace runs the same arc, and knowing it in advance is most of the calm. Here it is end to end; the tool from your row of the table above does the heavy lifting at step four.

1. Sign up and verify your domain. Workspace setup walks you through proving you own yourcompany.com, usually by adding one DNS record at your domain registrar. Nothing about your existing email changes yet.

2. Create your users. Every person gets their Workspace account before any mail moves, because the import needs a destination mailbox per person. For a handful of people this is manual; larger organizations upload a list.

3. Prepare the source. This is the step that varies by path: enable IMAP access, set up the Exchange connection, or grant the migration tool its permissions on the old system, per your row above. The one universal rule: do not cancel the old service yet, the tools need a live source to pull from.

4. Run the import. Point the tool at the source, map old accounts to new ones, and let it run. Mail transfers in the background over hours or days depending on volume, and people keep working in the old system while it does.

5. Switch your DNS. This is the actual cutover: updating your domain's MX records so new mail arrives in Workspace instead of the old system. From this moment, Gmail is live for your domain. Most teams do it at the end of a working week.

6. Run a final delta and verify. Import whatever arrived at the old system between the first run and the cutover, then check both directions: send in, send out, confirm delivery, and keep the old service alive in parallel until you have watched one full business day arrive cleanly.

7. Retire the old system. Only after the parallel day, and after anything beyond mail, calendars, contacts, files, has been confirmed across. The first-week checklist below picks up from here.

None of this requires anything beyond the tools in Google's table for most organizations; the steps are the same whether the import runs from Google's built-in tools or a specialist's platform, which is exactly why the do-it-yourself question below is about complexity, not about the arc.

Should you do it yourself or hire help?

Here is the assessment none of the tool vendors, hosts, or consultants writing about this can give you, because every one of them sells a tool, hosting, or consulting hours: most migrations under a hundred users need nothing beyond Google's free built-in tooling and a careful weekend. Google's table above is the proof; the busiest cells all name free products.

The honest line where that stops: complexity, more than headcount. Shared drives and Vault data moving between tenants, Exchange estates past the built-in caps, compliance requirements with no tolerance for a missed message, or simply nobody internal with admin hours to spend. Past that line, specialists and migration platforms earn their fees, and the right way to buy is to name your source, size, and the data types beyond mail, then make them quote against Google's own table so you are paying for the part Google's tooling genuinely does not cover.

After the migration: the first week

Migration guides end at the cutover; the first week is where the move pays off or leaks. Three things worth doing before the old system is a memory: verify mail flow both ways and let the old service run in parallel until you have seen a full business day of clean delivery; set up the shared addresses properly, because support@ and sales@ are why most teams moved, and Google Workspace's shared mailbox options plus the wider Gmail shared inbox approaches are a deliberate choice, not a default; and only then retire the old service.

How this guide is verified

Every routing cell in the table above comes from Google's own migration product matrix on its admin documentation at knowledge.workspace.google.com, last updated July 22, 2026, with the IMAP row from Google's companion getting-started table, and the Exchange import cap from Google's own documentation. No migration vendor, consultant, or aggregator source is used anywhere on this page.

One rumor is worth naming because it circulates in search summaries: that Google Workspace Migrate for Exchange Online is being retired in October 2026. As of this page's verification date, July 28, 2026, no Google page states it, and five of Google's own documentation pages were read directly to check. If Google announces it, this page will carry the announcement with its date; until then, treat the claim as unsourced. This guide is re-verified when Google updates the matrix, with changes recorded rather than silently overwritten.

You migrated for a reason. Set it up right.

Most teams do not move to Google Workspace for the storage. They move because the work lives in email, the old system fought them, and support@ or sales@ deserves better than a forwarding rule.

That job has a tool. Drag turns the Gmail you just migrated to into your team's shared inbox: shared addresses become boards, emails carry assignments, internal notes, and tasks, and everyone can finally see who is handling what. It is the difference between landing in Workspace and actually working there.

Start free trial · Book a demo

7-day trial, no card required, from $12 per user per month.

Google Workspace migration FAQs

Can I migrate to Google Workspace for free?

For most organizations up to 100 users, yes: Google's built-in data import tools cover Outlook, IMAP providers, and Gmail sources at no cost, per Google's own documentation. Costs appear with scale and complexity, not with the migration itself.

How do I migrate from one Google Workspace account to another?

With Google's own tooling, despite what the vendor-dominated search results imply: Domain Transfer if the domain itself is moving between organizations, data import if you are moving mailbox contents between organizations keeping separate domains.

What is the best tool to migrate from Outlook to Google Workspace?

Google's own data import, built into the Admin console, for organizations up to the documented 1,000-users-at-a-time cap; Google Workspace Migrate for large Exchange estates. Third-party tools earn their place mainly on data types beyond mail, like complex permissions or archives.

How long does a Google Workspace migration take?

Small migrations commonly complete over a weekend: the mail transfer runs unattended, and the human time goes to DNS cutover and verification. Large estates run staged over weeks, which is exactly the point at which the do-it-yourself question in this guide changes its answer.