To migrate Google Calendar and contacts to Outlook in Microsoft 365, run the automated Google Workspace batch in the Exchange admin center with the Calendar and Contacts filters selected, then rebuild the items Microsoft says it skips: shared calendars, event colors and room bookings. If you moved mail some other way, such as IMAP, each user can export from Google and import into Outlook instead.
This page covers one slice of a G Suite to Office 365 migration: the calendar and contact data. For the full project plan, use the migration checklist, and for the mail side, see migrating email from Google Workspace to Office 365.
Who this is for and what you will have at the end
This is for the admin (or the person acting as one) who has moved or is about to move Gmail and now needs calendars and address books to follow. It also suits individual users who were told to "bring your own calendar" after an IMAP move.
At the end you will know what the batch carries over, what you must rebuild by hand, and how to import calendars and contacts per user when the batch is not an option. You will also have a short post-migration check to run with a pilot user.
What moves and what does not
Microsoft's Google Workspace migration page lists three functions that can be migrated: Mail and Rules, Calendar, and Contacts. It also lists the limitations. The table below restates them.
| Data type | What Microsoft says | What you do about it |
|---|---|---|
| Calendar | Shared calendars and event colors are not migrated | Re-share calendars in Exchange; let users re-apply colors or categories |
| Meeting rooms | Room bookings are not migrated | Create room mailboxes; rebook future meetings |
| Contacts | A maximum of three email addresses per contact are migrated | Check contacts that have more than three addresses |
| Contacts | Gmail tags, contact URLs and custom tags are not migrated | Export a copy first if you rely on labels |
| Vacation and automatic reply settings are not migrated | Users set Automatic replies in Outlook | |
| Rules | Migrated, but turned off by default | Users review each rule, then turn it on |
Two general limits also apply. Throughput for contacts and calendars depends entirely on the quota restrictions of your tenant's service account on the Google side, so a large batch can be slower than the mail portion. And Google Workspace migration is not currently available for Microsoft 365 US Government GCC High or DoD.
Choose your method
| Situation | Method |
|---|---|
| Moving mail, calendar and contacts in stages | Exchange admin center automated Google Workspace batch |
| Mail already moved with IMAP | Per-user export and import (later in this guide), or a batch with only Calendar and Contacts selected |
| A handful of users | Per-user import; Microsoft itself suggests a different method than the batch for very small businesses |
| Only some data wanted | Batch filter options (Mail, Calendar, Contacts, Rules) |
Microsoft's guidance calls the automated batch recommended over the manual batch, and notes that you can instead migrate email through IMAP, so compare methods first. If you are a very small business with a few users, Microsoft suggests a different method, such as importing to Outlook through a PST file.
Prerequisites for the admin batch
The batch needs the same groundwork as a mail migration. Microsoft says that if you skip the prerequisites, the migration will not succeed. In short:
- The admin needs at least the Recipient Management role group in Exchange Online.
- Create a subdomain that routes mail to Microsoft 365, such as
m365.contoso.com, and one that routes mail to Google, such asgsuite.contoso.com. - Provision each person as a mail user, with the External email address set to the Google routing address.
- Allow forwarding in both Google Workspace and Exchange Online.
- The Google account that creates the project needs the Project creator and Service Account Creator roles, and a Google Workspace super administrator authorizes domain-wide delegation.
- Disable messaging records management (MRM) and archival policies on target mailboxes, or items they delete will be flagged as "missing".
The exact steps for these are in the Gmail-only migration guide, so they are not repeated here.
Run the batch with Calendar and Contacts selected
These are the labels in Microsoft's current instructions.
- In the Exchange admin center, go to Migration and select Add migration batch.
- Give the batch a unique name and confirm Migration to Exchange Online under Select the mailbox migration path. Select Next.
- Select Google Workspace (Gmail) migration and select Next.
- On Prerequisites for Google Workspace migration, select Start in the Automate the configuration of your Google Workspace for migration section. Sign in to Google. A
projectid-*.jsonfile downloads and the page shows a ClientID and Scope. - Open the API access link, select Add new on Google's API Clients page, paste the ClientID and Scope, and select Authorize. Then select Next.
- On Set a migration endpoint, create an endpoint. The defaults are 20 for Maximum concurrent migrations and 10 for Maximum concurrent incremental syncs.
- On Gmail migration configuration, enter the Google admin email address and use Import JSON to pick the downloaded key.
- On Add user mailboxes, import a CSV.
EmailAddressis required andUsernameis optional:
EmailAddress
[email protected]
[email protected]- On Move configuration, choose the Target delivery domain. This page also shows the migration filtering options, Mail, Calendar, Contacts and Rules. Microsoft's screenshot shows all four checked by default. Clear Mail if mail is already in Exchange Online and you only want calendars and contacts.
- On Schedule batch migration, set start and end behavior. Microsoft's example sets the end to manual completion. Select Save, then Done.
Think about the Mail filter before you clear it. The documented filter options let you choose which components move, but Microsoft's page does not describe what happens when a batch with only Calendar and Contacts runs against a mailbox that already holds IMAP-migrated mail. Run a pilot with one user and compare before you scale up.
Complete the batch and license users
When the batch status changes from Syncing to Synced, you must complete it. Go to Migration, select the batch, select Complete migration batch, then Confirm in the Details pane. The status then shows Completed.
Microsoft notes two timing rules. All users are converted from mail users to mailboxes when the batch starts, and the Exchange license is assigned only after that point, within 30 days. And during completion another incremental sync copies changes made in Google since the last sync, so a calendar edited an hour ago still arrives.
Rebuild what the batch skips
Rooms and equipment
Because room bookings are not migrated, recreate each room as an Exchange room mailbox. In the Exchange admin center, go to Recipients > Resources and select Add a room resource. On Set up room mailbox, enter a Name and a Resource mail address. Microsoft's PowerShell example is:
New-Mailbox -Name ConfRoom1 -Room -DisplayName "Conference Room 1"On the booking page, repeating meetings are allowed by default, the booking window defaults to 180 days and the maximum duration to 24 hours. Then ask organizers to re-send invitations for future room bookings, since the old bookings did not come across.
Shared calendars
Shared calendars are not migrated, so permissions must be re-granted. Use Add-MailboxFolderPermission with the calendar folder as the identity. Microsoft's example shows a delegate with the Editor role:
Add-MailboxFolderPermission -Identity [email protected]:\Calendar -User [email protected] -AccessRights Editor -SharingPermissionFlags DelegateFor view-only sharing, Microsoft lists the calendar-specific roles AvailabilityOnly (availability only) and LimitedDetails (availability with subject and location). The existing guide to calendar permissions with Exchange Online PowerShell covers the roles in more depth.
Event colors and contact labels
Colors do not move. Outlook uses categories instead, so let users assign categories to recurring series that depended on color. If a team organized contacts with Google labels, export a copy before cutover, since labels, contact URLs and custom tags are on the not-migrated list.
Per-user fallback: export from Google, import into Outlook
Use this after an IMAP migration or when you do not want a batch. Each user does it for their own data.
Calendars
- In Google Calendar on a computer (the Google Calendar app cannot export), click Settings, then Settings, then Import & export on the left. Under "Export", click Export. A .zip file downloads. To export one calendar instead, point to the calendar under "My calendars", click More, then Settings and sharing, then Export calendar.
- Extract the .zip to get one .ics file per calendar.
- In classic Outlook, go to File > Open & Export > Import/Export, choose to import an iCalendar (.ics) file, select Next, browse to the file and select OK, then select Open as New.
Microsoft's page says a file imported this way is a static snapshot that does not update itself, and the imported calendar appears under "Other Calendars" in the Navigation Pane. Google's help page adds that you need the "Make changes and manage sharing" permission on a calendar to export it, and that an organization may restrict exports.
If the calendar should stay in sync for a while, subscribe instead. In Google Calendar, open Settings and sharing for the calendar and copy the Secret address in iCal format link. In new Outlook, select Add calendar below the calendar grid, then Subscribe from web, paste the URL and select Import. Treat that secret link like a password, because anyone who has it can read the calendar.
Contacts
- In Google Contacts on a computer, choose the group to export, select Export, and pick CSV for Outlook only as the format. Microsoft's page names that option; Google's own help page names Google CSV for backups, so confirm which choices your export dialog shows.
- Open the file in Excel and check that it contains data. Microsoft says that an empty CSV means the export failed, so export again. Keep the heading row in place and choose Yes if Excel asks about keeping the CSV format.
- In classic Outlook, go to File > Open & Export > Import/Export, choose Import from another program or file, then Comma Separated Values, then browse to the file. Choose how duplicates are handled. For missing data, Microsoft recommends Replace duplicates with items imported. Select the Contacts folder, then Finish.
- To verify, open the Address Book in Outlook, select the mailbox and choose Contacts.
Microsoft's page notes that Google does not export contact photos and that importing more than 2,000 contacts at once causes an error, so split larger files. If an import stops partway, Microsoft's "Fix problems importing contacts" page points to the row where it stopped as the likely cause.
Verify with a pilot user
Before migrating everyone, pick one person and compare:
- The number of calendars and contacts in Google against Outlook.
- A recurring weekly meeting: confirm the series, the time zone and the attendees.
- A meeting with a room: confirm the room is gone, then rebook it.
- A contact with four or more email addresses: expect only three.
- A calendar the user had shared: confirm it needs re-sharing.
Microsoft's own last step is to have migrated users check that their email, contacts and calendars migrated successfully. Take that literally: do not decommission Google data until the pilot checks pass.
Troubleshooting
| Symptom | Likely cause and fix |
|---|---|
| Calendar and contacts arrive slowly | Microsoft says throughput depends on the Google service account's quota; run smaller batches |
| Batch fails at the start | A prerequisite is missing; Microsoft states the migration will not succeed without all of them |
| Items reported as "missing" | MRM or archive policies removed items; disable them on target mailboxes before the batch |
| Contacts import errors | More than 2,000 contacts in one file; split the CSV |
| A contact has fewer addresses than before | Only three email addresses per contact migrate |
| Imported calendar is out of date | An imported .ics file does not update; re-import or subscribe |
| Cannot export a calendar | Check your permission on it, and ask your administrator whether exports are restricted |
Checklist
- Decide the method: batch with filters, or per-user import.
- Complete the prerequisites and run a one-user pilot.
- Select Calendar and Contacts on Move configuration; clear Mail only if mail is already moved.
- Complete the batch and assign licenses within 30 days.
- Rebuild room mailboxes and re-share calendars.
- Tell users about event colors, contact labels and the three-address limit.
- Keep Google data until the pilot checks pass.
What we checked
- Opened the Microsoft Learn pages on the automated Google Workspace batch, the Google Workspace migration limitations, batch completion and the business email and calendar overview on 2026-11-17. The filter options Mail, Calendar, Contacts and Rules appear on the batch page.
- Compared the limitations table (shared calendars, event colors, room bookings, three email addresses per contact, tags and URLs) with the overview page, which points to the same limitations page.
- Opened Microsoft's Gmail contacts import page and Google's contacts and calendar export pages on 2026-11-17. They differ on the export format name: Microsoft says "CSV for Outlook only" and Google's page names "Google CSV", which is why the article tells readers to check their dialog.
- Opened the Microsoft Learn pages for resource mailboxes and Add-MailboxFolderPermission and copied the example commands exactly as documented.
- Documented output: Microsoft shows no console output for the cmdlets above, so none is shown here.
- Not checked: nothing was run on a live Google Workspace or Microsoft 365 tenant, and the new Outlook import menu for .ics files and contacts was not checked. Steps follow vendor documentation as of 2026-11-17.
Last tested: 2026-11-17
References
- Perform a Google Workspace migration to Microsoft 365 or Office 365 (limitations)
- Perform an automated Google Workspace migration in EAC
- Completion of migration batch in EAC
- Migrate business email and calendar from Google Workspace
- Manage resource mailboxes in Exchange Online
- Add-MailboxFolderPermission
- Import Gmail contacts to Outlook
- Import calendars into Outlook
- Export your Google Calendar data
- Export Google contacts
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.