What Are the Best Google Workspace Migration Tools? (Quick Answers)
Q: What are the main Google Workspace migration tools?
A: Google offers two free native options: Data Migration Service (DMS) for email, calendars, and contacts, and Google Workspace Migration for Microsoft Exchange (GWMME) for larger Exchange-to-Workspace moves. For Drive files, Google provides the Drive Migration Tool. Third-party tools like CloudM, BitTitan, and ShuttleCloud handle complex multi-platform jobs.
Q: How long does a Google Workspace migration take?
A: A standard small-business migration (5-25 users, single source platform) takes one to three days of elapsed time, with most of the heavy lifting running overnight. Larger jobs with multiple source platforms, Outlook PSTs, or 100GB+ mailboxes can stretch to one or two weeks. The DNS cutover itself takes minutes - everything else is prep and sync.
Q: What’s the most common Google Workspace migration mistake?
A: Cutting over MX records before the email backfill completes. The result: emails that arrive during the gap land in a mailbox you have already abandoned. The fix is simple - finish the delta sync first, verify recent mail is present in Gmail, then change DNS. Pre-migration DNS audits prevent the second most common mistake: stale SPF records that send your first day of Workspace email straight to spam.
The Five Migration Scenarios (And Which Tool Each Calls For)
Most “Google Workspace migration tools” articles list every tool ever made. That is not useful. The actual question is: where are you coming from? Once you answer that, the right tool is usually obvious.
Here are the five scenarios we see week in, week out at itGenius - and what we use for each.
| Source Platform | Recommended Tool | Why |
|---|---|---|
| Microsoft 365 (Exchange Online) | Data Migration Service (DMS) | Native, free, handles email + calendar + contacts |
| Personal Gmail accounts (@gmail.com) | Data Migration Service (DMS) | Same tool, IMAP mode - covers free Gmail with no extra cost |
| Another Google Workspace tenant | DMS (between tenants) or a controlled offboarding flow | Native between Google tenants; the tricky bit is shared drives and calendar ownership |
| cPanel, GoDaddy, Bluehost, legacy IMAP | DMS in IMAP mode | Slow but reliable - the source has no API, so we read mailboxes one by one |
| Drive files only (large archives) | Google Drive Migration Tool or rclone | Files don’t go through DMS - they need a separate path |
If your scenario does not appear in this list, you probably have two scenarios stacked on top of each other (for example: M365 mail plus a SharePoint document library plus a few @gmail.com accounts the founders still use). Each layer gets its own tool. Trying to migrate all three with one tool is where projects fall over.
For a step-by-step walkthrough of the M365 case specifically, see our Microsoft 365 to Google Workspace migration guide.
Google’s Native Migration Tools (Free, Usually Enough)
Data Migration Service (DMS)
DMS is the workhorse. It lives in the Google Admin console under Account → Data Migration and it covers email, calendars, and contacts from most source platforms - Exchange (M365 or on-prem), other Google Workspace tenants, free @gmail.com accounts, and any IMAP server.
What DMS is good at:
- Running in the background while users keep working on the old system
- Migrating historical email back to a chosen date (or all of it)
- Re-running deltas after the initial sync to catch new mail
- Handling 50 to a few hundred users without falling over
What DMS is not good at:
- Drive files - it does not touch them
- Shared mailboxes with complex permissions - it migrates the data but not the share rules
- PST archive files - these need to be imported to M365 first, then migrated, or handled separately
- Very large mailboxes (50GB+) - it works, but plan for slow throughput and overnight runs
Google Workspace Migration for Microsoft Exchange (GWMME)
GWMME is the older Windows-based desktop tool for Exchange migrations. Google has effectively replaced it with DMS for most use cases, but it is still around for legacy Exchange Server (on-premise) jobs where the source is not in M365. If you are migrating from Exchange Online, use DMS - GWMME adds complexity with no benefit.
Drive Migration Tools
Files are a separate problem. Google offers a Drive-specific migration path that handles ownership, sharing permissions, and folder structure when moving files from one Workspace tenant to another. For one-way archive moves from non-Google sources (OneDrive, Dropbox, Box, local file shares) the practical tools are:
- Drive for Desktop (formerly File Stream) - mount Drive locally, drag and drop, accept that you lose granular permission history
- rclone - command-line tool with full sync, retry, and verification, ideal for engineers comfortable with terminals
- Third-party migration tools (see below) - paid, but they preserve sharing and ownership
For a detailed walkthrough of moving Drive files between Workspace tenants, see our Google Drive files migration service page.
Third-Party Migration Tools (When They Are Worth It)
If your migration involves any of these complications, paid third-party tools usually save more time than they cost:
- Multi-platform sources (M365 + Dropbox + personal Gmail in one project)
- Strict preservation of shared drive permissions and external sharing rules
- Audit trail and reporting requirements (regulated industries)
- Calendar ownership transfer at scale
- More than 200 users with high mailbox sizes
The well-known players:
| Tool | Best For | Notes |
|---|---|---|
| CloudM Migrate | Large multi-platform jobs, regulated industries | Strong audit logging, scales to thousands of users |
| BitTitan MigrationWiz | Mid-market, Drive permission preservation | Per-user pricing, mature platform |
| ShuttleCloud | Smaller Drive-heavy jobs | Used to power some Google-native migration paths |
| Quest On Demand Migration | Enterprise, hybrid identity | Heavier weight, more setup |
The honest take: for a 25-user small business moving from M365 with standard mail and a clean Drive, you do not need any of these. DMS plus the Drive Migration Tool plus an afternoon of planning covers it. Reach for paid tools when scale or compliance forces your hand.
The Step Most People Skip: Pre-Migration Prep
Migration tools get all the attention. The reason migrations fail is almost never the tool - it is the prep. Three things to do before you open the migration console.
1. Inventory Everything
Build a single document that lists:
- Every active mailbox (and which are shared mailboxes, distribution lists, or aliases)
- Every shared folder, document library, or shared drive
- Every domain (primary, aliases, secondaries, dead ones still receiving mail)
- Every external integration (Mailchimp, e-signature tools, CRM connectors) that sends mail or reads from the mailbox
If the inventory takes longer than the migration itself, you are doing it right.
2. Audit Your DNS Before You Touch MX Records
DNS misconfigurations are the silent killer. Your first day on Google Workspace, your team sends 500 emails - and 200 of them land in spam because the SPF record still references the old mail host. Run a full check on SPF, DKIM, DMARC, and any third-party sending services before the migration weekend, not after.
If this is uncharted territory, our DNS Fix QuickFix handles it as a fixed-price service - we do the audit, fix the records, and verify deliverability in the first 48 hours on the new host.
3. Tell Your Team What Is About to Happen
The single biggest source of post-migration support tickets is users who did not know the cutover happened. They open Outlook on Monday morning, see no new mail, and assume the system is broken. A two-paragraph email three days before the migration weekend, plus a 30-minute team session walking through Gmail, Calendar, and Drive, eliminates 80% of support volume in the first week.
What Goes Wrong (And How To Avoid It)
After running hundreds of migrations, the same handful of issues come up over and over.
Lost Email During the Delta Sync Window
The classic failure: you finished the initial sync on Friday, cut MX on Sunday night, and on Monday users find Saturday and Sunday emails missing. The cause is almost always that the delta sync was not re-run between the last sync and the cutover, or it was re-run but not verified.
The fix: run one final delta sync within 30 minutes of the MX change, then spot-check three or four users for recent mail before declaring done.
Calendar Events Owned by the Wrong Person
Recurring meetings created by a colleague who left the company become orphans during migration. They migrate, but you cannot edit them. The fix is to identify orphaned recurring events before the migration and have the new owner re-create them, or use the calendar permissions transfer feature in DMS.
Shared Drive Permissions Quietly Resetting
Shared drives migrate the files cleanly but the permissions on the new tenant are not always identical to the old. After the cutover, audit at least one folder per shared drive and confirm the right people have the right access.
Stale Domain Aliases Still Routing Mail
Old domain aliases that nobody uses but were still receiving mail will keep routing to the old MX until they are removed at the registrar. Audit your domain list at the registrar before the cutover, not after the first support ticket.
For complex multi-tenant migrations - which is when these issues compound - our Google Workspace to Google Workspace migration service handles the cutover end to end.
Key Takeaways
- The right tool depends on the source platform - DMS handles M365, IMAP, free Gmail, and most Workspace-to-Workspace jobs for free
- Third-party tools (CloudM, BitTitan) earn their cost on multi-platform jobs, regulated industries, or 200+ user moves
- Drive files migrate separately from email - plan a distinct path for them
- The biggest migration risk is not the tool, it is skipping the DNS audit and team comms before the cutover
- Run one final delta sync within 30 minutes of the MX cutover and verify recent mail before walking away
Get the Migration Done Right the First Time
A Google Workspace migration is a project, not a quick task. Done well, your team logs in Monday morning and finds everything where they expect it - including last week’s emails and last year’s archive. Done poorly, you spend the next month firefighting missing mail, broken calendar invites, and “why is everything different” tickets.
itGenius has run thousands of Workspace migrations across every source platform - Microsoft 365, legacy Exchange, cPanel, personal Gmail consolidations, and tenant-to-tenant moves. We handle the prep, the tool selection, the cutover weekend, and the first-week support so your team does not feel a hiccup.
See our Google Workspace Migration service →
Or, if you have a specific scenario in mind, the relevant fixed-price options:
- Microsoft 365 to Google Workspace Migration
- Free Gmail to Google Workspace Migration
- Google Workspace to Google Workspace Migration
- cPanel to Google Workspace Migration
