This Migration Guide provides the procedures for migrating file shares from Windows File Servers to Dropbox. If you are migrating home directories to Dropbox accounts, refer to File Server Home Directories to Dropbox Migration Guide for more information.
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.
To see what items are included in the migration, see What items are migrated with MigrationWiz? and What items are not migrated with MigrationWiz?
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.
The maximum file size for migration through MigrationWiz varies by migration type and environment, but may never exceed 60GB.
Prepare the Azure Environment
- Estimate Azure storage costs. This step is optional but is useful in providing the customer with upfront storage costs ahead of time. You will need enough storage capacity to upload all of the migrating data.
- Buy an Azure subscription, or use the free one-month trial ( this option is only viable if you are performing a very small migration).
- Create an Azure storage account. We recommend that you create an Azure Storage Account in the same Microsoft data center as the Destination Microsoft 365 tenant. Leave all settings default unless otherwise specified.
- Visit https://portal.azure.com
- Click Storage accounts
- Click Storage Create
- Select the subscription in which you want to create the new storage account.
- Select your Resource group. Create new if one doesn't exist.
- Enter a name for your storage account.
- Choose your datacenter Location.
- Choose Standard performance
- In the Redundancy field, select Locally Redundant Storage (LRS).
- Click Review
- Click Create
- Once the deployment shows as complete, click on Go to resource
- Select Access keys under "Security + Networking"
- Copy the Storage account name and the key 1. You will use this when running UploaderWiz and within the migration project.
- Click on Containers under "Data Storage"
- Create a container for each separate file server you will be uploading and make note of the name(s)
When uploading, MigrationWiz will create three metadata files, which will be added to each container. These are used during migration by MigrationWiz, to build the folder structure in the destination. They should not be deleted until after the migration.
Prepare the Destination Dropbox Environment
- 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
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.
- Download and extract the UploaderWiz utility from here (e.g., extract into the c:\apps\uploaderwiz directory).
- (Optional, but recommended) Set the file shares to read-only access 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.
- 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" -container xxxxxx -type azureblobs -rootpath "xxxxxxxx". Note: 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 (e.g. x:\File Server). If there are spaces in the path, then it needs to be enclosed within quotation marks
- The AccessKey will be the name of the storage account
- The SecretKey will be the access key for the storage account
- The Container will be the name of the conainer you are uploading to
- The RootPath will be the path to the files that you want to migrate
Create a Document Project
- Log in to MigrationWiz.
- Click the Go to My Projects button.
- Click the Create Project button.
- Select the Document project type.
- Click Next Step.
- Enter a Project name and select a Customer.
- Click Next Step.
- Click on New to create a new endpoint or select an existing one from the dropdown list
- Give the endpoint a name
- For Endpoint Type, select Azure File System
- Enter the storage account name
- Enter the Access Key
- Click on Add
- Click Next Step.
- Click on New to create a new destination endpoint or select an existing one from the dropdown list
- Give the endpoint a name
- Select Dropbox as the endpoint type
- confirm that Provide Credentials is selected
- Click on Save And Go To Summary
- In the "Authorization" tab, click on the option to "Request Access Token" and go through the steps to sign into your Dropbox tenant. This will generate the Token that MigrationWiz will use to connect to Dropbox
- Once the token has been provided, click on "Advanced Options on the left side of the screen
- Under the "support" Section enter the option InitializationTimeout=8 This increases the maximum allowed timeout window for the enumeration phase of the migration. This is most useful for larger migrations, but does not negatively impact smaller ones.
- Click on the Source/Destination tab
- Under the Source section, update the Container Name to reflect the container that the items were uploaded to.
- Click on Save and then Save Project
Note: If you are migrating from more than one source, and are using different containers within Azure for each upload, you will need a separate project for each separate container. You can easily create additional projects using this first one as a template by cloning it. You would then just need to update the container in each one to reflect your desired source.
Clone the project
- Click the Edit Project button
- Select Clone Project from the drop-down list
- Enter the name for the new Project (each new project should be named after the file share name)
- Click the Clone Project button.
Within the project, add the Dropbox account to migrate the files into. Select Add/Quick Add and enter the login name of the Dropbox account within the Destination field labeled "Email Address".
Once the item has been added to the project, select it by checking the box next to it and then click on "Apply Licenses" > "Apply User Migration Bundle Licenses". This will apply the UMB license to the user. Once the "User Migration Bundle Active' column changes to a Yes, you will be ready to proceed with the migration.
Run Verify Credentials
Note: You do not need a license applied to run this step.
- Open the Project containing items you wish to validate.
- Select the items you wish to validate.
- Click on the Start button in your dashboard.
- Select Verify Credentials from the drop-down list.
Once complete, the results of the verification will be shown in the Status section.
- Select the users
- Click the Start button from the top
- Select Full Migration
- Click Start Migration
If the migration fails, you will see a red Failure message in the project, clicking on this will take you to a screen which will show the error which caused it to fail. If the Migration was successful, but certain items failed to migrate, You will also see those errors listed. If the migration is failed, you can simply try it again after resolving whatever caused it to fail. If it was successful but with failed items, you can run a "Retry Errors" migration pass to attempt those failed items again without running the entire migration again.
If problems persist, contact Support.
- Remove access to the Source file shares.
- Provide training on Dropbox.
- Decommission file server. Perform this step only after migrating all data from the file server, such as home directories, and you are certain that you will not be returning to the file server.
- Delete the Azure blob container that was created during the upload to Azure. This will prevent incurring post-migration Azure costs for this container.
- If preferred, you can move data from shared folders to team folders on Dropbox, and set up access permissions. Read the Shared folder differences with Dropbox Business article from Dropbox for more information.