This document will walk you through the environment preparation and MigrationWiz steps necessary to perform your migration from one Microsoft 365 Personal Archives instance to another Microsoft 365 Personal Archives instance. 

First migration?

If this is your first time performing a migration, we have created a Migration Planning & Strategy Guide to walk you through planning, set-up, and general migration best practices.

Limitations

MigrationWiz is a migration tool, not a syncing tool. If changes are made at the source after migration, they will not sync to the destination, nor will changes made at the destination sync to the source. We do not have “live” monitoring of changes (as with a sync agent) and we cannot handle scenarios such as conflict resolution without user interaction.

We are not able to support migrations with two-factor or multifactor authentication. 

The maximum individual file size supported by MigrationWiz is 60GB.

Items located in the root folder of the mailbox are not migrated.

Below is a list of items that will and will not be migrated. Note that these items frequently change, so review this list before any and all migration projects.

Important: If the In-Place Archive mailbox being migrated is more then 100 GB in size and auto expanding archiving is enabled for the In-Place Archive mailbox in the destination tenant, the migration may take 30 days or more to complete due to the auto expanding archiving process not making space available immediately in the destination archive mailbox when moving data. Microsoft outlines how auto expanding archiving works in Microsoft 365. If you have additional questions, please contact BitTitan support.

Prepare the Source Exchange Environment

If you have completed a mailbox migration project against this Source environment, these steps will already be complete.

1. Create an administrator account in Microsoft 365 to be used for migration or use the global admin account for the tenant.
2. (Optional) Export a list of users from the source tenant. This will be used to import the users to be migrated into the migration project. You can find instructions to export a list of active users here: Microsoft 365 Reports in the Admin Center – Active Users. The report can be exported as a CSV. You can then edit the CSV to add or remove users as needed.

Prepare the Destination Environment

If you have already completed a mailbox migration project against this Source environment, these steps will already have been completed. If not, create an administrator account in Microsoft 365 to use for this migration, or use the global admin account for the tenant. 

Set up accounts

Set up accounts on Microsoft 365 and assign licenses. These can be created in several ways:

• • Manually, one at a time. Microsoft instructions to add users individually
  • By bulk import, via CSV file. Microsoft instructions to bulk add users
  • By PowerShell script. TechNet article

MSPComplete Steps

If you have already completed a mailbox migration project against this Source environment, these steps will already have been completed. The endpoints that were created for your mailbox migration project can be used for your in-place archive migration project.

Create Customer

1. Click the Add button in the top navigation bar
2. Click the Add Customer button on the All Customers page
3. In the left navigation pane, select the appropriate workgroup and then click All Customers.
4. Click Add Customer.
5. Enter the new customer’s information in the Add Customer form. Primary Email Domain and Company Name are required. The rest are optional.
6. Click Save.
7. Repeat steps 1 through 4 for each customer you want to add. 

Purchase licenses

A User Migration Bundle license is required for this migration scenario.. User Migration Bundle licenses allow multiple types of migrations to be performed with a single license. They also allow DeploymentPro to be used to configure Outlook email profiles. For questions on licensing, visit MigrationWiz Licenses

To purchase licenses:

1. Sign in to your BitTitan account. 
2. In the top navigation bar, click Purchase.
3. Click the Select button and choose User Migration Bundle licenses.
4. Enter the number of licenses you want to purchase. Click Buy Now.
5. Enter a Billing address if applicable.
6. Click Next.
7. Review the Order Summary and enter a payment method.
8. Click Place Your Order.

MigrationWiz Steps

Create a Migration Project

Create a Personal Archive Migration project.

1. Click the Go to My Projects button.
2. Click the Create Project button.
3. Select Personal Archive Migration Project.
4. Click Next Step.
5. Enter a Project name and select a Customer.
6. Click Next Step.

Endpoints

You may either select an existing endpoint or create a new one. 

If you are selecting existing endpoints, use Office 365 for both the source and destination. 

To create a new source endpoint:

1. 1. Click New
   2. Name endpoint
   3. Select type Office 365
   4. Provide credentials.
   5. Click Add
   6. Click Next Step
2. Select or create a new destination endpoint.
3. To create a new destination endpoint:
   1. Click New
   2. Name endpoint
   3. Select type Office 365
   4. Provide credentials.
   5. Click Add
4. Click Next Step
5. Click Save and Go to Summary.

Add Users

Important: If the domain name will remain the same, use the tenantname.onmicrosoft.com addresses for both the Source and Destination usernames.  If the accounts are added with the vanity domains, use the Change Domains button at the top of the project to change the domains to the onmicrosoft domain.

Add Users

Add the user accounts that will be migrated to the project. This may be done in several ways, depending on the size of the project. Steps for each option are in the accordion below, simply click to show the option you select and follow the guidance there.

Small Migrations:

For small migrations, it is easy to add users one-at-a-time using Quick Add. The steps for this are below. 

Larger Migrations:

For larger migrations, we recommend either using the Autodiscover or Bulk Add option.

Autodiscover will add all users found on the source tenant. This can then be edited in the project to remove users not being migrated. All users will be added with the source and destination email addresses set to match the source email. This can be changed by using the Change Domain Name button at the top of the project page. If the usernames are changing during the migration, we recommend using the Bulk Add option.

Bulk Add uses a CSV containing the source and destination email addresses for the users to add the users to the project. If migrating only a specific group from a tenant, we recommend using the Bulk Add option.

Set the Project Advanced Options 

The following options are the most valuable for this migration scenario:

• Checkmark the Use impersonation at Source
• Checkmark the Use impersonation at Destination
• IMPORTANT: Set your preferred Destination. The default is to migrate into the primary mailbox, not the archive mailbox at the Destination. To change this, set Destination: Microsoft Office 365 > migrate to: Archive under the Source/Destination in the advanced options of the project.
• 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. There is no limit for this value (for cloud to cloud migrations), if using impersonation.

Recipient Mapping

This is a required step for this type of migration. There are two variations of this option:

1) If the domain is remaining the same in the new destination tenant, use: "RecipientMapping=@sourcetenantname.onmicrosoft.com->@destinationdomainname.com" (replace @sourcetenantname and @destinationdomainname with your domains). 

2) If the domain is changing in the new destination tenant, use: "RecipientMapping=@sourcedomainname->@destinationdomainname" (replace @sourcetenantname and @destinationdomainname with your domains). 

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 Microsoft 365 to Microsoft 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 Verify Credentials

1. ​Sign in to your MigrationWiz account​.
2. Open the Project containing items you wish to validate​.
3. Select the items you wish to validate.
4. Click on the Start button in your dashboard.
5. Select Verify Credentials from the drop-down list.

Once complete, the results of the verification will be shown in the Status section.​ 

Notify Users

Notify users that a migration is occurring. Send email to all users telling them the time and date of the migration.

Run Migration

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.

Full pass

1. Select the users
2. Click the Start button from the top
3. Select Full Migration
4. Click Start Migration

Run Retry Errors

Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.

If problems persist, contact Support.

Request Statistics

Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics.