File Server (Home Directories) to OneDrive For Business Migration Guide, Using PowerShell
This guide provides the procedures to be followed for migrating
home directories from File Servers to OneDrive for Business.
We recommend this strategy when migrating a large number of home directories. When migrating a smaller number of home directories, follow the steps in
When migrating file shares from the file server, follow the migration guide specific to that scenario. Typically, file shares will be migrated to SharePoint Online Site libraries.
The diagram below provides a high-level overview of the steps involved in migrating a large number of home directories. The key difference for this type of migration scenario is that this requires an Azure subscription, and the use of the BitTitan UploaderWiz utility to upload the home directories to Azure, before they can be migrated into the OneDrive for Business accounts using MigrationWiz. It also uses a combination of a PowerShell script and a CSV file, which automates the building of the MigrationWiz projects, with all of the Advanced Options preset. There is also no need to create endpoints in MSPComplete prior to running MigrationWiz, because the PowerShell script automates the creation of the endpoints on the first run, and includes checks for subsequent runs so that it can use the existing endpoints that were created from the first run.
Set up the BitTitan PowerShell.
Prerequisites for installing BitTitan PowerShell are detailed in
KB005158. These are:
Microsoft Windows PowerShell 4.0
Microsoft Framework 3.5,
Microsoft.NET Framework 4.6.21
Uninstall any previous versions of MigrationWiz PowerShell, or BitTitan PowerShell, on the machine that you will be running the PowerShell scripts from.
Older versions will be listed as "MigrationWiz PowerShell" under your program list in Control Panel. This was because earlier versions were known as "MigrationWiz PowerShell" rather than "BitTitan PowerShell".
Versions that were installed after October 5, 2016 will be listed as "BitTitan PowerShell".
UploaderWiz -accesskey "xxxxxxxx" -secretkey "xxxxxxxxxxxxxxxxxxxxxxx" -type azureblobs -rootpath "xxxxxxxx" -homedrive true
If there are problems with the upload, for 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 rootpath needs to match this drive letter, followed by the directory path, e.g., "x:\staging_batch" (if there are spaces in the path, you need to surround the path with quotes).
Run the script, using the Windows PowerShell. Change to the directory that you extracted the scripts into, e.g., c:\scripts:> .\projectimport.ps1
When prompted for credentials, enter your BitTitan credentials.
All projects will be created with a name set to destinationemailaddress_ps. The '_ps' is used by the Full migration pass script (RunSubmission.ps1) so that it only starts migrations for those projects matching this name criteria.
This script will set all the neccessary Advanced Options. These include:
Add ShrinkFoldersMaxLength=200 under
RunSubmission.ps1 script (e.g., c:\scripts:> .\RunSubmission.ps1). This performs a Full migration pass.
When prompted for credentials, enter your BitTitan credentials. You can set your BitTitan account credentials within this script (but these could then be seen by others who have access to the script). This will avoid being prompted to enter your BitTitan account credentials.
Once the script completes, launch MigrationWiz and enter one of your projects. You can then monitor the progress of the migration.