File Server to Office 365 Groups Files Migration Guide


This is the complete onboarding task flow for migrating file shares from File Servers to Office 365 groups. You will need to create separate MigrationWiz projects for each file share. You will create a baseline project first with all the Advanced Options set, and then use the MigrationWiz Clone feature to create one MigrationWiz project per file share, based on this first baseline project. The Destination for this scenario is the Files document library in each Office 365 Group.

First migration?

We’ve created a guide on scoping, planning, and managing the migration process for your use. If this is your first migration, we recommend reading this guide carefully.


MigrationWiz is a migration tool, not a syncing tool. If changes are made at the source after migration, they will not sync to the destination, nor will changes made at the destination sync to the source. We do not have “live” monitoring of changes (as with a sync agent) and we cannot handle scenarios such as conflict resolution without user interaction.

MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all Agents besides those who are Inactive can view all migrations projects. 

We are not able to support migrations with two-factor or multifactor authentication. 

Prepare Azure Environment

  1. Estimate Azure storage costs. This step is optional but is useful in providing the customer with upfront storage costs ahead of time.
  2. Buy an Azure subscription, or use the free one-month trial (this option is only viable if you are performing a very small migration).
  3. Create an Azure storage account. We recommend that you create an Azure Storage Account in the same Microsoft data center as the Destination Office 365 tenant. 
    1. Log in to
    2. Click Storage.
    3. Click Manage Access Keys at the bottom of the screen. The access keys 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. 
    4. Take note of the Storage Account Name and the Primary Access Key. To find these, click Manage Access Keys at the bottom of the screen. These need to be entered into the MigrationWiz document project when specifying the Source settings.

You do not 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 the extensions: -directory.metadata and -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.

Prepare the Destination Environment

  1. Create a user in Office 365.
  2. Create the Office 365 Group, if it doesn't already exist. 
  3. Add the migration administrator account as an owner and a member of the Destination group. 
  4. Add other owners and members to the group.
  5. If they have not already been created, set up accounts on Office 365 and assign licenses. These can be created in several ways:
    • Manually, one at a time.
    • By bulk import, via CSV file. You can use the CSV file that was created under Step 3 of the Prepare the Source Environment section of this guide.
    • By PowerShell script
    • Important: If you are migrating permissions, the part of the usernames before the "@" sign on Office 365 must match the part of the username on Source before the "@" sign, e.g., on Source must follow the same format before the @ sign on Office 365, and so must also equal "john.smith" on Office 365. The domain name, however, can be different.
  6. If they have not already been created, set up groups on Office 365. If permissions were assigned to groups on Source, and you want these to be migrated, the group names on Office 365 must match the group names on Source.
  7. Set up the app-based authentication in the Office 365 tenant. For specific instructions, see App-based Authentication.

Upload Files to Azure

Steps are performed from a file server, or a computer joined to the domain, when logged in with the domain admin account, with local admin rights to the machine. This process utilizes UploaderWiz. Our guides contain information on running, configuring, and troubleshooting UploaderWiz. 

  1. Steps are performed from a file server, or a computer joined to the domain, when logged in with the domain admin account, with local admin rights to the machine.
  2. Download and extract the UploaderWiz utility from here (e.g., extract into the c:\apps\uploaderwiz directory).
  3. Set the file share migration batch to read-only access by user and inform the users that a migration is occurring and that their file shares are now read-only. This will prevent the user from adding files to these file shares during the migration.
  4. You can restrict users to read-only access to their Home Directories through the Active Directory Users and Computers console on the AD controller, or via PowerShell. Prerequisites:
      1. Create a CSV file containing all the usernames (SAMAccountName).
      2. Install the required AD module on the machine that you're running the script from.
      3. Example script: 

    Import-Module 'ActiveDirectory'
    import-csv E:\usersname.csv | foreach-object{
    $homeDrive = (Get-ADUser -Identity $ -Properties homedirectory).homedirectory #Query AD for the HomeDirectory attribute
    $ACL = Get-Acl $homeDrive
    $ACL.setAccessRule((New-Object System.Security.AccessControl.FileSystemAccessRule($, "Read", "ContainerInherit,ObjectInherit", "none", "allow")))
    Set-Acl $homeDrive $ACL

  5. From the command console, running as administrator, from the directory that UploaderWiz was extracted into, run the following command (replace the x's with your own information):
    UploaderWiz -accesskey "xxxxxxxx" -secretkey "xxxxxxxxxxxxxxxxxxxxxxx" -type azureblobs -rootpath "xxxxxxxx" -homedrive true
    1. 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.
    2. The parameter -homedrive true creates separate blob containers for each file share, under your top-level Azure blob container.

MSPComplete Steps

Create Customer

  1. Click the Add button in the top navigation bar.
  2. Click the Add Customer button on the All Customers page.
  3. In the left navigation pane, select the appropriate workgroup and then click All Customers.
  4. Click Add Customer.
  5. Enter the new customer’s information in the Add Customer form. Primary Email Domain and Company Name are required. The rest are optional.
  6. Click Save.
  7. Repeat steps 1 through 4 for each customer you want to add. 

Purchase licenses

We recommend that you purchase the User Migration Bundle license for this migration scenario. User Migration Bundle licenses allow multiple types of migrations to be performed with a single license. They also allow DeploymentPro to be used to configure Outlook email profiles. For questions on licensing, visit MigrationWiz Licenses

To purchase licenses:

  1. Sign in to your BitTitan account. 
  2. In the top navigation bar, click Purchase.
  3. Click the Select button and choose User Migration Bundle licenses.
  4. Enter the number of licenses you want to purchase. Click Buy Now.
  5. Enter a Billing address if applicable.
  6. Click Next.
  7. Review the Order Summary and enter a payment method.
  8. Click Place Your Order.

Apply licenses

  1. Select the correct workgroup on the top of the left navigation pane. This is the workgroup that the customer and migration project were created under. Your account must be part of the workgroup if the project was not created under your account.
  2. On the left navigation pane, click Customers.
  3. Click the customer that employs the user to whom you want to apply a User Migration Bundle license.
  4. Click the Users tab at the top of the page.
  5. Check the box to the left of the email for the user(s) to whom you want to apply a license.
  6. Click the Apply User Migration Bundle License button at the top of the page. It is recommended that users be added to the Customer page with the vanity domain. Then have the User Migration Bundle Licenses applied, before editing to show the .onmicrosoft domain, if the .onmicrosoft domain will be used for the migration.
  7. If there is at least one unassigned User Migration Bundle license available for each selected user, click Confirm.

MigrationWiz Steps

Create a Document Project

  1. Log in to MigrationWiz.
  2. Click the Go to My Projects button.
  3. Click the Create Project button.
  4. Select the Document project type. 
  5. Click Next Step.
  6. Enter a Project name and select a Customer.
  7. Click Next Step.
  8. Select endpoints or follow the steps below to create new endpoints. 

This first project is the baseline project, from which all other projects will be cloned. We recommend that you call this "baseline", for easy reference.

The Destination endpoint can be set to any Office 365 Groups Destination endpoint. Once the project has been cloned, you will need to change the Destination endpoint for the cloned project, to reflect the correct Office 365 Group endpoint


Endpoints are now created through MigrationWiz, rather than through MSPComplete. The steps for this section outline how to create the endpoints in MigrationWiz.

If you are selecting an existing endpoint, keep in mind that only ten endpoints will show in the drop-down. If you have more than ten, you may need to search. Endpoint search is case and character specific. For example, Cust0mer will not show up if the search is customer. We recommend keeping a list of endpoints you have created, along with any unique spellings or capitalization you may have used.

You may either use existing endpoints, or create new ones.

To create a new source endpoint:

  1. Click Endpoints.
  2. Click Add Endpoint.
  3. Select Azure File System
  4. Enter Storage Account Name and Access Key in fields provided.

  5. Click Add Endpoint

To create a new destination endpoint:

  1. Click Endpoints.
  2. Click Add Endpoint.
  3. Select Office 365 Groups
  4. Enter the URL of the group's document library into the URL field.

  5. Enter the admin account credentials. This should be a global admin account. 

  6. Click Add Endpoint
  7. Important: You must create Destination endpoints for each Office 365 Group that you will be migrating file shares into.

Add Advanced & Support Options

  • ShrinkFoldersMaxLength=200  This option shrinks file path names to prevent issues during the migration. 
  • RenameConflictingFiles=1  This prevents errors due to files with duplicate names.
  • InitializationTimeout=8 This increases the initialization timeout window to eight hours.

There are no spaces on either side of the "=" sign, and the entries are case-sensitive, so pay special attention to the capital letters in the commands above.

Set the Preferred BitTitan Data Center. For the fastest migration speeds, select the Data Center that is closest to your Office 365 Destination tenant. 

Clone the project

  1. Click the Edit Project button.
  2. Select Clone Project from the drop-down list.
  3. Enter the name for the new Project (each new project should be named after the file share name).
  4. Click the Clone Project button.
  5. Important: Repeat this process to create one MigrationWiz project per file share.

Add Items

In each cloned MigrationWiz project, add an item for the file share to be migrated. 

  1. Select Add/Quick Add.
  2. Enter Shared Documents as the Destination library name.

Change Endpoints

In each cloned MigrationWiz project, change the Destination endpoint to reflect the Office 365 Group endpoint that you want to migrate the file share into.

  1. Click the Edit Project button.
  2. Select Edit Project.
  3. Click Destination Settings.
  4. Click the endpoint drop-down list and choose the Destination Office 365 Group endpoint.
  5. Click Save Project.

The Source entry field will already contain the Azure information, based on the Source endpoint.

The Destination Library field will be the name of the SharePoint document library, for Office 365 groups. This will always be "Shared Documents", because each Office 365 Group gets assigned a document library, named "Shared Documents". It does not need the entire URL because this was captured when setting up the Destination endpoint.

Container Name

In each cloned MigrationWiz project, set the Project Advanced Option for the container name

Specify the correct container name under the Source: File System/Container Name field. By default, the container name is migrationwiz. This must be changed or your migration will fail.

This must be set to match the name of the Azure container that was created on your Azure subscription when the home directories were uploaded in the previous step, under the "Prepare Source File Server Environment" section of this guide.

Typically, this will match the name of the home directory, unless the home directory contained any special characters (including spaces and uppercase characters). In such cases, the Azure container name could be different, and so the names should be checked within Azure.

Run Verify Credentials

  1. Open the Project containing items you wish to validate​.
  2. Select the items you wish to validate.
  3. Click the Start button in your dashboard.
  4. Select Verify Credentials from the drop-down list.

Once complete, the results of the verification will be shown in the Status section.​ 

Start migration

  1. Select the users.
  2. Click the Start button from the top.
  3. Select Full Migration.
  4. Click Start Migration.

Run Retry Errors

Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.

If problems persist, contact Support.

Post Migration

  1. Remove access to the Source file shares.
  2. Remove the migration administrator account (that was used for migration) from the Office 365 Group.
  3. Provide training on Office 365 Groups.
  4. Decommission the file server. Perform this step only after migrating all data from the file server, such as home directories, when you are certain that you will not be returning to the file server.
  5. Delete all the Azure blob containers that were created during the upload to Azure.
    • This will prevent incurring post-migration Azure costs for these containers.
    • Be careful to only delete the containers created by UploaderWiz; these will be names that match the file shares, and have a create date from the date of the upload.


Was this article helpful?
0 out of 0 found this helpful