Prepare the Destination Environment
Note: If you have completed a mailbox migration project against this Source environment, these steps will already have been completed.
Prepare the tenant to send and receive large mail items. KB005139
Contact Microsoft to ask to have the tenant EWS throttling limits raised for 60 days. Note: This step is only required if your Source environment will support migration speeds that are faster than the Destination. KB005493
- Create an administrator account in Office 365 to be used for migration, or use the global admin account for the tenant. KB004948
- Set up accounts on Office 365 and assign licenses. These can be created in several ways:
- Create a Personal Archive Migration project. Important: Remember that this is a personal archive migration project. It is neither a mailbox migration project, nor an Archive Migration Service project. KB005070
Add the accounts (also referred to as "items") that will be migrated to the project. KB004842
- Create the Personal Archive Migration project > Select the customer > Select the Source endpoint > Select the Destination endpoint.
Purchase licenses. From your MSPComplete Dashboard, click on Purchase > Personal Archive Migration > select MigrationWiz-Personal Archive and enter the number of licenses you wish to purchase. KB004647. Important: This type of project requires personal archive migration licenses to be purchased, NOT mailbox migration licenses. Each archive license allows up to 10GB of data to be migrated. If there are archives larger than 10GB, increase the licensing Advanced Option so that the migrations do not pause at 10GB. This option is detailed below in the MigrationWiz steps. Note: You get an accurate value of the licenses required by running the PowerShell script in KB005838.
Set the Project Advanced Options. KB004834
- Note: You can add users via the Add > Bulk Add option. You could then copy the user lists from your Source and Destination CSV files directly into the columns marked Source Email and Destination Email.
- Important: If the domain name is remaining the same, it is important to use the tenantname.onmicrosoft.com addresses for both the Source and Destination usernames, rather than the vanity names.
Run Verify Credentials. KB004511
Perform a Full migration pass: Select the users > Click on the Start button from the top, select Full Migration > Click on Start Migration. KB004938
- The following options are the most valuable for this migration scenario:
- Set to use impersonation at the Source. Checkmark the Use impersonation at Source box. KB004727
- Set to use impersonation at the Destination. Checkmark the Use impersonation at Destination box. KB004727
- Set your preferred Destination. Note: The default is to migrate into mailboxes, rather than archives, at the Destination. To change this, set Destination: Microsoft Office 365 > migrate to: Archive. KB004910
- Set the value for maximum licenses to consume per item, per pass. The default value is one license per user, which allows up to 10GB to be migrated per user. However, if a user has 28GB of data, the migration will pause at 10GB, and you will have to assign more licenses to the user. The recommended maximum number of licenses to consume per user for a personal archive migration project is five (5) licenses per user, which allows up to 50GB of data to be migrated per user. The project will only consume the number of licenses for the amount of data migrated. If a user has 28GB of data, only three out of the five licenses will be consumed, and two licenses will remain. KB004890
- If this is a large migration project, the value for Maximum concurrent migrations, under the Performance section, can be set to a very high value, e.g., 250. Note: There is no limit for this value (for cloud to cloud migrations), if using impersonation.
- If the domain name is changing at the Destination, add the following:
- Under Support/Support Options, add the following: RecipientMapping="@sourcetenantname.onmicrosoft.com->@destinationdomainname.com" KB005150
- The RecipientMapping above is just an example; do not copy this verbatim. It needs to be changed to reflect the sourcetenantname.onmicrosoft.com account name and the customer Destination domain name.
- More than one remapping expression can be used.
- This is a very important step for Office 365 to Office 365 migrations. It ensures that archived email has the ability to be replied to after migration because it will be mapped to the new Destination domain name rather than using the old sourcetenantname.onmicrosoft.com account name (which will no longer be available, once the tenant is retired).
Run Retry Errors. KB004658
Look through the user list and click on any red "failed migration" errors. Review information and act accordingly.
If problems persist, contact Support. KB004529
Click on the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. KB004626
- For archive migrations, we recommend only running a Full Pass Migration, rather than following the Pre-Stage Migration strategy (typically used with mailbox migration projects).
- Since the archive migration project is typically performed after the mailbox migration project has been completed (or at the same time), this guide does not include the steps for MX record cutover.