'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Migrate Google Workspace Mailboxes Larger Than 200 GB to Microsoft 365
Question details
Organizations need a reliable method to migrate Google Workspace mailboxes larger than 200 GB to Microsoft 365 Exchange Online without exceeding the standard 100 GB limit or risking data loss.
- Product
- Microsoft 365 Exchange Online
- Device & OS
- not provided
- Scenario
- Migrating massive enterprise email accounts from Google Workspace to Microsoft 365.
- Observed behavior
- Standard Microsoft 365 mailboxes cap at 100 GB, and manually exporting oversized mailboxes to very large PST files significantly increases the risk of data corruption and migration failure.
Ensure you have Microsoft 365 Global Administrator permissions, access to the Exchange Online PowerShell module, and have reviewed Microsoft's latest prerequisites for large mailbox migrations.
Use Microsoft 365 Large Archive Onboarding (LAO)
Leverage Large Archive Onboarding via PowerShell to automatically expand archives for mailboxes exceeding 100 GB during migration.
Standard Exchange Online mailboxes have a strict 100 GB capacity limit. To accommodate mailboxes up to or exceeding 200 GB, administrators must use Large Archive Onboarding (LAO). This feature seamlessly routes data into auto-expanding archives during the IMAP or Google Workspace migration, eliminating the need to rely on error-prone PST files.
Open PowerShell as an administrator and connect to the Exchange Online module using your Microsoft 365 global admin credentials.
Set up the Google Workspace migration endpoint in the Microsoft 365 Exchange Admin Center or via PowerShell, ensuring the connection is verified.
Execute the required PowerShell commands for LAO to enable auto-expanding archives for the target Microsoft 365 users before the migration begins.
Initiate the automated migration batch and monitor the synchronization status directly through the Exchange Admin Center.
Thoroughly test and validate the migrated emails and archive folders in Microsoft 365 before decommissioning or removing the source Google Workspace mailboxes.
Avoid Oversized PST Exports
Understand why traditional PST exports fail for massive mailboxes and implement proper data splitting if manual migration is unavoidable.
Equip Your Team with WPS Office During Your Workspace Transition
While you navigate complex administrative tasks like 200 GB email migrations, ensure your users stay productive. WPS Office is a powerful, lightweight, and free alternative to Microsoft Office that offers a familiar interface and seamless compatibility with all major document formats.
- 1. Download the installer: Visit the official WPS Office website and download the free installation package for your operating system.
- 2. Install the suite: Run the installer and follow the quick setup wizard to install WPS Office on your device.
- 3. Open your files: Launch WPS Office and instantly open your existing Word, Excel, and PowerPoint documents without losing any formatting.
Frequently Asked Questions
What is the maximum primary mailbox size in Microsoft 365?
For most enterprise plans (like E3 and E5), the primary mailbox size limit is 100 GB. Any data exceeding this must be routed to the user's online archive, which supports auto-expansion up to 1.5 TB.
Why shouldn't I migrate 200 GB using PST files?
PST files are inherently unstable at very large sizes. Microsoft recommends keeping PST files under 50 GB. Exceeding this limit dramatically increases the risk of file corruption, resulting in permanent data loss and failed migrations.
Can I enable Large Archive Onboarding (LAO) from the graphic interface?
Currently, managing Large Archive Onboarding for automated migrations of massive IMAP or Google Workspace mailboxes is primarily supported and configured via Exchange Online PowerShell.
Will users notice any downtime during the LAO migration?
If properly configured in a migration batch, users can continue working in their Google Workspace accounts while data syncs in the background. The final cutover simply switches the mail routing.
