Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Introduction
This document provides comprehensive guidance for tenant administrators on migrating mailboxes from on-premises Exchange servers, to Microsoft 365 Primary and Archive mailboxes. Administrators will use a combination of retention policies and the autoexpanding archive feature to move mailboxes smoothly to Microsoft 365.
What do you need to know before you begin?
Tenant admins moving large amounts of Exchange user data (such as email, calendar, and contacts), defined as more than 100 GB per user, from an on-premises Exchange Server environment into Microsoft 365 comes with the following important notes:
Limitations
The maximum size of a Microsoft 365 user's stored mailbox data is 1.5 TB. This size includes the primary mailbox, the main archive mailbox, and extra archive storage space from the autoexpanding archive feature. Storing more than 1.5 TB of data for a single Microsoft 365 user isn't supported. If the on-premises user has more than 1.5 TB of data, then this data has to be split across multiple Microsoft 365 mailboxes to be onboarded to Microsoft 365.
Onboarding an on-premises archive of more than 240 GB to Microsoft 365 is currently not supported.
Deleted-item retention (also known as "single-item recovery") time in Microsoft 365 is 14 days, with a maximum of 30 days. When a mailbox is migrated to the cloud, items exceeding this time limit in mailboxes that aren't on hold are removed.
Requirements
Cloud archives must be provisioned for users in Microsoft 365 before migration.
Autoexpanding archive must be enabled at the organization level, which enables the feature for all users who are migrated. Review the "considerations and limitations" and "Outlook requirements" sections in this article and "before you enable autoexpanding archiving" in the Enable autoexpanding Archive article.
When a mailbox is on legal hold on-premises, administrators need to ensure that on-premises holds are synced to Microsoft 365 and that the target MailUser objects of users who are being migrated have the required hold state.
Performance
Before beginning a migration of any mailbox, but particularly for large mailboxes, be familiar with the concepts and recommendations in the Microsoft 365 email migration performance and best practices guide.
Retention policies are used to relocate data when needed to reduce the size of primary mailboxes. Administrators need to include time required to plan retention policies and for those policies to relocate data to the cloud.
The following advice can be used to tune the quantity and interval of items processed by the Exchange Lifecycle service:
To increase the number of items moved to the cloud archive during each run of the Exchange Lifecycle, or "ELC", process, set this registry value on every on-premises back-end Exchange server: SYSTEM\CurrentControlSet\Services\MSExchange MRM\Parameters\MoveToArchiveTotalCountLimit to 10000 and restart the MSExchangeAssistants service. (The default is 2000.)
For priority or VIP mailboxes, tenant admins can choose to run the Start-ManagedFolderAssistant command no more often than once every hour. This action creates more ELC work runs that move up to 10,000 more items. Admins may also change the ELC work cycle to process mailboxes every 8 hours. (This setting affects all mailboxes on the specified servers, which may have a performance impact, and the default is once per day.)
Beginning the migration
Once an archive is provisioned in the cloud for a user who is being migrated, tenant admins use retention policies to move content into that cloud archive to reduce the size of the primary mailbox under 100 GB. Tenant admins must consult with their compliance or legal teams to determine company policies on length of time for retention of items in the primary mailbox.
When a recoverable item is moved to an archive, a user can't restore it using the "recover deleted item" feature in Outlook/OWA on the primary mailbox. Tenant admins need to set their retention policies for recoverable items to move only items older than the deleted item retention setting on-premises so users keep using this feature as expected.
Migrating users without an on-premises archive
More than 100 GB but less than 240 GB of mailbox content
For users whose mailboxes don't have an on-premises archive and the mailbox is over 100 GB but less than 240 GB, follow these steps:
Create a retention policy that moves recoverable items from the user's on-premises mailbox to a new cloud archive where the autoexpanding feature is enabled.
If this action reduces the on-premises mailbox under 100 GB, perform a regular migration of the user's on-premises mailbox to the cloud. (If it doesn't, use retention policies to move items from the user's primary mailbox to the cloud archive to reduce the primary mailbox under 100 GB, then perform a regular migration.)
More than 240 GB of mailbox content
For users whose mailboxes don't have an on-premises archive and are over 240 GB, follow these steps:
- Create a retention policy that moves recoverable items from the user's on-premises mailbox to a new cloud archive where the autoexpanding feature is enabled.
- Use retention policies to move items from the user's primary mailbox to the cloud archive to reduce the primary mailbox under 100 GB.
- Once the on-premises primary mailbox total size is under 100 GB, perform a regular migration of the user's primary mailbox to the cloud.
Users with an on-premises archive
Primary mailbox more than 100 GB of content and archive less than 240 GB
Reminder: On-premises archive mailboxes larger than 240 GB cannot be migrated to Microsoft 365 using the existing tools in the service.
For users whose mailboxes do have an on-premises archive and the primary mailbox is over 100 GB and the on-premises archive is under 240 GB, follow these steps:
- Migrate the user's on-premises archive to the cloud, ensuring that autoexpanding is enabled.
- Use retention policies to move all recoverable items from the primary mailbox to the user's cloud archive, along with enough regular items from the primary mailbox to reduce the primary mailbox size under 100 GB. Do this step once the archive migration is complete.
- Once sufficient items are moved to the cloud archive, perform a regular migration of the user's primary mailbox to the cloud.