- This is the complete onboarding task flow for migrating file shares from File Servers to Office 365 groups.
- Important: Due to API limitations, MigrationWiz is unable to migrate a file greater than 250MB in size.
- Complete each step in order. Links to corresponding Knowledge Base articles are provided.
- If you are performing a file server file share to SharePoint Online migration, refer to KB005112.
- The diagram below provides a high-level overview of the steps involved in migrating a small number of file shares. The key difference for this type of migration scenario is that this one requires an Azure subscription, and the use of the BitTitan UploaderWiz utility to upload the file shares to Azure before they can be migrated into Office 365 groups, using MigrationWiz.
- 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.
Prepare Azure Environment
- Estimate Azure storage costs. This step is optional, but is useful in order to provide the customer with up-front storage costs ahead of time. KB005177
- 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. KB004996
- 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.) 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 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. KB004832
Prepare the Destination Environment
- Create an administrator account in Office 365 to be used for the migration, or use the global admin account for the tenant. KB004948
- Create the Office 365 Group, if it doesn't already exist. Read the Create and navigate a group article from Microsoft to learn more.
- Add the migration administrator account as an owner and a member of the Destination group. Read the Manage Group membership in the Office 365 admin center article from Microsoft to learn more.
- Add other owners and members to the group.
- 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. Microsoft instructions. Note: 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. TechNet article
- By DirSync, AAD Sync, or AAD connect. KB004336
- 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., [email protected] 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. KB004843
Upload Files to Azure (Note: 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.)
- Download and extract the UploaderWiz utility from here (e.g., extract into the c:\apps\uploaderwiz directory).
- 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. KB005479
- 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): KB004997
UploaderWiz -accesskey "xxxxxxxx" -secretkey "xxxxxxxxxxxxxxxxxxxxxxx" -type azureblobs -rootpath "xxxxxxxx" -homedrive true
· 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.
MSPComplete Steps (https://manage.bittitan.com/)
- Create the customer. KB005421
- Create the Source and Destination endpoints.
- For the Source endpoint:
- Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select Azure File System.
- Enter Storage Account Name and Access Key in fields provided.
- For the Destination endpoint:
- Click Endpoints > click Add Endpoint > Enter endpoint name > select Office 365 Groups for endpoint type.
- Enter the URL of the group's document library into the URL field. KB005831
- Enter the admin account credentials. Note: This should be a global admin account. If creating a separate admin account for the purpose of migration, refer to the Office 365 section in KB004725.
- Important: You must create Destination endpoints for each Office 365 Group that you will be migrating file shares into.
- Set up the Project. Create project > Create a document project > Name the project > Select MSPComplete customer >Select Source endpoint > Select Destination endpoint.
- 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, as directed under Step 5 of this section.
- Set the value for Licensing/Maximum licenses to consume per item per pass. The default value is one license per user, which allows up to 10GB to be migrated per user. However, if a file share contains 28GB of data, the migration will stop at 10GB and you will have to assign more licenses. The project will only consume the number of licenses for the amount of data migrated. For example, if this parameter is set to 5, and a file share has only 28GB of data, then only three out of the five licenses will be consumed, and two licenses will remain. KB004890
- Add ShrinkFoldersMaxLength=200 under Support/Support options. KB005007
- Add FolderLimit=20000 under Support/Support options. This increases the maximum number of folders for the migration to 20,000. Large companies might have more than 10,000 folders (the default) to migrate, so we recommend increasing the folder limit to 20,000. KB005557
- Add RenameConflictingFiles=1 under Support/Support options. KB005058 Refer to the section in this article with the heading "Multiple files with the same name limitation".
- Add InitializationTimeout=28800000 under Support/Support options. KB005242
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. KB004268
- 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.
- 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. 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. KB005484
- Remove access to the Source file shares.
- Remove the migration administrator account (that was used for migration) from the Office 365 Group.
- Provide training on Office 365 Groups.
- 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.
- 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.