File Server File Shares to Dropbox Shared Folders Migration Guide


This Migration Guide provides the procedures for migrating file shares from 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.

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 is a migration solution (not a synchronization solution) and will NOT propagate updates, deletes, or moves of the items previously migrated in the first migration pass because 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. For more information, visit Project Sharing in MigrationWiz.

The diagram below provides a high-level overview of the steps involved in migrating a small number of home directories. 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 home directories to Azure before they can be migrated into the Dropbox accounts using MigrationWiz.


Prepare the Azure Environment

  1. Estimate Azure storage costs. This step is optional but is useful in order to provide the customer with upfront storage costs ahead of time. Read the Estimate Azure Storage costs for migrations article for more information.
  2. 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. Read the How do I buy an Azure subscription? article for more information.
  3. 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 Manage Access Keys at the bottom of the screen.) These need to be entered when creating your MSPComplete Source endpoint. 

Note: 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. During the upload to Azure, the UploaderWiz utility will create a container on Azure which all file shares will be uploaded into. This will also contain two separate metadata files (with extensions: -directory.metadata and -files.metadata). These are used during migration by MigrationWiz, to build out the folder structure. They should not be deleted until after the migration. Read the How do I Create an Azure Storage Account? article for more information.


Prepare the Destination Environment (Dropbox)

  1. 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.
  2. Create the new Dropbox user accounts. Follow the instructions in the Invite your Team article from Dropbox.​

Note: 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.

  1. Download and extract the UploaderWiz utility from here, e.g., extract into the C:\Apps\uploaderwiz directory.
  2. Set the file shares to read-only access by user, and inform each user that a migration is occurring, and that these file shares are now read-only. This will prevent the user from adding any files to the file shares during the migration. Read the How do I restrict users to read-only access to their Home Directories? article for more information.
  3. From the command console, running as administrator, from the directory that UploaderWiz was extracted into, run the command listed below (replace the x's with your own information). Read the Using BitTitan UploaderWiz for File Server Migrations article for more information.
    UploaderWiz -accesskey "xxxxxxxx" -secretkey "xxxxxxxxxxxxxxxxxxxxxxx" -type azureblobs -rootpath "xxxxxxxx" -container "xxxxxxxx"


  • If there are problems with the upload, and you need troubleshooting help, read the How do I troubleshoot UploaderWiz?
  • 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.
  • The container parameter should be set to the name that you want the container to be called on Azure. You will then match this container name, under your MigrationWiz project Advanced Options, as specified in Step 2 under the MigrationWiz section of this guide.


MSPComplete Steps

  1. Create customer. Read the View, Add, and Edit Your Customers article.
  2. Create the Source and Destination endpoints. Select Azure File System for the Source endpoint, and Dropbox for the Destination endpoint.
  3. Purchase User Migration Bundle licenses. 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. Refer to these articles for more information:


MigrationWiz Steps

  1. Set up the Project. Read the How do I create a new migration project? article for more information.
    Note: When you reach the Authorization tab, click 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 Save Project to continue.
  2. Set the Project Advanced Options Read the What project Advanced Options are available? article for more information.
  3. 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 file shares were uploaded in step 3, under the Upload Files to Azure section of this guide.
  4. Add under Support Options: InitializationTimeout=8 Read the Cannot get folders from My Drive article for more information.
  5. 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.
  6. Add a line item to your MigrationWiz project. Select Add > Quick Add > set Destination email address. 

    Notes: You only need to add one line item to your project. This will be used to migrate all file shares that are in the Azure container to shared folders on Dropbox.

  7. For the Destination, enter an email address of a Dropbox admin in the Email Address field.
  8. Run Verify Credentials. Read the How do I verify credentials? article for more information.
  9. Purchase User Migration Bundle licenses. Refer to these articles for more information:
  10. Perform a Full Migration pass. Read the How do I start a migration? article for more information.
  11. Important: Recent changes to the Dropbox APIs prevent us from adding watermarks on files in the Destination Dropbox accounts. Therefore, if you perform a partial migration, reset the items in MigrationWiz, and then perform the migration again, you will end up with duplicate files at the Destination. If you must rerun the migration, we recommend that you first delete all files already migrated to the Destination Dropbox accounts.


Post-Migration Steps

  1. Remove access to the Source file shares.
  2. Provide training on Dropbox.
  3. 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.
  4. Delete the Azure blob container that was created during the upload to Azure.
    Note: This will prevent incurring post-migration Azure costs for this container.
  5. 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.




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