IMPORTANT: Now it is not required to enable IMAP for migrations from G Suite on the organization level unless you need 'Important' and 'Starred' target folders to have the same non-English localized names as the corresponding Gmail labels on the source.
To have migrated Google Labels appear in the Office 365 Categories list, in O365, open manage categories... from the categorize menu and select add new category. Then create a category that exactly matches a category that was applied to an O365 message during the migration. All messages marked with that category will take on the color applied (if any) and the category will remain on the user's list for future use.
This can also be achieved in Outlook 2010. From the Home tab, click the Categorize button and then select All Categories. You will see your labels that are missing with (Not in Master Category List) next to the name. Select the category, click New, select a color, and click Save.
The Chats label is no longer supported due to Google Chat was officially shut down (https://support.google.com/chat/?hl=en).
Note: ODME does not migrate primary shared calendars.
If you want to allow the migration of secondary shared calendars, which will become independent (orphaned) calendars in the target:
On an individual user basis:
If you want to prevent the migration of secondary shared calendars, so that they can be setup natively as shared calendars in the target:
On an individual user basis:
Log in to the account whose calendar is being shared.
Go to Calendar > Settings (gear icon) > Settings > Calendars.
Under "Share with specific people", change the Permission Settings for the user(s) with the "Make changes AND manage sharing" permission to any other option you want.
ODME does not migrate some Contact fields from G Suite to Office 365.
Fields that are currently supported:
Job title, Company
Note: When migrating contacts, ODME explicitly validates the Email Address property. If the property does not contain the correct e-mail address, it will not be migrated.
Custom G Suite fields that cannot be migrated from G Suite to Office 365:
The "other" URL for Zimbra contacts is not migrated.
Items contained Zimbra Briefcases are not migrated.
ODME does not correctly map contact File-As field "Company (First Last)".
Tags applied to mail, contacts, and tasks are not migrated.
Certain mail items that can be defined in the Zimbra Outlook connector are not supported in the Zimbra UI and as a result cannot be migrated. These mail items include, but are not limited to, the recurrence information for tasks and completed date fields.
ODME cannot migrate Zimbra item fields that do not exist on the target. For example, when migrating to O365, the location field on tasks will not migrate as there is no comparable field for tasks in O365.
ODME support migrating a total of 3 email addresses per contact to an Exchange target mailbox. Zimbra has fields for 5 addresses per contact.
ODME cannot migrate to an Exchange target group members in Zimbra that do not have contacts with defined email addresses. This is because Exchange requires each member of a distribution list to have an email address, while group members in Zimbra are not required to have an email address.
ODME does not migrate message tags.
ODME does not support migration of excluded dates in recurring meetings. For example, if a meeting is scheduled for "every Friday, except 2015-05-01", then it will be migrated as recurring “every Friday” - the excluded date will not be migrated to the target server.
For the list of known issues, please refer http://documents.quest.com/on-demand-migration-for-email/release-notes/known-issues.