Home > Exchange Migration > Migration from Exchange On-Premises
Export to PDFMigration from Exchange On-Premises
Refer to the table below to view the supported and unsupported object types for Exchange On-Premises Migration.
√ – Supported; × –Unsupported.
| Object Type | Object Type | Object Type | On-premises Service Account Support Status | Comment |
|---|---|---|---|---|
| Mailbox | ||||
| User mailbox | User mailbox | √ | When the usage of mailboxes exceeds storage quota, they also can be migrated. | |
| Mailbox | ||||
| Shared mailbox | Shared mailbox | √ | When the usage of mailboxes exceeds storage quota, they also can be migrated. | |
| Mailbox | ||||
| Resource mailbox | Resource mailbox | √ | When the usage of mailboxes exceeds storage quota, they also can be migrated. | |
| Mailbox | ||||
| In-Place Archive mailbox | 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. | |
| Mailbox | ||||
| Linked mailbox | Linked mailbox | √ | ||
| Distribution list | Distribution list | Distribution list | × | |
| Folder | Inbox | Inbox | √ | |
| Folder | Sent Items | Sent Items | √ | |
| Folder | Deleted Items | Deleted Items | √ | |
| Folder | 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. |
| Folder | Archive | Archive | √ | |
| Folder | Conversation History | Conversation History | √ | |
| Folder | Notes | Notes | √ | |
| Folder | RSS Subscriptions | RSS Subscriptions | √ | Only the RSS Subscriptions folders can be migrated to the destination. The items in RSS Subscriptions folders cannot be migrated. |
| Folder | Custom Folder | Custom Folder | √ | |
| Folder | Junk Email | Junk Email | √ | |
| Folder | Contacts | Contacts | √ | |
| Folder | Calendar | Calendar | Partially Supported | 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. However, the resource names displayed in the Location of the destination calendar items and meeting requests are still the source names. |
| Folder | Journal | Journal | √ | |
| Folder | Recoverable Items folders | Deletions | √ | The Recoverable Items folders cannot be migrated to Microsoft 365 Group mailboxes.Fly can only migrate DiscoveryHolds folders of Exchange 2013 SP1 or later. |
| Folder | Recoverable Items folders | Versions | √ | The Recoverable Items folders cannot be migrated to Microsoft 365 Group mailboxes.Fly can only migrate DiscoveryHolds folders of Exchange 2013 SP1 or later. |
| Folder | Recoverable Items folders | Purges | √ | The Recoverable Items folders cannot be migrated to Microsoft 365 Group mailboxes.Fly can only migrate DiscoveryHolds folders of Exchange 2013 SP1 or later. |
| Folder | Recoverable Items folders | Audits | × | The Recoverable Items folders cannot be migrated to Microsoft 365 Group mailboxes.Fly can only migrate DiscoveryHolds folders of Exchange 2013 SP1 or later. |
| Folder | Recoverable Items folders | DiscoveryHolds | √ | The Recoverable Items folders cannot be migrated to Microsoft 365 Group mailboxes.Fly can only migrate DiscoveryHolds folders of Exchange 2013 SP1 or later. |
| Folder | Recoverable Items folders | Calendar Logging | × | The Recoverable Items folders cannot be migrated to Microsoft 365 Group mailboxes.Fly can only migrate DiscoveryHolds folders of Exchange 2013 SP1 or later. |
| Folder | Recoverable Items folders | SubstrateHolds | √ | The Recoverable Items folders cannot be migrated to Microsoft 365 Group mailboxes.Fly can only migrate DiscoveryHolds folders of Exchange 2013 SP1 or later. |
| Folder | Tasks | 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. |
| Folder | 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. |
| Folder | Search Folders | Search Folders | × | Search folders are virtual folders that do not contain any actual items. |
| Folder | Snoozed | Snoozed | √ | |
| Folder | Hidden folder | Hidden folder | 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 | √ | |||
| Mailbox item | Post | Post | √ | |
| Mailbox item | Appointment | Appointment | √ | Appointment is a calendar item and follows the limitations of calendars. |
| Mailbox item | Meeting | Meeting | Partially Supported | Meeting is a calendar item and follows the limitations of calendars. |
| Mailbox item | Contact | Contact | 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 | √ | |
| Mailbox item | Note | Note | √ | |
| Mailbox item | Journal Entry | Journal Entry | √ | |
| Mailbox item | Auto-complete list | Auto-complete list | 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 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 | Assign Policy | Assign Policy | Partially Supported | Only the built-in archive policies and retention policies applied on emails can be migrated. |
| Mailbox item property | Calendar Access Rights | Calendar Access Rights | × | |
| Mailbox item property | Pin/Unpin | Pin/Unpin | √ | |
| Mailbox item property | Flag | Flag | √ | |
| Mailbox item property | Mark as Read/Unread | Mark as Read/Unread | √ | |
| Mailbox item property | Follow Up | Follow Up | √ | |
| Mailbox item property | Category | Category | Partially Supported | The custom categories cannot be migrated to the destination. |
| Mailbox item property | To-Do list | To-Do list | × | The property will no longer be supported due to Microsoft’s changes. |
| Mailbox item property | Reply status of meeting participants | Reply status of meeting participants | × | |
| Mailbox delegations | User mailbox | User mailbox | × | |
| Mailbox delegations | Resource mailbox | Resource mailbox | × | |
| Mailbox delegations | Shared mailbox | Shared mailbox | × | |
| Mailbox delegations | Distribution group | Distribution group | × | |
| Outlook settings | Outlook configuration | User profiles | × | |
| Outlook settings | Outlook configuration | Signatures | × | |
| Outlook settings | Email forwarding | Email forwarding | × | |
| Outlook settings | Outlook quick action setting | Outlook quick action setting | × | |
| Outlook settings | Automatic Replies (Out of Office) settings | Automatic Replies (Out of Office) settings | √ | |
| Outlook settings | Inbox rules | Inbox rules | 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. |
On this page