When migrating mailboxes to Exchange Server 2013/2016/2019, consider the following:
Mailbox migration to the target environment is transparent. It is recommended to start mailbox migration after the domain and directory migration is completed and after the public folder data is copied to the target environment.
Calendar and free/busy synchronization should be started simultaneously with mailbox migration to enable users to work without interruption during the coexistence period.
|
NOTE: The scenario involving migrating users from Active Directory to Microsoft Office 365 and their mailboxes from the on-premises Exchange organization to Microsoft Exchange Online is described separately in the Migrating To Microsoft Office 365 document included in the Migration Manager documentation set. |
To begin mailbox migration, right-click the Mailbox Synchronization node in the management tree and click Add Mailbox Synchronization Job. This opens a dialog box that lets you select one of the following methods to synchronize mailboxes:
The guidelines for choosing the right type of job are in the Mailbox Migration Process topic.
|
NOTE: Office 365 mailbox migration is described in the dedicated Migrating to Microsoft Office 365 document. |
You can track the mailbox migration progress using the Statistics dashboard. For information on how to do that, see Tracking the Migration Progress.
A mailbox synchronization job is currently the only method for migrating mailboxes to Microsoft Exchange 2010 (only for migration from Exchange 2010 or later by MAgE), Exchange 2013 or higher.
Specify the source organization where the mailboxes need to be synchronized and the credentials to use for performing the synchronization operations. You can specify a single set of credentials for working with both Active Directory and Exchange, or two distinct sets of credentials.
Specify the target Exchange organization where the mailboxes need to be synchronized and the credentials to use for performing the synchronization operations. You can specify a single set of credentials for working with both Active Directory and Exchange, or two distinct sets of credentials.
Specify the notification messages that will be sent to the old and new mailboxes involved in the migration. Use the default notification messages or customize them as necessary.
The Migration Agent for Exchange is used for performing direct mailbox synchronization operations. This step lets you set up the agent on an agent host that you select.
The default installation path is in the hierarchy of the Program Files system folder. You can customize the path, but your custom path will be used only if there are no previously installed instances of the Migration Agent for Exchange on the computer. Otherwise, the agent will be installed to the same location as the other existing instances regardless of the path you specify.
You can also override the default credentials that the agent will use. However, note that in this case you will be changing the credentials not only for the agent instance you are installing, but also for any existing agent instances on the agent host.
To change the original settings you specified during mailbox synchronization job creation, open the properties of the job.
To create a new mailbox collection for an existing mailbox synchronization job, right-click the job in the management tree and click Add Collection.
This will start the Add Mailbox Collection Wizard, which will help you to set up and configure a new collection for the mailbox synchronization job. Each step of the wizard is described below.
Specify the following general options:
Here, you can explicitly specify the target mailbox database where you want this collection's mailboxes to reside.
Select one of the following:
When processing the collection Migration Manager will attempt to follow the schedule you specify on this page. By default, the option to Start as soon as possible is selected. Change this if you want to specify a date when the collection processing should be started.
Do one of the following:
The collection can be populated with user accounts, groups and organizational units. To change the item list, use the buttons next to it.
|
NOTE: Migration Manager for Exchange does not process groups nested in organizational units (OUs). |
The final step in mailbox migration is to switch to the target mailbox, making it the primary mailbox for the user. You can select to perform this step automatically and specify a schedule for it.
However, you may want to defer this step in case there are problems and perform the switch manually when you have made sure the mailboxes are ready.
You can also select to skip automatic switching for mailboxes with corrupted messages and set a threshold value for the number of corrupted messages. This allows you to manually investigate such mailboxes to make sure nothing of value is lost, and later complete their migration manually.
To change the original settings you specified during mailbox collection creation, open the properties of the collection.
After you created collection, you can configure filter settings that let you exclude from migration certain message classes and/or messages that are older than a specified number of days. For that, open Properties of the collection, select the Filters node in the dialog box that appears, and specify message classes to be excluded from the migration scope.
You have two options to exclude specific message class from the scope:
|
Caution: Use separate line for every message class. |
Use the following syntax for message classes:
|
NOTE:
|
When specifying filters for a collection, consider the following:
To apply filters for already migrated items you need to perform resynchronization of the mailbox. Note that messages filtered out at source will be deleted from the target mailbox.
|
NOTE: After mailbox is switched, Migration Agent for Exchange continues synchronizing mail data from the source to the target mailbox to ensure that the most recent messages are successfully migrated to the target mailbox. Therefore, before removing mailbox from the collection after switch, check that mailbox was not processed during last migration session according to its Last Processed Time value. |
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy