Prepare the Azure Environment
- Estimate Azure storage costs. This step is optional, but is useful in order to provide the customer with upfront storage costs ahead of time.
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.
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 when creating your MSPComplete Source endpoint. 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 the upload to Azure, the UploaderWiz utility 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. They should not be deleted until after the migration.
Prepare the Destination Environment (Dropbox)
- Create a Dropbox user account that will be used for the migration, and grant
team admin privileges to the user. Follow the instructions in the
Add Tiered Admins article from Dropbox.
Create the new Dropbox user accounts. Follow the instructions in the Invite your Team article from Dropbox.
You must wait for all new users to accept their Dropbox invitations before starting the migration.
Upload Files to Azure
(Note: These steps are performed from the file server, or the computer joined to the domain, when logged in with 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 home directory migration batch to read-only access by user, and inform each user that a migration is occurring and that their home directory is now read-only. This will prevent the user from adding any files to their home directory during the migration.
- 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
- If there are problems with the upload, and you need troubleshooting help, refer to
- 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:\home directories" (if there are spaces in the path, you need to enclose the path with quotes) or x:\homedir.
- Create customer.
- Create the Source and Destination endpoints. Select
Azure File System for the Source endpoint, and
Dropbox for the Destination endpoint.
- Launch Document migration. Select
- Set up the Project. Create project > Create a document project > Name project > Select MSPComplete customer > Select Source endpoint > Select Destination endpoint > Authorization > Destination Authorization > Click on the Request Access Token button. You will then be taken to a Dropbox login window. Sign in with the Dropbox admin account to authorize. Once authorized, you will be taken back to MigrationWiz, and the status of the Change Access Token button will change to Provided. Click on
Save Project to continue.
Note: 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.
- Set Project Advanced Options
Clone the Project. Click on the
>From the drop-down list, select
Clone Project >Enter the name for new Project (each new project should be named after the home directory container name in Azure) >Click on the
Clone Project button.
Important: Repeat this process to create one MigrationWiz project per home directory.
KB005487For each cloned project, you must move through the steps to set up Authorization. Edit Project > Edit Project > Authorization > click on the Request Access Token button. The status of the Change Access Token button will change to Provided. To continue, click
Save Project.For each cloned project, add the Dropbox account to migrate home directory files into. Select
Add/Quick Add and enter the login name of the Dropbox account within the Destination field labeled "Email Address".Set the Project Advanced Option for the container name.
- Set the value for 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 user has 28GB of data, the migration will pause at 10GB and you will have to assign more licenses to the user. The recommended maximum licenses to consume per user for a document migration project is five (5) licenses per user, which allows up to 50GB of data to be migrated per user. The project will only consume the number of licenses for the amount of data migrated. If a user has 28GB of data, only three out of the five licenses will be consumed, and two licenses will remain.
Support/Support options. KB005242
FolderLimit=20000 - 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.
Note: 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.
KB004511Purchase Document licenses.
KB004647Perform a Full Migration pass. Checkmark the
next to the Root Path >Select theStart
button from the drop-down list >Select
Click on theStart Migration
- Specify the correct container name under the Source: File System/Container Name field. By default, the container name is migrationwiz. Important: 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 Step 3, under the Upload Files to Azure 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.