#Migration from Exchange On-Premises

Refer to the table below to view the supported and unsupported object types for Exchange On-Premises Migration.

√ – Supported; × –Unsupported.

#Mailbox

Object Type	On-premises Service Account Support Status	Comment
User mailbox	√	When the usage of mailboxes exceeds storage quota, they also can be migrated.
Shared mailbox	√	When the usage of mailboxes exceeds storage quota, they also can be migrated.
Resource mailbox	√	When the usage of mailboxes exceeds storage quota, they also can be migrated.
In-Place Archive mailbox	√	If the storage space of the 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.
Linked mailbox	√

#Distribution list

Object Type	On-premises Service Account Support Status	Comment
Distribution list	×

#Folder

Folder Type	On-premises Service Account Support Status	Comment
Inbox	√
Sent Items	√
Deleted Items	√
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.
Archive	√
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	√
Junk Email	√
Contacts	√
Calendar	Partially Supported	Refer to Comment 1 below the table.
Journal	√
Recoverable Items - Deletions	√	Refer to Comment 2 below the table.
Recoverable Items - Versions	√	Refer to Comment 2 below the table.
Recoverable Items - Purges	√	Refer to Comment 2 below the table.
Recoverable Items - Audits	×	Refer to Comment 2 below the table.
Recoverable Items - DiscoveryHolds	√	Refer to Comment 2 below the table.
Recoverable Items - Calendar Logging	×	Refer to Comment 2 below the table.
Recoverable Items - SubstrateHolds	√	Refer to Comment 2 below the table.
Tasks	√	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 On-Premises 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.
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	Partially Supported	Refer to Comment 3 below the table.

Comment 1:

• The Other Calendars 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 Exchange On-Premises 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.

  • 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, and the resource names displayed in the Location of the destination calendar items and meeting requests can be updated to the destination resource display name.

Comment 2:

• The Recoverable Items folders cannot be migrated to Microsoft 365 Group mailboxes.

• Fly can only migrate DiscoveryHolds folders of Exchange 2013 SP1 or later.

Comment 3: 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

Item Type	On-premises Service Account Support Status	Comment
Email	√
Post	√
Appointment	√	Appointment is a calendar item and follows the limitations of calendars.
Meeting	Partially Supported	Meeting is a calendar item and follows the limitations of calendars.
Contact	Partially Supported	The source contacts that have been added to favorites will not be marked as favorites in the destination after the migration.
Task	√
Note	√
Journal Entry	√
Auto-complete list	Partially Supported	Refer to Comment 1 below the table.

Comment 1:

• 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 the Exchange. Refer to how the auto-complete lists features works in Outlook for Mac for more information.

• The auto-complete lists cannot be migrated to the destination when the service account/delegated app profiles' consent users does not have the ApplicationImpersonation role.

• The auto-complete lists cannot be migrated from/to archive mailboxes or Microsoft 365 Group mailboxes.

#Mailbox item property

Property Type	On-premises Service Account Support Status	Comment
Assign Policy	Partially Supported	Only the built-in archive policies and retention policies applied on emails can be migrated.
Calendar Access Rights	×
Pin/Unpin	√
Flag	√
Mark as Read/Unread	√
Follow Up	√
Category	Partially Supported	The custom categories cannot be migrated to the destination.
To-Do list	×	The property will no longer be supported due to Microsoft's changes.
Reply status of meeting participants	×

#Mailbox delegations

Delegation Type	On-premises Service Account Support Status	Comment
User mailbox	×
Resource mailbox	×
Shared mailbox	×
Distribution group	×

#Outlook settings

Setting Type	On-premises Service Account 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	Refer to Comment 1 below the table.

Comment 1:

• 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.

#Supported Exchange Service Provider and Version for Exchange On-Premises Migration

Refer to the table below to view the supported Exchange service providers and versions for Exchange On-Premises.

Service Provider	Version
1&1 IONOS	Exchange 2013
AppRiver	Exchange 2010
AppRiver	Secure Hosted Exchange 2013
Apptix	Exchange 2010
Cobweb	Exchange 2010
Cobweb	Exchange 2013
Colt Ceano	Exchange 2010
CytexOne	Exchange 2010
Exchange My Mail	Exchange 2010
Giacom	Exchange 2010
Giacom	Exchange 2013
Giacom	Exchange 2016
GoDaddy	Exchange 2010
Intermedia	Exchange 2010
MessageStream	Exchange 2010
MessageStream	Exchange 2013
mindSHIFT	Exchange 2010
OzHosting	Exchange 2010
Rackspace	Exchange 2010
Rackspace	Exchange 2013 - MEX06
Rackspace	Exchange 2013 - MEX08
Rackspace	Exchange 2016 - MEX09
SherWeb	Exchange 2016
SherWeb	Exchange 2019
SilverSky/SoftLayer	Exchange 2010/2013
VAR Dynamics	Exchange 2010
WebCentral	Exchange 2010
WebHosting.net	Exchange 2010