Part 3: Setup for the Migration Tool
You can download the script package
Layer2 OneDrive for Business Migration Tool
Before you start, there are some small preparations to do.
The script is written in PowerShell, so you must have the PowerShell console
installed on the client machine, as well as have the following Office 365
For more information about the Office 365 cmdlets, visit http://powershell.office.com/get-started.
The client machine needs the following assemblies available:
When you unpack the Migration Tool zip it will contain the PowerShell script
itself, two .txt files used for configuration, a folder to collect the created
connections, and this users guide.
Below are the description and use of the two configuration .txt files. Both
must be filled in with the appropriate data for the script to function
General information about the Office 365 tenant, the administrator account,
etc., are stored in a text file named config.txt. This is necessary for both the
OneDrive provisioning and the connection file creation.
Please fill in the settings appropriate for your company.
An Office 365 site URL normally
looks like "companyname.onmicrosoft.com". Your domain in should be the
companyname part of it.
Global Admin Account (mandatory)
With this account, the
script connects to OneDrive for Business and creates the different user sites.
It will set itself as contributor on each site to guarantee proper permissions
for the Layer2 Cloud Connector to use for access later. For more information
about creating/assigning Admin Accounts for O365, see Assign Admin Roles in
This account should also be used as service account for the
Layer2 Cloud Connector Service.
If you have your own validated domain, and
your user account scheme and your OneDrive address does not contain the
onmicrosoft pattern, you can define the domain
Note: If you have a domain with subdomains
(e.g. sub.domain.com), you have to adjust the PowerShell script for that. We do
not support such domains yet.
If you have your ownvalidated domain, and
your user account scheme and OneDrive address is not containing the onmicrosoft
pattern, you can define the topleveldomain here.
The users.txt file will provide all the necessary user information to the
script. Each line in the file is one user (except the very first line, do not
edit this). It has the format of:
<base username>;<path to user
The 'base username' is the name without the domain – that was supplied with
the config.txt file, so you just need the base name. The 'path to user drive' is
standard notation to the specific location in the file share where that user’s
content is stored.
For example, if you have a user with the login handle 'firstname.lastname@example.org',
who has a file share path like 'P:\Userdrives\user1', the file is filled like
This notation gives you the chance to provide different user drive paths if
you migrate from a heterogenic environment.
Note: The first line of this file is not read as
user input. Please leave the comment as is.