Prepare the Azure Environment
- Estimate Azure storage costs. This step is optional, but is useful in order to provide the customer with storage costs ahead of time. For guidance, see Estimate Azure Storage costs for migrations.
- 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). For guidance, see How do I buy an Azure subscription?
- Create an Azure storage account, and take note of the Storage Account Name and the Primary Access Key. (Log in to: https://manage.windowsazure.com > Click Storage > click Manage Access Keys at the bottom of the screen.) These need to be entered when creating the MSPComplete Source endpoint. We recommend that you create an Azure Storage Account in the same Microsoft data center as the Destination Office 365 tenant. For guidance, see How do I create an Azure Storage Account?
- Create an Azure BLOB container. Take note of the name of the BLOB to be entered in the Bucket Name field in the project advanced options. For guidance, see Best practices when crating an Azure container
Prepare Destination Office 365 Environment
Note: If you have already completed a mailbox migration project against this Source environment, these steps will already have been completed.
Prepare the tenant to send and receive large mail items. For guidance, see How do I migrate large mail items to Office 365?
- Create an administrator account in Office 365 to be used for migration, or use the global admin account for the tenant. For guidance, see Create an Office 365 administrator account for migration.
- Set up accounts on Office 365 and assign licenses. These can be created in several ways:
Discover PST Files and Upload to Azure
MSPComplete Steps (https://manage.bittitan.com/)
- Create the customer. For guidance, see View, Add, and Edit your Customers.
- Create the Source and Destination endpoints.
- For the Source endpoint:
For the Destination endpoint:
- Click EndPoints > Add Endpoint, then enter the endpoint name. For endpoint type, select PST.
- Enter Storage Account Name and Access Key in fields provided.
Launch Personal Archive Migration (select All Products/Personal Archive Migration).
- Click EndPoints > Add Endpoint, then enter the endpoint name. For endpoint type, select Office 365, then fill in the required fields.
- Set up the Project. Create project > Create a Personal Archive Project >Name project, and Select MSPComplete customer > Select Source endpoint > Select Destination endpoint.
- Set Project Advanced Options. For guidance, see What Project Advanced Options are available?
Import PST files into the MigrationWiz PST archive project. Steps: Click on the Autodiscover Items bar > Click on the Start Autodiscover button > Once the PST files have been discovered, click on the green + Import Items button.
- Set the value for maximum licenses to consume per item per pass licensing count. The default value = 1. (This allows up to 10GB to be migrated. For example: If the largest PST file = 27GB, set this value to 3, otherwise this migration will pause at 10GB.) For guidance, see How do I enable consumption of multiple licenses for a single item?
- Under Source/Bucket Name, set the bucket name to "migrationwiz". If you are using your own Azure storage and uploaded your PST files into a container that has a different name, change the bucket name to "migrationwiz". If the container name and bucket name do not match, you will get an error when trying to import your PST files.
- Under Destination, choose whether to ingest the PST files into mailboxes or archives.
- Enable impersonation at Destination by selecting the check box Use impersonation at Destination. For guidance, see How do I migrate to Office 365 or Exchange 2010+ using impersonation?
- Folder Mapping. Folder mapping is optional, but you can control the mapping of folders on the destination by using regular expressions. For more information, see Can I add folder mapping in MigrationWiz?
- By default, MigrationWiz will mirror the folder structure that exists on the Source when migrating to the Destination.
- Important: When a migration starts and you are taking the default folder mappings (that is, a single folder at the root), MigrationWiz creates the Destination folder based on the item type of the first item migrated. If the first item is a calendar item, then the Destination is mapped to the root of the calendar folder. You can control this by migrating item types in batches (mail items, calendar items, etc.), each item type migrated in a separate migration pass.
- Set the preferred BitTitan data center. For the fastest migration speeds, select the data center that is closest to your Office 365 Destination tenant. For guidance, see How do I specify the data center?
- Add PSTCustomEndpointSuffix=Azure URI under Support options. For guidance, see How do I set the Azure location for PST migrations?
- Note: The Azure URI needs to be changed to one of the following values:
- core.chinacloudapi.cn (China)
- core.cloudapi.de (Germany)
- core.usgovcloudapi.gov (government)
- Important: This advanced option is only needed when uploading your PST files to a specific Azure data center, using the UploaderWiz optional parameter of azurelocation=gov, ger or china.
Note: If 0 items are discovered, a common mistake is that the Source/Bucket Name under Project Advanced Options has not been set to the correct Azure container name.
Choose which Destination mailbox to inject each PST file into.
Run Verify Credentials. See How do I verify credentials?
Purchase licenses by clicking Purchase > Personal Archive Migration > MigrationWiz-PST Migration & Discovery Bundle. See How do I purchase licenses?
Perform a Full Migration pass by selecting the check box beside Root Path. From the drop-down list, select Start, select Full Migration, then click Start Migration.
- The owner's email address should be displayed under the "Destination Email" column.
Note: If email@example.com is displayed as the Destination email address instead of the actual owner's email address, click on the Edit Item (pencil icon) to the right of the row, under the Destination Email Address field, and then enter the mailbox that this file will be ingested into. For guidance, see How do I choose which Destination mailbox to ingest files into?
- If you have multiple PST files to migrate into a single mailbox, click on the pencil icon next to the individual migration item. Then, under Source PST Path, click on the Add button (the +) to add the additional PST path(s). For guidance, see How do I add multiple entries to a line item?
- Delete the Azure blob container that was created during the upload to Azure.
Note: This will prevent incurring post-migration Azure costs for these containers. Be careful to only delete the container that was created for this migration project.