For a G Suite to Office 365 migration, the main tool is the Google Workspace (Gmail) migration batch in the Exchange admin center. It moves mail, rules, calendars and contacts. Google Drive files need a second tool, Migration Manager, and IMAP is a mail-only fallback that Microsoft documents mainly for consumer Gmail.
This guide compares the options by what each one moves, what it skips and what you must prepare first. It does not repeat the full procedure. For that, use the G Suite to Office 365 migration pillar guide.
Who this is for and what you will have at the end
This is for IT staff and owners who are choosing a method before they start. You should know your user count, roughly how much data is in Gmail and Drive, and whether you need calendars and contacts to arrive.
At the end you will have a decision for each data type: mail, calendar, contacts, rules, Drive files and anything the native tools skip. You will also have a short list of limits to check against your own data. If you are earlier in the process, read the migration checklist first.
The tools at a glance
Microsoft's Exchange documentation lists three ways to migrate Google Workspace mail: automated through the Exchange admin center (EAC), manual through the EAC, and Exchange Online PowerShell. Alongside these, you have the IMAP route, Migration Manager for Drive, a PST import for small groups, and third-party tools.
| Tool | Moves | Does not move | Best fit |
|---|---|---|---|
| Automated EAC batch (Google Workspace migration) | Mail, Calendar, Contacts, Rules | Vacation and automatic reply settings, room bookings, shared calendars, event colors, Gmail tags | Most organizations with more than a handful of users |
| Manual EAC batch | The same data types | The same exclusions | When you prefer the manual method Microsoft still offers |
| Exchange Online PowerShell batch | Same data types; supports -ExcludeFolder and -SkipRules | The same exclusions | Admins who want to script batches and exclude folders or labels |
| IMAP migration | Email only | Calendar and contacts | Consumer Gmail mailboxes, or when you accept mail-only |
| Migration Manager | Google Drive files, metadata and permissions | Mail, calendar, contacts | Drive content, in addition to the mail tool |
| PST import (Outlook) | What users export into the file | Anything not exported | Very small businesses with a few users |
| Third-party tools | Vendor-defined | Vendor-defined | Cases the native tools do not cover |
The next sections cover each in more detail. Every statement about Microsoft tools comes from the Microsoft Learn pages listed in References.
The automated Exchange admin center batch
Microsoft says the batch migration tool in the Exchange admin center can transfer your organization's mail, rules, calendars and contacts from Google Workspace to Microsoft 365, and that it recommends the automated method because it completes several required tasks in your Google admin console for you.
What you prepare first
Microsoft lists four prerequisite steps before an automated migration:
- Create a subdomain in Google Workspace to route mail to Microsoft 365.
- Create a subdomain to route mail to Google Workspace.
- Provision mail users to migrate from Google Workspace to Microsoft 365.
- Verify Google migration administrator role assignments.
The Microsoft 365 admin center page adds that the Exchange administrator must have at least the Recipient Management role group, and that the Google account creating the Google Cloud project and service account needs the Project creator and Service Account Creator roles. A Google Workspace super administrator must authorize domain-wide delegation separately. Microsoft warns that if you skip the prerequisites, the migration will not be successful.
How the batch is started
In the Exchange admin center you go to Migration, select Add migration batch, keep Migration to Exchange Online, and choose Google Workspace (Gmail) migration as the migration type. On the Prerequisites for Google Workspace migration page, the Automate the configuration of your Google Workspace for migration section has a Start button that automates four required prerequisite steps. A JSON file is downloaded, and you copy a ClientID and Scope into Google's API controls.
You then set a migration endpoint. For a new endpoint the page shows Maximum concurrent migrations at a default of 20 and Maximum concurrent incremental syncs at a default of 10. The user list is a CSV file with an EmailAddress header (required) and an optional Username header for the Gmail address if it differs.
EmailAddress,Username
[email protected],[email protected]
[email protected],[email protected]On the Move configuration page you choose the target delivery domain, which is the subdomain you created, and the migration filtering options: Mail, Calendar, Contacts and Rules. That filter is how you decide per batch what the tool moves. When the batch shows Synced, you complete it. After batch start, assign Exchange licenses within 30 days.
Limits to check
| Item | Documented behavior |
|---|---|
| Message size | Default limit of 35 MB per message, configurable up to 150 MB |
| Contacts | A maximum of three email addresses per contact are migrated |
| Calendar and contact throughput | Depends on the quota restrictions of the Google Workspace service account |
| Rules | Migrated but turned off by default; verify in Outlook before enabling |
| Large mailboxes | Microsoft points to a separate large-mailbox path for Google mailboxes over 100 GB |
| Government clouds | Not available for Office 365 US Government GCC High or DoD |
Microsoft also strongly recommends disabling messaging records management (MRM) and archival policies before migrating. Its migration tool is unaware of them, so items they delete or archive are flagged as "missing", which looks like data loss and makes real data loss harder to spot.
The manual EAC batch and PowerShell
Microsoft notes that the EAC continues to offer manual migration, and that the PowerShell method is a third option. They move the same data types, so the choice is about control, not coverage.
PowerShell has two options that matter for planning. The -ExcludeFolder parameter of New-MigrationBatch lets you leave out folders by name, and Gmail labels that apply to many messages, to reduce the size of the new mailbox. The -SkipRules parameter stops rules from migrating. Microsoft's page describes these on the Google Workspace migration page and refers to the New-MigrationBatch reference for details. Read that reference before you script anything.
If you only need to leave out Gmail filters or a noisy label, PowerShell is therefore the tool with the finer controls. For everything else the automated EAC wizard is the shorter path.
IMAP migration
An IMAP migration also runs from the Exchange admin center, using an IMAP migration endpoint and an IMAP migration batch. Microsoft's IMAP page states plainly that it migrates emails only, not calendar and contact information, and that users can import their own calendar and contacts to Outlook afterward.
Its other constraints are practical ones:
- Every account owner must create an app password, because Google treats Outlook as a less secure app, and your Google Workspace users must be able to turn on 2-step verification.
- The migration file has
EmailAddress,UserNameandPasswordcolumns, and can include up to 50,000 mailboxes with a file size up to 10 MB. - You must be a global admin in Microsoft 365 to complete the IMAP steps.
- Microsoft says large mailboxes can show Syncing for a long time because of Google bandwidth and sync limits, and suggests alternative methods.
The page opens with a note that it explains how to migrate consumer Gmail mailboxes, and that organizations wanting calendar and contacts too should use the Google Workspace migration. For a business tenant, treat IMAP as the fallback, not the first choice.
Migration Manager for Google Drive
Mail tools do not touch Drive. Microsoft's Migration Manager migrates Google Workspace files, metadata and permissions to OneDrive and SharePoint. A standard workflow has six steps: connect to Google, scan and assess, copy to the migrations list, review destination paths, map identities and migrate and monitor.
Two details help you choose:
- Migration Manager Lite is a simplified version for small and medium businesses. Microsoft says it is enabled by default for tenants with fewer than 300 Microsoft 365 licenses when the project is created, and it presents only the connect and migrate stages as separate steps.
- Identity mapping alone does not turn on file-level permission migration. Microsoft says file-level permissions and older file versions require explicit migration settings.
The page also notes file size limitations and unsupported files, and says to use migration reports to find content that needs a separate method. For the full walkthrough, see Migrate Google Drive to OneDrive and SharePoint with Migration Manager.
To open it from the Microsoft 365 admin center, Microsoft's page says to go to Setup > Migration resources, select Explore migration & imports tools under Self-service migration and import tools, and then select Google Workspace.
PST import and very small businesses
Microsoft's small business guidance says that if you are a very small business with a few users, you should migrate email using a different method, such as importing to Outlook through a PST file. The Exchange overview makes the same point: if you need to migrate a small number of users, you can move them all at once using a PST file.
A PST import is only as complete as the export. It carries whatever each user exports, so check that mail, calendar and contacts were all included, and keep in mind that it needs hands-on time at each computer.
Third-party tools
Third-party tools exist for this migration, and Microsoft's migration best-practices page acknowledges them: it says third-party tools are mostly used in scenarios that do not involve Exchange, such as migrations from Gmail, G Suite or Google Workspace, IBM Lotus Domino and Novell GroupWise. It also says that for data consistency or integrity issues after a migration with a third-party tool, you should contact the vendor for support.
This article does not rank third-party products. The one vendor page checked, BitTitan's MigrationWiz page, says only that it supports a wide range of platforms including Microsoft 365 and Google Workspace. It lists no per-item details or prices for the Gmail to Microsoft 365 path, so those would have to come from the vendor's own documentation and quote.
Questions to ask any vendor before you buy:
- Which of Mail, Calendar, Contacts, Rules and Drive does it move, and which does it skip?
- How does it connect to Google, and what permissions does it need?
- How does it handle throttling and large mailboxes?
- What happens to items already migrated when you run a delta pass?
- Who supports you if data is inconsistent?
Which tool for which job
| Your situation | Suggested path |
|---|---|
| Many users, need mail, calendar, contacts | Automated EAC batch, in pilot and then production batches |
| Need to leave out folders or labels, or script batches | Exchange Online PowerShell batch |
| Mail only, consumer-style Gmail accounts | IMAP migration |
| Drive and shared drives | Migration Manager, alongside the mail tool |
| A handful of users | PST import |
| Anything the native tools skip | Evaluate a vendor, using the questions above |
Whichever method you pick, plan what the native tools do not carry across. Vacation and automatic reply settings, room bookings, shared calendars and event colors are not migrated by the batch tool, so list them and rebuild them by hand. For planning the effort and timeline of that rework, see the migration cost and timeline guide.
Verification and troubleshooting
After a batch, ask pilot users to check mail, calendar and contacts, and compare folder counts for a sample mailbox. Items flagged as "missing" are the first thing to rule out as MRM or archival policy effects before assuming data loss.
| Symptom | What Microsoft's pages indicate |
|---|---|
| Migration fails to start or authorize | Check that all four prerequisite steps are complete and the Google roles are in place |
| Batch stays at Syncing for a long time | Google bandwidth and sync limits can slow large mailboxes; consider another method |
| Items reported missing | MRM or archival policies can delete or move items; disable them before migrating |
| Message did not migrate | Check the 35 MB default size limit |
| Rules not working after migration | Rules arrive turned off; review them in Outlook first |
Closing checklist
- Decide per data type: mail, calendar, contacts, rules, Drive, and the unsupported items.
- Confirm your tenant is not GCC High or DoD, where Google Workspace migration is unavailable.
- Complete the four prerequisite steps before creating a batch.
- Disable MRM and archival policies before migrating.
- Run a small pilot batch and compare results before the main batches.
- Assign Exchange licenses within 30 days of batch start.
- Plan Drive with Migration Manager and the manual rebuild of skipped settings.
What we checked
- Opened "Perform an automated Google Workspace migration to Microsoft 365 or Office 365 in EAC" on learn.microsoft.com on 2026-11-18 (page updated 2026-07-28 per its metadata). Confirmed the EAC labels used here, the default 20 and 10 endpoint values, the CSV headers and the Mail, Calendar, Contacts and Rules filters.
- Opened the Google Workspace automated batch mail migration overview on 2026-11-18 and cross-checked its limitations table (35 MB default message size, three email addresses per contact, not-migrated items) against the "Perform a Google Workspace migration" page; both agree.
- Opened the IMAP page for Gmail on 2026-11-18 and confirmed that it migrates email only, requires app passwords, allows up to 50,000 mailboxes per file and is written for consumer Gmail.
- Opened the Migration Manager Google overview on 2026-11-18 and confirmed Migration Manager Lite is enabled by default for tenants with fewer than 300 licenses.
- Opened the Microsoft 365 admin center page "Migrate business email and calendar from Google Workspace" on 2026-11-18 and confirmed the Recipient Management role requirement and the 30-day licensing window.
- Opened the BitTitan MigrationWiz page on 2026-11-18. It states no Gmail-path item details or prices, so none are given here.
- Not checked: no live tenant or Google Workspace domain was used, and the other third-party vendors were not reviewed. Steps follow Microsoft's documentation as of 2026-11-18.
Last tested: 2026-11-18
References
- Perform a Google Workspace migration to Microsoft 365 or Office 365
- Perform an automated Google Workspace migration in EAC
- Google Workspace automated batch mail migration overview
- Migrate business email and calendar from Google Workspace
- Migrate Google Workspace mailboxes with IMAP
- Overview: Migrate Google Workspace to Microsoft 365 with Migration Manager
- Migration performance and best practices (third-party tools section)
- BitTitan MigrationWiz
Comments
Questions and tips are welcome. Comments are checked by the EpiFive team before they appear; please do not share passwords, phone numbers or other private details.