Microsoft 365 Personal Archives to Microsoft 365 Personal Archives Migration Guide

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.


  • 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.
  • App password usage and MFA/2FA are not supported for the admin account being used for this endpoint. 
  • The maximum individual file size supported by MigrationWiz is 60GB.
  • Items located in the root folder of the source primary mailbox are not migrated. Only items located in the source archive mailbox are migrated.
  • Exchange Web Services (EWS) must be enabled for the mailboxes in the Exchange Online tenant for this migration type


If the In-Place Archive mailbox being migrated is more than 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.

More information on how auto-expanding works with archive mailboxes can be found outlined by Microsoft here: Office 365: Auto-Expanding Archives FAQ
If you have additional questions, please contact BitTitan support.

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 migration projects.

Which items are migrated?
  • Inbox
  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks
  • Journals
  • Notes
  • Server-Side Rules
  • Folder Permissions
  • Post (when the destination is Exchange or Microsoft 365)
Which items are not Migrated?
  • Safe Sender/Block Lists
  • In-line images in Tasks
  • Calendar acceptance status emails

Modern Authentication Requirements

The steps listed in the Obtain Client and Tenant ID Settings for Mailbox and Exchange Online Migrations section of the Authentication Methods Migrations KB apply to both the source and destination tenant when they are Exchange Online, in regards to Exchange Web Services (EWS) in mailbox, archive mailbox, and public folder projects. Use a Global Administrator for the configuration steps.

Please review the documentation before preparing both the source and the destination.

Prepare the Source Exchange Online Environment

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

  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 Exchange Online 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:

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.

Purchase licenses by following the next steps:

  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 are now created through MigrationWiz, rather than through MSPComplete. The steps for this section outline how to create the endpoints in MigrationWiz.

If you are selecting an existing endpoint, keep in mind that only ten endpoints will show in the drop-down. If you have more than ten, you may need to search. Endpoint search is case and character-specific. For example, Cust0mer will not show up if the search is "customer". We recommend keeping a list of endpoints you have created, along with any unique spellings or capitalization you may have used.

You may either use existing endpoints (if ones for your mailbox project already exist) or create new ones.

Create a New Endpoint

Perform these steps for both the source and destination endpoints

  1. Click New.
  2. Name the endpoint (It is highly recommended to create a unique name for your source and destination endpoints) 
  3. Under Endpoint Type, select the endpoint from the options below that corresponds with the type of Microsoft 365 tenant being used:
    • Microsoft 365 - (This is also used for GCC Commercial tenants)
    • Microsoft 365 (China)
    • Microsoft 365 (Germany)
    • Microsoft 365 (US Government) - (Use this for GCC High tenants only)
  4. Enter the administrator username and password in the fields. This should be the corresponding global admin or the admin created in the steps for preparing the source or destination. 
  5. Click Add. 
  6. Complete the Application (client) ID and the Directory (tenant) ID fields.
    Source Settings.png
  7. Click Next Step.
  8. Click Save and Go to Summary.


Do not forget to complete the client ID and the tenant ID fields, otherwise, you cannot save your project migration.

Once the information has been provided for both, the source and/or destination endpoint, and the customer selects Save and Go to Summary, MigrationWiz performs an endpoint validation check.

This validation tests the administrator credentials entered into the project and the Modern Authentication setup only. If there is an issue, the screen redirects to the endpoint and provides an error message or flyout that can be selected for more information regarding the error.

Common Errors when Configuring Your Endpoint

For more information, review the AADSTS700016, AADSTS90002, and ADDSTS50126 issues on the Common Errors Using Modern Authentication page.

Add Users


If the domain name is migrated to the new destination tenant, it is strongly recommended that users in the migration project be migrated using the domain names for both the source and destination email addresses, rather than using the vanity domain. To do this, add the users using their Vanity Domain and once they are in the project, select all the users and click the Change Domains option in the menu to bulk change them to using the domain. 

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. The Autodiscover option is not available for this migration type.

Small Migrations

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

Larger Migrations

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

Quick Add
This option allows you to add items one at a time. To do so, you only have to provide an email address if you entered administrative credentials when setting up the project. If you did not, enter the following user information:
  • An email address
  • Login name
  • Password
  • Mailbox status
Bulk Add

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.

MigrationWiz allows you to bulk import mailboxes into the system.

To import one or more mailboxes:

  1. Sign in to your MigrationWiz account.
  2. Select the Project for which you want to perform the bulk import.
  3. Click on Add.
  4. Click on Bulk Add.
  5. Follow the instructions on the page.

Advanced Options

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

Support Tab

Required Settings

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

  • If the domain remains the same in the new destination tenant, use: ">" (replace @sourcetenantname and @destinationdomainname with your domains). 
  • 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 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 can be replied to after migration because it will be mapped to the new Destination domain name rather than using the old account name (which will no longer be available, once the tenant is retired).

Default Options

The client and tenant ID fields for source and destination in the Support tab of the project’s Advanced Options, are view-only fields. This means that you cannot edit or remove them from the support options page. To edit them,  you need to edit the project.

Advanced Options.png


You cannot update the default Advanced Options, in case you try to modify or add new ones the following message arises.
Duplicate Support Option.png

Source/Destination Tab

  • Checkmark the Use impersonation at Source
  • Checkmark the Use impersonation at Destination


    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.

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 an 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.

Was this article helpful?
1 out of 4 found this helpful