EML to Office 365 Migration Guide
Important: When you sign in to MigrationWiz, you are redirected to the Getting Started page in MSPComplete. To get 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, click the waffle icon () in the top navigation bar of MSPComplete, and select the appropriate migration product.
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).
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 on
Manage Access Keys at the bottom of the screen.) The Storage Account Name and the Primary Access Key need to be entered into the MigrationWiz document project when specifying the Source settings. We recommend that you create an Azure Storage Account in the same Microsoft data center as the Destination Office 365 tenant. KB004832
Create a public Azure container (e.g., migrationwiz).
Note: You will be prompted to enter this container name when creating your MigrationWiz project. KB008059
Ensure that the EML file structure follows supported formats.
Upload the EML files to your Azure container. Options include UploaderWiz, AZCopy, Azure Storage Explorer, Microsoft Azure Import/Export Service and PowerShell. Details can be found in
If using you are using UploaderWiz for the upload to Azure, this includes logic to overcome Microsoft restrictions to Azure container names.
UploaderWiz can only support file path names that are shorter than 248 characters. This limitation is due to the Microsoft .Net Framework.KB005516
Create an administrator account in Office 365 to be used for migration, or use the global admin account for the tenant.
Set up accounts on Office 365 and assign licenses. These can be created in several ways:
Create the Source and Destination endpoints.