Independent guide and affiliate disclosure: we may receive a one-time reward if an eligible reader signs up through our link. We are not Google.
Inventory your Microsoft setup
List each Exchange Online mailbox, calendar, shared mailbox, distribution list, OneDrive account, and SharePoint site that matters. Decide who owns each destination Workspace account and which data needs to remain accessible. Large or complex migrations may require a different Google import method than a small team’s default path.
Match the tool to the data
Google documents a default import method for Exchange Online email, calendars, and contacts. It also lists separate import paths for OneDrive and SharePoint files. Do not assume one email import moves documents or every Microsoft-specific feature. Google says the Exchange Online import copies source data and does not delete it; some features are not supported in Workspace.
Plan the cutover
- Create users and verify your domain in Workspace.
- Read the current prerequisites for the chosen Google import method, including Microsoft administrator access.
- Test a small set of mailboxes and files. Compare important messages, calendar events, contacts, and permissions.
- Schedule the MX-record change, then test incoming and outgoing mail.
- Keep the Microsoft environment available until import results and business workflows are checked.
Common gaps to review
Review shared mailboxes, meeting rooms, mail rules, file permissions, and apps that send mail through Microsoft. Plan equivalent workflows in Google before removing the old service. For regulated or high-volume data, have an administrator review the full migration documentation and retention requirements.
What to do next
Compare the official plan and billing details before you commit. If Workspace fits, check the final price, availability, and terms at Google’s checkout.