Export to PST Migration Guide


This is the complete onboarding task flow for exporting either regular mailboxes or in-place archive mailboxes to PST (Portable Storage Table) files. Complete each step in the order listed. Links to corresponding Knowledge Base articles are provided.

For this scenario, the Destination is a Bring Your Own storage container on Azure. This will hold all of the PST files after the mailboxes have been exported to PST. The export of the selected mailboxes will be saved, in the Azure container, as one or more PST files per user mailbox. BitTitan Azure Storage is only available as a Source endpoint for PST migration.

A new PST will be created for every 10GB of data in a mailbox. This increases the export speed and leads to efficiency improvements.

Which items are migrated with MigrationWiz?

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. 

Prepare the Source Environment

Note: If your Source server is running Exchange version 2003, or Small Business Server (SBS), refer to the Prepare the Source Environment section in the On-Premises Exchange 2003 to Office 365 Migration Guide.

  1. If your migration requires it, set up an administrator account for the migration.
  2. If your Source is Exchange, EWS must be working on the Source Exchange server. Read the How do I verify if my OWA URL is correct? article for more information.
  3. Test mailbox access. Read the How do I test mailbox access? article for more information.
  4. Disable the Exchange throttling policy during migration. Read the How do I disable the throttling policy on Exchange? article for more information.
    • This is only relevant for Exchange 2010+. Exchange versions 2007 and earlier do not have throttling policies.
    • Follow the instructions under Option 1 in the How do I disable the throttling policy on Exchange? article to disable throttling for just the admin account, rather for than all users.


Prepare the Destination Environment

  1. Estimate Azure storage costs.

    This step is optional, but it is useful in order to provide the customer with upfront storage costs ahead of time. Read the Estimate Azure Storage costs for migrations article for more information.
  2. Buy an Azure subscription (or use the free one-month trial, and be aware that this option is only viable if you are performing a very small migration). Read the How do I buy an Azure subscription? article for more information.
  3. Create an Azure storage account, and take note of the Storage Account Name and the Primary Access Key (in Azure, from the storage screen, click Manage Access Keys at the bottom of the screen). These will be needed when creating your Destination endpoint in MSPComplete.
    Note: There is no need to create any Azure containers for this migration. If you do create your own container, it must be a public container, and the name should not contain any spaces. Read the What are some best practice tips when creating a container in Azure? article for more information.


MSPComplete Steps

  1. Create the customer. Read the View, Add, and Edit Your Customers article for more information.
  2. Create the Source and Destination endpoints. Read the View, Add, and Edit Customer Endpoints article for more information.
    • For the Source endpoint:
      • Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select Exchange Server 2003+.
      • Enter the EWS URL. 
      • Click the Provide Credentials radio button, and enter the admin account credentials for the account that was set up under the "Prepare the Destination Environment" section of this guide.
    • For the Destination endpoint:
      • Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type,select PST.
      • Enter the Storage Account Name.
      • Enter the Access Key.
  3. Purchase User Migration Bundle licenses. User Migration Bundle licenses allow multiple types of migrations to be performed with a single license. Refer to these articles for more information:

MigrationWiz Steps

  1. Create the Mailbox Migration project or Archive Migration project (depending on whether you are exporting regular or in-place archive mailboxes to PST). Read the How do I create a new migration project? article for more information.
    • Create the Mailbox Migration Project or In-Place Archive Project > Select the customer > Select the Source endpoint > Select the Destination endpoint.
      Note: If you are migrating a mixture of regular mailboxes and in-place archive mailboxes, create one mailbox migration project and one archive project.
  2. Add the accounts, also referred to as "items", that will be migrated to the project. Read the How do I add items to my migration project? article for more information.
    • The Source will be the STMP address for each mailbox.
    • The Destination will be the name that you want for the PST file. It must include .pst at the end of each entry. A good format to follow is to name each file after the username that the PST file will belong to, e.g., user1.pst, user2.pst.
  3. Set the Project Advanced Options. Read the What project Advanced Options are available? article for more information.
    • The following options are the most valuable for this migration scenario:
      • Destination: PST > Container Name = migrationwiz.
        • If you did not create your own Azure container when preparing your Destination environment, this can be left as is, and the PST files will be exported to a container named "migrationwiz".
        • If you created an Azure container with a different name, this entry must be changed to match the name of your container.
  4. Run Verify Credentials. Read the How do I verify credentials? article for more information.
  5. Perform export. Select the users > Click the Start button from the top > Select Full Migration > Click Start Migration. Read the How do I start a migration? article for more information.
  6. Run Retry Errors. Read the How do I retry failed items? article for more information.
  7. Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.
  8. If problems persist, contact Support. Read the How do I get support for your products? article for more information.
  9. Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. Read the How do I request statistics for my migration project? article for more information.


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