On-Premises Exchange In-Place Archives to Office 365 Personal (In-Place) Archives Migration Guide


This is the complete onboarding task flow for in-place archive mailboxes from On-Premises Exchange servers (versions 2007 and later) to in-place archive mailboxes on Office 365. Complete each step in the order listed. Links to corresponding Knowledge Base articles are provided.

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

If your Source server is running Exchange version 2003, or Small Business Server (SBS), refer to the Prepare Source Exchange Environment section for instructions on how to prepare your Source server for migration. On-Premises Exchange 2003 to Office 365 Migration Guide.

We recommend that the mailbox migration project is performed first, before migrating archives. For guidance, refer to the migration guide that matches your scenario. For example, if your Source server is Exchange 2007 or later, refer to On-Premises Exchange (versions 2007 and later) to Office 365 Migration Guide.

If a mailbox migration project has already been performed, the same administrative credentials that you used during your mailbox migration project can be used for this project. It is likely that you have already performed all of the steps in each section, other than the MigrationWiz Steps. Proceed to the MigrationWiz section of this guide.

MigrationWiz is a migration solution (not a synchronization solution) and will NOT propagate updates, deletes, or moves of the items previously migrated in the first migration pass because 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.

MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all Agents besides those who are Inactive can view all migrations projects. For more information, visit Project Sharing in MigrationWiz.

 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. The following Microsoft blog outlines how auto expanding archiving works in O365. https://techcommunity.microsoft.com/t5/exchange-team-blog/office-365-auto-expanding-archives-faq/ba-p/607784#  If you have additional questions, please contact BitTitan support.

A note on root migrations

Exchange migrations do not migrate from the root, as EWS only sees and migrates items contained in folders. To migrate items at the root, create a folder for these items, drag and drop the items into the folder, and then migrate as usual. 


Prepare the Source Exchange Environment

Note: If you have already completed a mailbox migration project against this Source environment, these steps will already have been completed.

  1. Set up an administrator account for migration on the Source Exchange mailbox server. How do I create an administrator account for login?
  2. EWS must be working on Source Exchange server. How do I verify if my OWA URL is correct?
  3. Test mailbox access. How do I test mailbox access?
  4. Disable the Exchange throttling policy during migration. How do I disable the throttling policy on Exchange?

    • This is only relevant for Exchange 2010+. Exchange versions 2007 and earlier do not have throttling policies.
    • If you are running Exchange 2010 and later, we highly recommend disabling the Exchange throttling policy in order to speed up your migrations.
    • Follow the instructions under Option 1 in How do I disable the throttling policy on Exchange? to disable throttling for just the admin account, rather for than all users.


Prepare the Destination Environment

Note: If you have already completed a mailbox migration project against this Source environment, these steps will already have been completed.

  1. Create an administrator account in Office 365 to be used for migration, or use the global admin account for the tenant. How do I create an administrator account in Office 365, and then use this during migration?
  2. Set up accounts on Office 365 and assign licenses. These can be created in several ways:
  3. Prepare the tenant to send and receive large mail items. How do I migrate large mail items to Office 365?


MSPComplete Steps

Note: 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.

  1. Create the customer. View, add, and edit your customers
  2. Create the Source and Destination endpoints. View, Add, and Edit Customer Endpoints
  3. Purchase User Migration Bundle licenses. 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. Refer to these articles for more information:


MigrationWiz Steps

  1. Create an In-Place Archive Migration project.
    Important: Remember that this is an in-place archive migration project. It is not a mailbox migration project. Read the How do I create a new migration project? article for more information.
  2. Add the accounts (also referred to as "items") that will be migrated to the project. How do I add items to my migration project?
  3. Set the Project Advanced Options. What project Advanced Options are available?
    • The following options are the most valuable for this migration scenario:
      • 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. What are my mailbox or archive migration options?
      • Set to use impersonation at the Destination. Checkmark the Use impersonation at Destination box. How do I migrate to Exchange or Office 365 using impersonation?
      • Set Maximum concurrent migrations. If the Source server has enough server resources, set this parameter based on the bandwidth guideline of three (3) mailboxes per 1Mbps of bandwidth. Therefore, for example, if there is a 10Mbps connection, we recommend setting the maximum concurrent migrations parameter to be 30. If the Source server has very few available server resources (e.g., it is running low on memory or it has a very high CPU utilization), we recommend setting this value to a lower number to avoid overwhelming the Source server with requests.
  4. Run Verify Credentials. How do I verify credentials?
  5. Perform a Full migration pass: Select the users > Click the Start button from the top, select Full Migration > Click Start Migration. How do I start a 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.
  6. Run Retry Errors. How do I retry failed items?
  7. Look through the user list and click any red "failed migration" errors. Review information and act accordingly.
  8. If problems persist, contact Support. How do I get support for your products?
  9. Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. How do I request statistics for my migration project?
Was this article helpful?
0 out of 2 found this helpful