#Gmail Migration

Refer to the tables below to view the supported and unsupported object types for Gmail Migration.

√ – Supported; × – Unsupported.

#Mailbox

Object Type	Service Account Authentication Support Status	App Profile Support Status	Comment
User Mailbox	√	√	Refer to Comment 1 below the table.
Resource Mailbox	Partially Supported	Partially Supported	Refer to Comment 2 below the table.

Comment 1:

• User mailboxes cannot be migrated to Microsoft 365 Group mailboxes.

• The mailbox cannot be migrated to the destination if the user is Suspended or Archived.

• Mailbox delegations/permissions are not supported for migration.

Comment 2:

• Resource mailboxes cannot be migrated to Microsoft 365 Group mailboxes and Archive mailboxes.

• The following properties of events may not be migrated to the destination:

  • The event's color cannot be migrated to the destination because the Exchange calendar does not have the color property.
  • The event's notification time cannot be migrated to the destination, and the destination Reminder's default time (15 mins) will be displayed for the migrated events.
  • If the source event takes place during the time switch between the Daylight Saving Time (DST) and the Standard Time of the source time zone, the event time may not be correctly migrated to the destination.
  • If the destination Exchange is configured with a maximum booking lead time (days) for resource mailboxes and the meeting end date of the source event is later than the destination booking lead time, the event can be migrated, however, the event will be automatically cancelled after the event organizer updates the event in the destination.
  • If the destination Exchange is configured with a maximum event duration for resource mailboxes and the meeting duration of the source event exceeds the maximum destination duration, the event can be migrated; however, the event will be automatically canceled after the event organizer updates the event in the destination.

#Folder

Object Type	Service Account Authentication Support Status	App Profile Support Status	Comment
Inbox	√	√
Sent	√	√
All Mail	×	×	The All Mail folder is a virtual folder where all mails can be viewed.
Starred	Partially Supported	Partially Supported	The Starred label will not be migrated as a folder in the destination. Mails in the Starred label will be marked as a flag in the destination. For example, if a source mail in the Inbox folder has been added to the Starred label, it will be migrated to the Inbox folder and will be marked as a flag in the destination.
Drafts	√	√
Archive Folder	√	√	To view your archived items in the Archive folder, you can enter has:nouserlabels -label:Inbox -label:sent -label:spam -label:chats -label:drafts -label:trash -label:social -label:promotions -label:updates -label:forums -in:scheduled in the Gmail Search mail text box.
Spam	√	√
Trash	√	√
Snoozed	×	×
Important	Partially Supported	Partially Supported	The Important label will not be migrated as a folder in the destination. Mails in the Important label will be marked as important in the destination. For example, if a source mail in the Inbox folder has been added to the Important label, it will be migrated to the Inbox folder and will be marked as important in the destination.
Custom Label	√	√	Refer to Comment 1 below the table.
Chats	×	×
Scheduled	Partially Supported	Partially Supported	Scheduled mails can be migrated to the destination Scheduled folder, while the schedule settings cannot be migrated.
Category	Partially Supported	Partially Supported	Only the Social/Updates/Forums/Promotions labels and mails with these labels are supported in the migration.

Comment 1:

• Select Migrate labels as folders in the migration policy to migrate source mails with multiple labels to different folders based on the labels, which would result in duplicate mails in the destination. This option will keep the source folder structure.

• Select Migrate labels as categories in the migration policy to migrate source mails with custom labels to the destination "Inbox" folder and apply a category with the same name as the source custom label to the migrated mails.

#Item

Object Type	Service Account Authentication Support Status	App Profile Support Status	Comment
Mail	√	√	Refer to Comment 1 below the table.
Calendar	Partially Supported	Partially Supported	Refer to Comment 2 below the table.
Task	√	√	Refer to Comment 3 below the table.
Chat	×	×
Contacts	Partially Supported	Partially Supported	Refer to Additional Notes.
Other contacts	×	×
Contacts Labels	√	√	When migrating to Exchange Online, the contact labels whose contact email address is empty can be migrated, but the contact without an email address cannot be migrated to the destination Contact Group since the contact cannot be created in Exchange Online.
Google Group (Migrate to Microsoft 365 Group)	Partially Supported	Partially Supported	Refer to Comment 4 below the table.
Google Group (Migrate to Distribution Group)	Partially Supported	Partially Supported	Refer to Comment 4 below the table.
Google Group (Migrate to Mail-enabled Security Group)	Partially Supported	Partially Supported	Refer to Comment 4 below the table.
Google Group Conversation	×	×

Comment 1:

• The source muted mails cannot be retrieved and migrated due to source Google API limitations.

• Due to destination API limitations, emojis in the source mail body may not be correctly displayed in the destination after the migration.

• Mail attachments can be migrated to the destination. Note the following:

• In the source, if an attachment uploaded to the mail exceeds 25 MB, Gmail will save the attachment to the user's Google Drive and leave a link to the attachment; If an attachment is inserted to the mail from Google Drive, Gmail will display the attachment as a link. After the mail is migrated to the destination, the attachment link in the mail is migrated to the destination and can be directed to the attachment in Google Drive.

Comment 2:

• The Other Calendars are not supported in the migration.

• If you have the Make changes and manage sharing permission to primary calendars shared by others, these primary calendars cannot be migrated.

• The calendar cannot be migrated to the destination if the user is Suspended or Archived.

• The information of the meeting room will be migrated to the meeting body in the destination.

• The out of office/focus time events are not supported in the migration. The following properties of events may not be migrated to the destination:

  • The event's color cannot be migrated to the destination because the Exchange calendar does not have the color property.

  • If the source event takes place during the time switch between the Daylight Saving Time (DST) and the Standard Time of the source time zone, the event time may not be correctly migrated to the destination.

Comment 3:

• The tasks whose Titles and Details are empty will not be migrated.

• Subtasks of tasks will be migrated to tasks because the destination Exchange task does not have the corresponding property.

• The Repeat property value of the task cannot be migrated due to the limitations of Google API.

• The task cannot be migrated to the destination if the user is Suspended or Archived.

Comment 4:

• Google groups that have All users in the organisation as members/owners/managers cannot be migrated to the destination.

• Google groups that have External users as members/owners/managers can be migrated to the destination.

• The Manager role of Google Groups will be migrated as the Member role.

• The owners, managers, members, group name, and group description of Google Groups can be migrated.

Comment 16: Google groups that have All users in the organisation as members/owners/managers cannot be migrated to the destination. Google groups that have External users as members/owners/managers can be migrated to the destination. The Manager role of Google Groups will be migrated as the Member role. The owners, managers, members, group name, and group description of Google Groups can be migrated.

Comment 17: Google groups that have All users in the organisation as members/owners/managers cannot be migrated to the destination. Google groups that have External users as members/owners/managers can be migrated to the destination. The Manager role of Google Groups will be migrated as the Member role. The owners, managers, members, group name, and group description of Google Groups can be migrated.

#Item Property

Object Type	Service Account Authentication Support Status	App Profile Support Status	Comment
Flag	√	√
Mark as read/unread	√	√
Category	Partially Supported	Partially Supported	Refer to Comment 1 below the table.
Attachment	√	√
Sharing Permissions	×	×

Comment 1:

• If you select the Migrate labels as folders option in the migration policy, source mails with multiple labels will be migrated to different folders based on the labels, which would result in duplicate mails in the destination. This option will keep the source folder structure.

• If you select the Migrate labels as categories option in the migration policy, source mails with multiple labels will be migrated to the destination built-in folder, which has the same name as the source folder in the corresponding language.

#Hold Data in Google Workspace

Object Type	Service Account Authentication Support Status	App Profile Support Status
Hold Mail	×	×
Google Group Conversation	×	×

#Gmail Setting

Object Type	Service Account Authentication Support Status	App Profile Support Status	Comment
Filter (Gmail Setting)	Partially Supported	Partially Supported	Refer to the Gmail Filter to Inbox Rule Mappings section to view the Gmail filter to Exchange inbox rule mappings.

#Additional Notes

• The inbox rules can be migrated when the source is not a resource mailbox and the destination is not an archive mailbox.

• The data size will be reduced when the source Gmail data is migrated to the destination Exchange due to the different data storage methods.

• When the source email configures the Confidential mode, after the migration, the email content cannot be displayed, and the email will contain a link in the destination. Recipients can click the link and log in to their Google accounts to view the email content when the source sender is online.

• While migration is in progress, for calendar invites, having an organizer at the Microsoft 365 side while some attendees at the Gmail side and with proper forwarding setup, the update or cancellation by the organizer cannot be synchronized to those attendees' Gmail calendars although attendees at the Gmail side do receive the emails triggered by the update or cancellation.

• When migrating Gmail contacts, note the following issues:

  • Contacts in the Trash folder cannot be migrated.

  • The prefix of a contact is migrated as the title in the destination.

  • If the birthday value of the contact is in the Date format, such as mm/dd/yyyy, yyyy-mm-dd, and mm.dd.yyyy, the birthday can be migrated.

    If the birthday value of the contact is in the Time format, such as mm/dd/yyyy HH:mm:ss, yyyy-mm-dd HH:mm:ss, and yyyymmddHHmmss, the birthday can be migrated, but only the birthday date can be displayed in the destination.

  • The phonetic middle of the contact cannot be migrated because the Exchange contact does not have the corresponding property.

  • The File as a property value of the contact cannot be migrated.

  • Only the first three email addresses of the contact can be migrated because only three email addresses can be added for the Exchange contact.

  • If a source contact's email address format is invalid or empty, the contact can be migrated but will not be added to the contact group in the destination.

  • If the contact's email address contains illegal characters that are not supported by EWS, the contact cannot be migrated.

  • Labels of contact email addresses cannot be migrated because the Exchange contact does not have the corresponding property.

  • The phone number of the Google Voice label is migrated as the Other type in the destination.

  • Only the first two/first (based on label type) phone numbers with the same label will be migrated.

  • The country of phone numbers will not be migrated.

  • If a contact has multiple street addresses with the same label, only the first street address of that label can be migrated since only one address with each label can be added for an Exchange contact.

  • The PO Box of the contact cannot be migrated because the Exchange contact does not have the corresponding property.

  • The Profile, Blog, or Home Page website of the contact is migrated as the Personal Web page in the destination. If multiple websites of the Profile, Blog, and Home Page types are added to the contact, only the first website can be migrated regardless of the website type because only one Personal Web page can be added for the Exchange contact.

  • The Work website of the contact is migrated as the Business Web page in the destination. If multiple Work websites are added to the contact, only the first website can be migrated because only one Business Web page can be added for the Exchange contact.

  • Only the first Work website can be migrated and will be migrated as the Business Web page in the destination because only one Business Web page can be added for the Exchange contact.

  • The relationships of contacts are migrated as Notes in the destination. Each relationship value is migrated as one row in the Notes.

  • Only the Anniversary event of the contact can be migrated, and only the first Anniversary event can be migrated because only one Anniversary can be added for the Exchange contact.

  • Only the first chat of the contact can be migrated because only one chat can be displayed for the Exchange contact. The label of chat is not supported in Exchange.

  • The internal calls of the contact cannot be migrated due to API limitations.

  • The custom fields of the contact cannot be migrated because the Exchange contact does not have the corresponding property.

  • If the character length of the following properties of a contact exceeds 255, the extra characters will be pruned after the migration: Prefix, First name, Middle name, Last name, Suffix, Phonetic first, Phonetic last, Nickname, Company, Job title, Department, Email, Phone, Street address (Postal Code, ZIP code, State, Province, City), Website, and Chat.