File Server (File Share) to SharePoint Online 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).
See KB004832 to create an Azure storage account. 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.) These 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. There is no need to create any Azure containers for this migration. Separate containers are created on a per-home directory basis. During migration, MigrationWiz will create two separate metadata files (with extensions:
-files.metadata) which will be added to each container. These are used during migration by MigrationWiz, to build the folder structure in OneDrive for Business and to migrate the permissions. They should not be deleted until after the migration.
Notes:If there are problems with the upload, and you need troubleshooting help, refer to
KB005473.If you are performing these steps from a domain-joined computer, a network drive needs to be mapped from the domain-joined computer to the file server, and the root path needs to match this drive letter, followed by the directory path, e.g., "x:\home files" (if there are spaces in the path, you need to surround the path with quotation marks) or x:\fileshare.the parameter
-homedrive true creates separate blob containers for each file share, under your top-level Azure blob container.
Create the Source and Destination endpoints.