Migration Manager provides tools for seamless migration to Microsoft Office 365 from on-premises Exchange environment.
We assume that you are familiar with Migration Manager concepts described in the Migration Manager Installation Guide, and that you have already installed the product, following the instructions provided in that guide. It is also recommended that you read the release notes for the current version of Migration Manager. The release notes contain information about specific product behavior, limitations, known issues, and workarounds that may be useful for planning and performing your migration.
For information which types of source Exchange environments are supported, see Cloud Migration subsection of Source and Target Exchange Organizations.
Migration Manager supports various scenarios of migrating your messaging infrastructure to Microsoft Office 365. This topic describes a basic migration when messaging infrastructure is completely moved to Microsoft Office 365.
Note: Migration Manager supports various cloud migration scenarios that involves hybrid deployments. For detailed information how to implement them, see Hybrid Migration Scenarios.
The basic migration to Microsoft Office 365 consists of the following main stages:
TIP: If you plan to implement Single Sign-On (SSO) for Microsoft Office 365, or you already use Microsoft Azure AD Connect to synchronize user accounts with Microsoft Office 365, review information in the Advanced Migration Topics section.
The table below describes the steps that you need to perform in each stage of migration and the results that you get after you complete those steps.
|Stage||What to Do||Result||Tool to Use|
|1||Both source Exchange and Microsoft Office 365 environments are ready for migration||N/A|
||Migration Manager for Active Directory (Microsoft Office 365) console|
|3||Calendars including users' free/busy information are kept in sync with Microsoft Exchange Online.||Migration Manager for Exchange console|
|4||Public folders are kept in sync with Microsoft Office 365.||Migration Manager for Exchange console|
||Migration Manager for Exchange console|
The following mailbox attributes are migrated to Microsoft Office 365:
NOTE: See the Mailbox Permissions Processing Considerations topic below for more details on mailbox permission migration.
|Migration Manager for Active Directory (Microsoft Office 365) console|
||Client Profile Updating Utility for updating Outlook profiles|
If your Exchange organization is deployed in an Exchange resource forest then consider the following:
Migration Manager can synchronize mailbox permissions and the Send As permission during synchronization and migration to Microsoft Office 365. So if a source user can send mail messages as another user account and/or manage mailboxes of other users, the corresponding target user will have the same rights.
Take into account the following:
For uninterrupted user collaboration during the migration to Microsoft Office 365, users in source Exchange organization and Microsoft Office 365 should see other users’ mailboxes in their Global Address Lists (GALs). All mail sent to the user should arrive to the mailbox he or she is currently using, no matter which mailbox it was sent to. To achieve this, mail should be automatically forwarded to the currently-used mailbox from the other mailbox. For that, Migration Manager establishes mail redirection between source Exchange servers and Microsoft Office 365 using the Migration Manager for Active Directory redirection technology as follows:
The process of mail redirection is fully automated by Migration Manager for Active Directory; therefore no additional configuration activities are required to be performed.
Before you start the migration, read the following:
Recommendation: Subscribe to Microsoft Office 365 in Advance
If you do not already have a Microsoft Office 365 account, consider signing up at http://office.microsoft.com before you start migration preparations. This will help avoid delays and interruptions during migration.