#Migration to Gmail

Refer to the table below to view the supported and unsupported object types for Exchange Online to Gmail Migration.

√ – Supported; × – Unsupported.

#Mailbox

Object Type	Source App Profile Support Status	Source Service Account Authentication Support Status	Comment
User mailbox	√	Partially Supported	Refer to Comment 1 below the table
Microsoft 365 Group mailbox	Partially Supported	Partially Supported	Refer to the notes in Additional Notes for considerations when the destination is a Google Group.
Shared mailbox	Partially Supported	Partially Supported	Refer to Comment 2 below the table
Resource mailbox	√	√	Refer to Comment 3 below the table
Archive mailbox	√	√
Scheduling mailbox	×	×

Comment 1:

• When the usage of mailboxes exceeds storage quota, they also can be migrated.

• Inactive mailboxes and mailboxes of users who are blocked from signing in are supported in Exchange Online Migration.

• If the license is removed from the source user in the Microsoft 365 admin center before the migration of the user mailbox, note the following:

  • When the litigation hold setting is enabled for the user, the user mailbox can be migrated.

  • When the litigation hold setting is not enabled for the user, the user mailbox can only be migrated within a period of time after removing the user license.

• When the destination is a Google Group, only users/groups with Full Access to the source user mailbox can be migrated as Google Group members. If a full-access user is mapped to a banned user, the banned user can still be added as a member.

  NOTE

  If a user is already added to the destination group as a member, manager, or owner, the migrate group permission process will not update that user's role.

Comment 2:

• When the destination is a Google Group, only users/groups with Full Access to the source shared mailbox can be migrated as Google Group members. If a full-access user is mapped to a banned user, the banned user can still be added as a member.

  NOTE

  If a user is already added to the destination group as a member, manager, or owner, the migrate group permission process will not update that user's role.

  Refer to the notes in Additional Notes for additional considerations when the destination is a Google Group.

Comment 3: When the destination is a Google Group, only users/groups with Full Access to the source resource mailbox can be migrated as Google Group members. If a full-access user is mapped to a banned user, the banned user can still be added as a member.

#Mailbox Property

Property	Source App Profile Support Status	Source Service Account Authentication Support Status
Hide from global address list (GAL)	×	×
General Information	×	×
Booking options	×	×

#Mailbox Folder

Folder Type	Source App Profile Support Status	Source Service Account Authentication Support Status	Comment
Inbox	√	√
Sent Items	√	√
Deleted Items	√	√
Drafts	√	√	Refer to Comment 1 below the table
Archive	√	√	Refer to Comment 2 below the table
Conversation History	√	√
Notes	×	×
RSS Subscriptions	√	√	Only the RSS Subscriptions folders can be migrated to the destination. The items in RSS Subscriptions folders cannot be migrated.
Custom Folder	√	√	Refer to Comment 3 below the table
Junk Email	Partially Supported	Partially Supported
Contacts	×	×
Calendar	Partially Supported	Partially Supported	Refer to Comment 4 below the table
Journal	×	×
Recoverable Items - Deletions	√	√	Only emails in the Deletions folder can be migrated. These emails will be migrated to the destination Trash label and applied with a Recoverable Items label.
Recoverable Items - Versions	×	×	Only emails in the Deletions folder can be migrated. These emails will be migrated to the destination Trash label and applied with a Recoverable Items label.
Recoverable Items - Purges	×	×	Only emails in the Deletions folder can be migrated. These emails will be migrated to the destination Trash label and applied with a Recoverable Items label.
Recoverable Items - Audits	×	×	Only emails in the Deletions folder can be migrated. These emails will be migrated to the destination Trash label and applied with a Recoverable Items label.
Recoverable Items - DiscoveryHolds	×	×	Only emails in the Deletions folder can be migrated. These emails will be migrated to the destination Trash label and applied with a Recoverable Items label.
Recoverable Items - Calendar Logging	×	×	Only emails in the Deletions folder can be migrated. These emails will be migrated to the destination Trash label and applied with a Recoverable Items label.
Recoverable Items - SubstrateHolds	×	×	Only emails in the Deletions folder can be migrated. These emails will be migrated to the destination Trash label and applied with a Recoverable Items label.
Tasks	×	×
Sync Issues	×	×	Sync Issues folders hold the synchronization logs that record any general problems or delays in syncing with the email server. These folders are skipped in the migration because they may contain many logs that will affect the migration performance and consume storage space in the destination.
Search Folders	×	×	Search folders are virtual folders that do not contain any actual items.
Snoozed	√	√
Hidden folder	×	×

Comment 1:

• When the destination is a Google Group, the Drafts folder will be skipped by default.

• After migrating a draft, if you edit the source and destination drafts and run an incremental job to migrate the draft, the destination draft cannot be overwritten and the source edited draft will be migrated as a new draft.

Comment 2:

• Email in archive folder will be migrated to destination without any labels.

• A suffix -migrated will be added to the destination folder.

Comment 3:

• If the source custom folder name is the same as a destination reserved label, a suffix -migrated will be added to the destination label.

• The custom contact folder is not supported in the migration.

Comment 4:

• The Other Calendars are not supported in the migration. The Calendar Group is not supported in the migration.

• The meeting links are not supported in the migration.

• The link of a Skype for Business meeting on the calendar will not be replaced with the destination link after the migration.

• If you do not keep the domain of the source environment to the destination, enable the Replace email addresses of senders/recipients based on user mappings setting in the migration policy to replace the recipients' email addresses with the corresponding email addresses in the destination. However, source users of calendar items created in a public folder cannot be replaced with the destination users due to API limitations.

• If you enable the Replace meeting links with the destination information setting in the migration policy to replace the source meeting link with a destination link:

  • Make sure you have configured user mappings for the source meeting organizers and select the Replace email addresses of senders/recipients based on user mappings option.

  • If the organizer or attendee is mapped to a calendar resource in the destination, the meeting link cannot be replaced and will remain the same as the source.

  • If you migrate only the attendee and select the option to replace the meeting link, the destination attendee's event will not display a meeting link.

• If user mappings are not configured for users related to the source calendar event, the calendar will be added as the event attendee after the migration.

• Only built-in calendar folder of source user/shared/resource mailbox can be migrated when the destination is a calendar resource.

• Birthday folder cannot be migrated.

• Embedded images inserted in source event description will be migrated as attachments on destination.

• Attachments inserted via Outlook Item cannot be migrated.

• The HTML format for the event body cannot be kept in the destination.

#Mailbox Item

Item Type	Source App Profile Support Status	Source Service Account Authentication Support Status	Comment
Email	√	√	Only the title and body of the source meeting requests can be kept.
Post	√	√
Appointment	Partially Supported	Partially Supported	Appointment is a calendar item and follows the limitations of calendars.
Meeting	Partially Supported	Partially Supported	Meeting is a calendar item and follows the limitations of calendars.
Contact	Partially Supported	Partially Supported	If the "Migrate event, task, and contact attachments to Google Drive for the destination user mailbox" option is not selected in the migration policy, the contact note attachments cannot be migrated. If the option is selected, contact note attachments will be added as links to the note.
Task	Partially Supported	Partially Supported	Refer to Comment 1 below the table
Note	×	×
Journal Entry	×	×
Conversation	√	√
Auto-complete list	×	×

Comment 1:

• The Repeat property of the task cannot be kept in the destination.

• The assignees of the task cannot be kept in the destination.

• If you clear mapping reports, then rerun a migration job, this will result in duplicate tasks in the destination.

• The Start Date, Status, Priority, Reminder, Follow-up, Category, and Task Recurrence fields cannot be migrated because they are not supported in the destination system.

#Mailbox Item Property

Property	Source App Profile Support Status	Source Service Account Authentication Support Status	Comment
Assign Policy	×	×
Pin/Unpin	×	×
Flag	√	√	Items will be applied with a starred label after the migration.
Mark as Read/Unread	√	√
Importance	√	√	Items will be applied with an Importance label after the migration.
Follow Up	√	√	Items will be applied with a starred label after the migration.
Category	√	√	The categories will be replaced with a label with the same name as the source categories in the destination.
To-Do list	√	√
Sensitivity label of email	Partially Supported	Partially Supported	Refer to Comment 1 below the table.
Reply status of meeting participants	√	√
Sharing Permissions	Partially Supported	Partially Supported	Refer to the Shared Calendar Permission Mappings section to view how Exchange Online shared calendar permissions map to Gmail during migrations.

Comment 1: Fly does not migrate sensitivity labels but allows you to remove source sensitivity labels from emails.

#Global contact

Object	Source App Profile Support Status	Source Service Account Authentication Support Status	Comment
Global contact	×	×

#Mailbox Delegations

Delegation Type	Source App Profile Support Status	Source Service Account Authentication Support Status
User mailbox	×	×
Resource mailbox	×	×
Shared mailbox	×	×
Microsoft 365 Group	×	×
Distribution list/Mail-enabled security group/Dynamic distribution list	×	×

#Group

Group Type	Source App Profile Support Status	Source Service Account Authentication Support Status	Comment
Distribution group	Partially Supported	Partially Supported	Refer to Comment 1 below the table.
Mail-enabled security group	Partially Supported	Partially Supported	Refer to Comment 1 below the table.
Dynamic distribution group	Partially Supported	Partially Supported	Refer to Comment 1 below the table.

Comment 1:

• Refer to the Supported Membership Filters for Dynamic Distribution List section to view the supported membership filters for dynamic distribution list.

• Refer to the Destination Group Privacy When Migrating to Non-Existing Google Groups section for details on destination group privacy settings when migrating source types to Google Groups.

• When migrating to a non‑existent Google Group, refer to Google Groups Help for limitations on email addresses and group names when creating a destination Google Group.

#Outlook settings

Type	Source App Profile Support Status	Source Service Account Authentication Support Status	Comment
Outlook configuration - User profiles	×	×
Outlook configuration - Signatures	×	×
Email forwarding	×	×
Outlook quick action setting	×	×
Automatic Replies (Out of Office) settings	×	×
Inbox rules	Partially Supported	Partially Supported	Refer to the Exchange Rule to Gmail Filter Mappings section to view the Exchange inbox rule to Gmail filters mappings.

#Additional Notes

• If the source category is a reserved label in Gmail, a suffix -migrated will be added to the destination label to avoid conflicts.

• If the source mail folder name exceeds Google’s limit of 255 characters. Only 255 characters of the name can be kept in the destination.

• Emails in the subfolders of the source Inbox folder will be migrated to the destination system Inbox label. Emails in the subfolders of other source built-in folders (Sent Items, Drafts, Deleted Items, etc.) will be migrated to corresponding system labels in the destination and applied with a destination system label corresponding to the source built-in folder.

• If the source email contains a calendar as attachment, select the option in the migration policy to migrate email attachments to Google Drive.

• If you clear mapping reports, then rerun a migration job, this will result in duplicate tasks in the destination.

• When the destination is a Google Group, note the following:

  • Refer to Google Groups Help for limitations on email addresses and group names when creating a destination Google Group.

  • Make sure the destinations configured in user mappings match the member types of the destination Google Group.

  • If multiple emails share the same Message ID, only one will be migrated.

  • Emails will be unread in the destination after migration.

  • Once emails are migrated to a Google Group, subsequent jobs cannot update them (e.g., read/unread status), as conflict resolution does not apply.

  • All emails will be migrated to the Conversations in the Google Group without labels applied.

  • Calendars, contacts, rules, and tasks cannot be migrated when the destination is a Google Group.