Skip Ribbon Commands
Skip to main content

On-Premises Exchange Personal Archives to Office 365 Personal Archives Migration Guide

Last Update: 7/21/2017 11:29 AM
This article has been moved to our new Help Center. Please update your bookmarks.

​On-Premises ​​​​Exchange Personal Archives to Office 365 Personal Archives Migration Guide

Important: When you sign in to MigrationWiz, you are redirected to the Getting Started page in MSPComplete. To go to a migration project created before April 4, 2017, click the Go to Projects button on the Getting Started Page. To create a new project for the migration scenario documented in this article, go to the Delivery Center and add an Archive: Exchange Personal Archives to Office 365 Personal Archive ​service to the customer. Read the Delivery Center article for more information about adding services to a customer.​


  • This is the complete onboarding task flow for personal archive mailboxes from On-Premises Exchange servers (versions 2007 and later) to personal archive mailboxes on Office 365.
  • Complete each step in order. Links to corresponding Knowledge Base articles are provided.
  • 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. KB004965.
  • 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 KB005903.
  • 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, and it is likely that you have already performed all of the steps in each section, other than the MigrationWiz Steps. In that case, proceed to the MigrationWiz section of this guide.

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.  KB004725
  2. EWS must be working on Source Exchange server. KB004392
  3. Test mailbox access. KB004616
  4. Disable the Exchange throttling policy during migration. KB004945

    • 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 KB004945 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. KB004948
  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. KB005139
  4. 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

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 personal archive migration project.

  1. Create the customer. KB005421
  2. Create the Source and Destination endpoints. KB005427

MigrationWiz Steps

  1. 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
    • Create the Personal Archive Migration project > Select the customer > Select the Source endpoint > Select the Destination endpoint.
  2. Add the accounts (also referred to as "items") that will be migrated to the project. KB004842
  3. Purchase licenses. From your MSPComplete dashboard, click on Purchase > Personal ArchiveMigration > select MigrationWiz-Personal Archive and enter the number of licenses you wish to purchase. KB004647Important: 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.
  4. Set the Project Advanced Options. KB004834
    • 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: ArchiveKB004910
      • Set to use impersonation at the Destination. Checkmark the Use impersonation at Destination box. KB004727
      • 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
      • 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.
  5. Run Verify Credentials. KB004511
  6. Perform a Full migration pass: Select the users > Click on the Start button from the top, select Full Migration > Click on Start Migration. KB004938
    • Notes:
      • 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.
  7. Run Retry Errors. KB004658
  8. Look through the user list and click on any red "failed migration" errors. Review information and act accordingly.
  9. If problems persist, contact Support. KB004529
  10. Click on the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. KB004626