Microsoft's migration tools, and what they leave behind
Gmail, contacts and calendars move with the Google Workspace migration in the Exchange admin center. It is automated, but its prerequisites are mandatory, so plan time to set them up first.
Google Drive moves with Microsoft's Migration Manager, which has Google Drive built in as a source. Mover, the older tool, is retired.
Neither tool moves Gemini chats or Gems. Gems export with Google Takeout and are rebuilt as Copilot agents; Gemini conversations can be exported with Google Vault and archived.
Source: Microsoft Learn: Google Workspace migration in the Exchange admin center
- Gmail, contacts, calendarsExchange admin center: Google Workspace migration
- Google DriveMigration Manager, into SharePoint and OneDrive
- GemsGoogle Takeout, then rebuilt as Copilot agents
- Gemini chatsGoogle Vault or Takeout export, archived in SharePoint
- NotebookLMWorkspace data export, then Copilot Notebooks or SharePoint
What moves where
Every part of Google Workspace has a home in Microsoft 365. This is where each one lands and how it gets there.
| In Google Workspace | In Microsoft 365 | How it moves |
|---|---|---|
| Gmail | Exchange Online and Outlook | Exchange admin center Google Workspace migration |
| Google Calendar | Outlook calendar | Same Exchange migration |
| Google Contacts | Outlook contacts | Same Exchange migration |
| Google Drive and shared drives | OneDrive and SharePoint | Migration Manager, with sharing reviewed and mapped |
| Gemini in Workspace | Microsoft Copilot in Word, Excel, PowerPoint, Outlook and Teams | Licensing plan, then training |
| Gems | Copilot agents | Takeout export, then rebuilt |
| Gemini chat history | Archived in SharePoint | Vault or Takeout export |
| NotebookLM notebooks | Copilot Notebooks or a SharePoint library | Workspace data export |
Gemini's own import of other AI chats isn't available for work accounts, and Copilot has no import button, so the Gemini half is always an export-and-rebuild job.
The order we run it in
1. Inventory and map
Mailboxes, shared drives, sharing, Gems, notebooks and the people who rely on them, each with a destination in Microsoft 365.
2. Prepare Microsoft 365
Licenses, the Exchange migration prerequisites, SharePoint sites and permissions, and Copilot settings, before any data moves.
3. Pilot a small group
Move a few mailboxes and drives first, check mail flow, calendars and file access, and fix what they flag.
4. Move data in batches
Mail, calendars and contacts with the Exchange migration; Drive with Migration Manager; Gemini exports in parallel.
5. Rebuild Gems and train
Gems become Copilot agents next to the moved files; short sessions by role show each task the old way and the new way.
6. Cut over and close down
Switch mail delivery to Microsoft 365, run final syncs, archive Gemini history, and retire Google Workspace licenses at renewal.
What teams worry about, and how we handle it
"Moving off Google is huge."
We plan mail, calendars, Drive and Gemini as one project with one cutover date, using Microsoft's own migration tools for the Workspace data.
"Our sharing will break."
We review Drive sharing, map it to SharePoint and OneDrive permissions, and check it in the pilot. Copilot only shows people what they are allowed to see, so permissions get extra attention.
"People love Gmail and Docs."
Training is by role and built on the tasks people do every day, showing each one the old way next to the new way.
Six steps, nothing lost
Each step has an owner and a sign-off, so nothing quietly breaks along the way.
- AssessWe inventory who uses what: assistants, prompts, files, integrations and spend.
- MapEvery piece gets a home in Microsoft 365, or a reason to retire it.
- RebuildAssistants, connectors and prompt libraries are rebuilt and tested before anyone switches.
- PilotA small group works in the new tool first. We fix what they flag.
- TrainShort sessions built around your team's real tasks, the old way next to the new way.
- Switch overEveryone moves, chat history is archived, and old licenses are retired.
Questions we hear most
What tools does Microsoft provide for Google Workspace migrations?
The Exchange admin center has an automated Google Workspace migration for Gmail, contacts and calendars, and Migration Manager moves Google Drive into OneDrive and SharePoint. Mover has been retired.
Do Microsoft's tools move Gemini?
No. Gemini chats and Gems are exported separately: Gems with Google Takeout, conversations with Google Vault or Takeout. Gems are then rebuilt as Copilot agents.
Do we have to move everyone at once?
No. We pilot with a small group, move the rest in batches, and set one final cutover date.
Can our Gems become Copilot agents?
Yes, by rebuilding them. Each Gem's instructions are rewritten for Copilot and its files move to SharePoint. See our Copilot agent examples.
Does everyone need a paid Copilot license?
No. Copilot Chat comes with Microsoft 365 business plans at no extra cost. We map who needs the paid Microsoft Copilot license.
Is eMazzanti affiliated with Google?
No. eMazzanti Technologies is an independent IT services company and a Microsoft partner, and offers this service with Messaging Architects. Neither is affiliated with or endorsed by Google.
Who does the work
eMazzanti Technologies is an IT services company and Microsoft partner, and runs AI migrations together with Messaging Architects. A few things we have done before:
Microsoft partner
Named Microsoft's SMB Worldwide Partner of the Year, with Modern Work and Azure specializations.
A New Jersey Best Place to Work
Named one of New Jersey's Best Places to Work for 2026 by NJBIZ, based on a confidential survey of our own team.
We teach Copilot
eMazzanti runs Microsoft Copilot Master Classes for business teams. The training step of every migration comes from the same people.
The migration process was flawless, with zero downtime, and their cost-effective solutions have significantly enhanced our operational efficiency.
There's absolutely no hesitancy for me to recommend eMazzanti to anyone.
Keep reading
See your plan before you commit to anything.
The chat at the top builds a migration outline for your team in about two minutes. When you are ready, an eMazzanti migration lead walks through it with you.