Migration from Exchange Online

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

√ – Supported; × –Unsupported.

Object Type	Object Type	Object Type	Object Type	App Profile Support Status	Service Account Authentication Support Status	Comment
Mailbox
User mailbox	User mailbox	User mailbox	√	Partially Supported	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.Exchange Online PowerShell is not supported for inactive mailboxes.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.
Mailbox
Microsoft 365 Group mailbox	Microsoft 365 Group mailbox	Microsoft 365 Group mailbox	√	√	When the usage of mailboxes exceeds 50 GB, they can also be migrated.
Mailbox
Shared mailbox	Shared mailbox	Shared mailbox	√	√	When the usage of mailboxes exceeds storage quota, they can also be migrated.
Mailbox
Resource mailbox	Resource mailbox	Resource mailbox	√	√	When the usage of mailboxes exceeds 50 GB, they can also be migrated.
Mailbox
Archive mailbox	Archive mailbox	Archive mailbox	√	√	If the storage space of destination archive mailbox is full during the migration, you need to make sure the auto-expanding archiving feature is enabled for the destination archive mailbox and run an incremental migration job to migrate newly created or modified source data every day.
Mailbox
Scheduling mailbox	Scheduling mailbox	Scheduling mailbox	×	×
Mailbox property	Mailbox property	Mailbox property	Hide from global address list (GAL)	Partially Supported	Partially Supported	Supported when migrating from resource/shared mailboxes to destination newly created resource/shared mailboxes.
Mailbox property	Mailbox property	Mailbox property	General Information	Partially Supported	Partially Supported	Supported when migrating from resource/shared mailboxes to destination newly created resource/shared mailboxes.
Mailbox property	Mailbox property	Mailbox property	Booking options	Partially Supported	Partially Supported	Only supported when migrating from resource mailboxes to destination newly created resource mailboxes.
Mailbox property	Mailbox property	Mailbox property	Resource scheduling settings	Partially Supported	Partially Supported	Only supported when migrating from resource mailboxes to destination newly created resource mailboxes.
Distribution list/Mail-enabled security group	Migrate to Microsoft 365 Group	Migrate to Microsoft 365 Group	Migrate to Microsoft 365 Group	√	√
Distribution list/Mail-enabled security group	Migrate to distribution list	Migrate to distribution list	Migrate to distribution list	√	√	If you map a source room list to a distribution list that does not exist in the destination, Fly will create the room list in the destination.
Distribution list/Mail-enabled security group	Migrate to mail-enabled security group	Migrate to mail-enabled security group	Migrate to mail-enabled security group	√	√
Dynamic distribution list	Dynamic distribution list	Dynamic distribution list	Dynamic distribution list	√	√	Dynamic distribution lists can only be migrated to dynamic distribution lists.
Mailbox folder	Inbox	Inbox	Inbox	√	√
Mailbox folder	Sent Items	Sent Items	Sent Items	√	√
Mailbox folder	Deleted Items	Deleted Items	Deleted Items	√	√
Mailbox folder	Drafts	Drafts	Drafts	√	√	The time of the migrated draft items in the destination will be the migration time of the items when viewing the items via OWA.
Mailbox folder	Archive	Archive	Archive	√	√
Mailbox folder	Conversation History	Conversation History	Conversation History	√	√
Mailbox folder	Notes	Notes	Notes	√	√
Mailbox folder	RSS Subscriptions	RSS Subscriptions	RSS Subscriptions	√	√	Only the RSS Subscriptions folders can be migrated to the destination. The items in RSS Subscriptions folders cannot be migrated.
Mailbox folder	Custom Folder	Custom Folder	Custom Folder	√	√
Mailbox folder	Junk Email	Junk Email	Junk Email	√	√
Mailbox folder	Contacts	Contacts	Contacts	√	√
Mailbox folder	Calendar	Calendar	Calendar	Partially Supported	Partially Supported	Due to API limitations, when migrating a calendar item with encrypted email attachments, the email content will appear blank in the destination environment. To ensure that destination users can access and view the message, enable the Replace email addresses of senders/recipients based on user mappings setting in the Exchange Online migration policy to replace the recipients' email addresses with the corresponding email addresses in the destination.The Other Calendars are not supported in the migration.The Calendar Group is 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 Exchange Online migration policy to replace the recipients’ email addresses with the corresponding email addresses in the destination. However, in the following cases, source users are not replaced with the destination users after the migration:● When the organizer views the calendar item in the destination, the source organizer/attendees are replaced with the destination users, but when the attendees view the calendar item, the source users are not replaced with the destination users.Source users of calendar items created in a public folder cannot be replaced with the destination users due to API limitations.● When attendees respond to the migrated item in the destination, email notifications may be sent to the source organizer. You need to configure the Email Forwarding setting for the source organizer to redirect emails sent to the source organizer to the destination organizer.● Though attendees have accepted a calendar item in the source, after the migration, when the organizer views the migrated item in the destination, there is no user responding to the event, and the organizer is added to the Didn’t respond list. ● The source resource mailboxes in calendar items can be replaced with the destination resource mailboxes. However, the resource names displayed in the Location of the destination calendar items and meeting requests are still the source names.If you enable the Replace the meeting links with the destination information setting in the Exchange Online 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 there are some notes that need your attention. Refer to the Notes when Replacing Meeting Links section below for details.
Mailbox folder	Journal	Journal	Journal	√	√
Mailbox folder	Recoverable Items folders	Deletions	Deletions	√	√	The Recoverable Items folders cannot be migrated from/to Microsoft 365 Group mailboxes.Subfolders that are manually created in the source Recoverable Items folders can only be migrated when there are subfolders with the same name exist in the destination Recoverable Items folders.
Mailbox folder	Recoverable Items folders	Versions	Versions	√	√	The Recoverable Items folders cannot be migrated from/to Microsoft 365 Group mailboxes.Subfolders that are manually created in the source Recoverable Items folders can only be migrated when there are subfolders with the same name exist in the destination Recoverable Items folders.
Mailbox folder	Recoverable Items folders	Purges	Purges	√	√	The Recoverable Items folders cannot be migrated from/to Microsoft 365 Group mailboxes.Subfolders that are manually created in the source Recoverable Items folders can only be migrated when there are subfolders with the same name exist in the destination Recoverable Items folders.
Mailbox folder	Recoverable Items folders	Audits	Audits	×	×	The Recoverable Items folders cannot be migrated from/to Microsoft 365 Group mailboxes.Subfolders that are manually created in the source Recoverable Items folders can only be migrated when there are subfolders with the same name exist in the destination Recoverable Items folders.
Mailbox folder	Recoverable Items folders	DiscoveryHolds	DiscoveryHolds	√	√	The Recoverable Items folders cannot be migrated from/to Microsoft 365 Group mailboxes.Subfolders that are manually created in the source Recoverable Items folders can only be migrated when there are subfolders with the same name exist in the destination Recoverable Items folders.
Mailbox folder	Recoverable Items folders	Calendar Logging	Calendar Logging	×	×	The Recoverable Items folders cannot be migrated from/to Microsoft 365 Group mailboxes.Subfolders that are manually created in the source Recoverable Items folders can only be migrated when there are subfolders with the same name exist in the destination Recoverable Items folders.
Mailbox folder	Recoverable Items folders	SubstrateHolds	SubstrateHolds	√	√	The Recoverable Items folders cannot be migrated from/to Microsoft 365 Group mailboxes.Subfolders that are manually created in the source Recoverable Items folders can only be migrated when there are subfolders with the same name exist in the destination Recoverable Items folders.
Mailbox folder	Tasks	Tasks	Tasks	√	√	For tasks in the Outlook Desktop App, 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 Exchange Online migration policy to replace the recipients’ email addresses with the corresponding email addresses in the destination. However, the email address of the task assignee may not be replaced with the destination email address after the migration.For tasks in the Outlook Web App, the task assignees cannot be migrated.
Mailbox folder	Sync Issues	Sync Issues	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.
Mailbox folder	Search Folders	Search Folders	Search Folders	×	×	Search folders are virtual folders that do not contain any actual items.
Mailbox folder	Snoozed	Snoozed	Snoozed	√	√
Mailbox folder	Hidden folder	Hidden folder	Hidden folder	Partially Supported	Partially Supported	When the source folder is a hidden folder, note the following:● If the destination folder does not exist, Fly will create a hidden folder with the same name as the source, and migrate the data, properties, and structure of the source hidden folder to the destination hidden folder.● If a normal folder with the same name as the source hidden folder exists in the destination, Fly will only migrate the data in the source hidden folder to the destination folder without changing the properties and structure of the destination folder.
Mailbox item	Email	Email	Email	√	√	The DateTimeCreated property of emails cannot be migrated due to API limitations.
Mailbox item	Post	Post	Post	√	√
Mailbox item	Appointment	Appointment	Appointment	√	√	Appointment is a calendar item and follows the limitations of calendars.
Mailbox item	Meeting	Meeting	Meeting	Partially Supported	Partially Supported	Meeting is a calendar item and follows the limitations of calendars.
Mailbox item	Contact	Contact	Contact	Partially Supported	Partially Supported	The source contacts that have been added to favorites will not be marked as favorites in the destination after the migration.
Mailbox item	Task	Task	Task	√	√
Mailbox item	Note	Note	Note	√	√
Mailbox item	Journal Entry	Journal Entry	Journal Entry	√	√
Mailbox item	Conversation	Conversation	Conversation	√	√
Mailbox item	Auto-complete list	Auto-complete list	Auto-complete list	Partially Supported	Partially Supported	The auto-complete lists generated via Outlook Web Access cannot be migrated due to an API limitation.The auto-complete lists generated via Outlook for Mac cannot be migrated because Outlook for Mac does not synchronize the auto-complete lists from/to Exchange Online. Refer to how the auto-complete lists features works in Outlook for Mac for more information.The auto-complete lists cannot be migrated from/to archive mailboxes or Microsoft 365 Group mailboxes.
Mailbox item property	Assign Policy	Assign Policy	Assign Policy	Partially Supported	Partially Supported	Only the built-in archive policies and retention policies applied on emails can be migrated.
Mailbox item property	Pin/Unpin	Pin/Unpin	Pin/Unpin	√	√
Mailbox item property	Flag	Flag	Flag	√	√
Mailbox item property	Mark as Read/Unread	Mark as Read/Unread	Mark as Read/Unread	√	√
Mailbox item property	Follow Up	Follow Up	Follow Up	√	√
Mailbox item property	Category	Category	Category	Partially Supported	Partially Supported	The custom categories can be migrated to the destination, but the color of the custom categories will be displayed in grey in the destination.
Mailbox item property	To-Do list	To-Do list	To-Do list	×	×	The property will no longer be supported due to Microsoft’s changes.
Mailbox item property	Sensitivity label of email	Sensitivity label of email	Sensitivity label of email	Partially Supported	Partially Supported	Sensitivity labels and default Rights Management Service are not supported when the source or destination is a 21Vianet tenant.Custom Rights Management Service is not supported for any tenants.Make sure the option selected for the Assign permissions now or let users decide? setting of the source and destination labels are the same.The sensitivity labels using the Double Key Encryption cannot be migrated.The emails encrypted by external users cannot be decrypted and cannot be migrated.If the label on the source email contains sublabels, the email cannot be migrated.If the label has not been published to the destination user, the label on the email cannot be displayed.
Mailbox item property	Reply status of meeting participants	Reply status of meeting participants	Reply status of meeting participants	×	×
Mailbox item property	Sharing Permissions	Sharing Permissions	Sharing Permissions	Partially Supported	Partially Supported	Only sharing permissions of calendar folders can be migrated.
Global contact	Global contact	Global contact	Global contact	√	√	Fly provides scripts for you to migrate global contact. Refer to the Step 7 in Prepare for Migrations for details.The scripts can only be used to sync the mail contacts in global contacts
Mailbox delegations	User mailbox	User mailbox	User mailbox	Partially Supported	Partially Supported	The Send As permission, Send on Behalf permission, and Full Access permission of user mailboxes can be migrated.Permissions of folders in user mailboxes are not supported to migrate.
Mailbox delegations	Resource mailbox	Resource mailbox	Resource mailbox	Partially Supported	Partially Supported	The Send As permission, Send on Behalf permission, and Full Access permission of resource mailboxes can be migrated. Permissions of folders in resource mailboxes are not supported to migrate.
Mailbox delegations	Shared mailbox	Shared mailbox	Shared mailbox	Partially Supported	Partially Supported	The Send As permission, Send on Behalf permission, and Full Access permission of shared mailboxes can be migrated.Permissions of folders in mailboxes are not supported to migrate.
Mailbox delegations	Microsoft 365 Group	Microsoft 365 Group	Microsoft 365 Group	Partially Supported	Partially Supported	The Send As permission and Send on Behalf permission of Microsoft 365 Group mailboxes can be migrated.Permissions of folders in mailboxes are not supported to migrate.
Mailbox delegations	Distribution list/Mail-enabled security group/ Dynamic distribution list	Distribution list/Mail-enabled security group/ Dynamic distribution list	Distribution list/Mail-enabled security group/ Dynamic distribution list	√	√
Distribution list/Mail-enabled security group/Dynamic distribution list settings*Note: By default, Fly will migrate the Settings configured for distribution lists /mail-enabled security groups / dynamic distribution group. If you don’t want to migrate the Settings, you can add the MigrateDistributionListSettings=false string to the Customized features section to disable this feature. Refer to Customized Features for Exchange Online Migration for details.	Distribution list/Mail-enabled security group/Dynamic distribution list settings*Note: By default, Fly will migrate the Settings configured for distribution lists /mail-enabled security groups / dynamic distribution group. If you don’t want to migrate the Settings, you can add the MigrateDistributionListSettings=false string to the Customized features section to disable this feature. Refer to Customized Features for Exchange Online Migration for details.	Distribution list/Mail-enabled security group/Dynamic distribution list settings*Note: By default, Fly will migrate the Settings configured for distribution lists /mail-enabled security groups / dynamic distribution group. If you don’t want to migrate the Settings, you can add the MigrateDistributionListSettings=false string to the Customized features section to disable this feature. Refer to Customized Features for Exchange Online Migration for details.	Distribution list/Mail-enabled security group/Dynamic distribution list settings*Note: By default, Fly will migrate the Settings configured for distribution lists /mail-enabled security groups / dynamic distribution group. If you don’t want to migrate the Settings, you can add the MigrateDistributionListSettings=false string to the Customized features section to disable this feature. Refer to Customized Features for Exchange Online Migration for details.	Partially Supported	Partially Supported	If the destination group already exists, Fly can migrate the source owners/members and keep the destination owners/members.For the Members rules of dynamic distribution lists, Fly will migrate them based on the conflict resolution configured in the migration policy.
Outlook settings	Outlook configuration	User profiles	User profiles	√	√	If you use the Fly Assist tool to update the Outlook profiles of end users, make sure the end user device uses a Windows operating system. For Outlook for Mac, you can refer to Manage profiles or identities in Outlook for Mac for guidance.*Note: The Fly Assist tool does not support the new Outlook.*Note: If there are multiple email accounts in your profile and you configure the Outlook profile for the primary email account via Fly Assist tool, the corresponding email account in the destination cannot be configured as the primary account.*Note: If there are multiple email accounts in the default profile and you configure the Outlook profile for the default email account via the Fly Assist tool, the corresponding email account in the destination cannot be configured as the default email account.
Outlook settings	Outlook configuration	Signatures	Signatures	×	×
Outlook settings	Email forwarding	Email forwarding	Email forwarding	×	×
Outlook settings	Outlook quick action setting	Outlook quick action setting	Outlook quick action setting	×	×
Outlook settings	Automatic Replies (Out of Office) settings	Automatic Replies (Out of Office) settings	Automatic Replies (Out of Office) settings	Partially Supported	Partially Supported	Only the Automatic Replies (Out of Office) settings of user/resource/shared mailboxes can be migrated.
Outlook settings	Inbox rules	Inbox rules	Inbox rules	Partially Supported	Partially Supported	Refer to Supported and Unsupported Outlook on the Web Rules and Supported and Unsupported Outlook Rules for details.Rules are migrated based on their names. After a rule is migrated, if you change the name of the source rule, it will be migrated again in the incremental jobs.

Notes when Replacing Meeting Links

If you enable the Replace meeting links with the destination information setting to replace the source meeting link with a destination link, some issues may occur in the following situations:

Due to API limitations, some features may be different from the source after users join the meeting with the new links.
- If destination organizers join the meeting via Teams on the web:
  - Chat, Apps, Record and translation, and Meeting notes actions are not available.
  - The meeting title, date and time, Meeting ID, and Meeting options link will not be displayed in Meeting info.
  - The Turn off incoming video action will not be displayed in More > Settings, but will be displayed in View > More options.
  - Only the current user will be displayed in the meeting.
  - The meeting duration will not be displayed.
  - The options in Meeting options displayed in More > Settings will not be displayed.
- If destination attendees join the meeting via Teams on the web:
  - Chat, Apps, Record and translation, and Meeting notes actions are not available.
  - The meeting title, date and time, Meeting ID, and Meeting options link will not be displayed in Meeting info.
  - The Turn off incoming video action will not be displayed in More > Settings, but will be displayed in View > More options.
  - Only the current user will be displayed in the meeting.
  - The meeting duration will not be displayed.
- If destination organizers join the meeting via the Teams app:
  - Chat, Apps, Record and translation, and Meeting notes actions are not available.
  - Only the current user will be displayed in the meeting.
  - The meeting title, date and time, Meeting ID, and Meeting options link will not be displayed in Meeting info.
  - The meeting duration will not be displayed.
  - The options in Meeting options displayed in More > Settings will not be displayed.
- If destination attendees join the meeting via the Teams app:
  - Chat, Apps, Record and translation, and Meeting notes actions are not available.
  - Only the current user will be displayed in the meeting.
  - The meeting title, date and time, Meeting ID, and Meeting options link will not be displayed in Meeting info.
  - The meeting duration will not be displayed.
The Meeting options link in the calendar cannot be opened.
The Join on the web link in the source calendar item cannot be replaced with the destination information. After you map the source meeting attendees to the destination, when the mapped attendees click the Join on the web link and use the meeting ID and passcode to join the meeting via Microsoft Teams on the web, they will wait in the lobby until the meeting organizer allows the user to enter the meeting.
The source tenant ID in the meeting link will be replaced with the destination information. If some users in your organization have been migrated to the destination and the meeting participants contain source users and users who have been migrated to the destination, when the source and destination participants click the meeting links in the email, they will enter two different meetings.
The source tenant ID in the meeting link will be replaced with the destination information. If the meeting participants contain external users, the destination meeting organizer needs to update the meeting after the migration to update the meeting link for external users. Otherwise, when external users click the link to attend the meeting, they will be redirected to the source meeting.
When you enable the Safe Links settings for email addresses in Microsoft 365 Defender for Office 365, the source meeting links cannot be replaced with the destination information. When the external/destination user clicks the source meeting link to attend the meeting, they will wait in the lobby until the meeting organizer allows the user to enter the meeting.

If your meeting meets the situation 4, 5, or 6 above, we recommend that you do not enable the Replace meeting links with the destination information setting and configure the ChangeTeamsMeetingScopeAsEveryone=true customized feature string in the migration policy to publish the source meeting link to everyone. Also, you need to note the following:

- The **ChangeTeamsMeetingScopeAsEveryone** customized feature is unsupported when the destination is a 21Vianet.

- Make sure you have configured an app profile for the source tenant, and the app has the permissions below to publish the source meeting link:

	- Make sure you have assigned the access policy for the **AvePoint Fly** app or custom Azure app. Refer to  for details.

	- If you use a custom Azure app, make sure you have assigned the Microsoft Graph API > **OnlineMeetings.ReadWrite.All** permission to the app. 

- If destination users join the meeting via Teams on the web:

	- **Apps**, **Record and translation**, and **Meeting notes** actions will not be displayed.

	- Source organizer will be displayed as a guest and source attendees will be displayed as external users in the destination.

	- **End meeting** action will not be displayed.

	- The options in **Meeting options** and **Mute notifications** action displayed in **More** > **Settings** will not be displayed.

	- **Manage permissions**, **Download attendance list** and **Lock the meeting** actions displayed in **Participants** will not be displayed.

	- **Together mode** action in **View** is not available.

	- Destination users cannot save the meeting recording. The meeting recording saved by the source user will be displayed in the meeting chat of destination users rather than meeting files. When destination users click the recording, a window appears with the recording link. Destination users do not have permissions to access the recording via the recording link since the link is a source link.

- If destination user joins the meeting via Teams app:

	- **Rooms**, **Apps**, **Record and translation**, and **Meeting** **notes** actions will not be displayed.

	- Source organizer will be displayed as an external user in the destination.

	- **End meeting** action will not be displayed.

	- The options in **Meeting options** displayed in **More** > **Settings** will not be displayed.

	- **Manage permissions**, **Download attendance list** and **Lock the meeting** actions displayed in **Participants** will not be displayed.

	- **Together mode** action in **View** is not available.

	- Destination users cannot save the meeting recording. The meeting recording saved by the source user will be displayed in the meeting chat of destination users rather than meeting files. When destination users click the recording, a window appears with the recording link. Destination users do not have permissions to access the recording via the recording link since the link is a source link.

For whether to enable the Replace meeting links with the destination information setting in the migration policy, we have recommendations based on different migration methods:

- For big bang migrations (migrate all objects at a time), the situations above may not occur, and we recommend that you enable the **Replace meeting links with the destination information** setting to replace the source meeting link with a destination link.

- For wave-based migrations (split the migration into multiple waves), to avoid the situations above, we recommend that you do not enable the **Replace meeting links with the destination information** setting and refer to the solutions provided above.

Exchange Rule to Gmail Filter Mappings

Migration to Microsoft Teams

Migration to OneDrive

Migration to Google Drive

Migration to SharePoint Online

Migration to Google Drive

Support Lists for User Attributes

Support Lists for Group Attributes

Support Lists for Contact Attributes

Migration from Exchange Online

Notes when Replacing Meeting Links

#Migration from Exchange Online

#Notes when Replacing Meeting Links

Migration from Exchange Online

Notes when Replacing Meeting Links