Skip Ribbon Commands
Skip to main content

File Server (File Shares) to Dropbox Shared Folders Migration Guide

Last Update: 7/21/2017 11:34 AM
This article has been moved to our new Help Center. Please update your bookmarks.
​​File Server (file shares) to Dropbox Migration Guide

Important: When you sign in to MigrationWiz, you are redirected to the Getting Started page in MSPComplete. To get to a migration project created before April 4, 2017, click the Go to Projects button on the Getting Started Page. To create a new project for the migration scenario documented in this article, click the waffle icon (waffle.png) in the top navigation bar of MSPComplete, and select the appropriate migration product.

  • 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 KB005819.
  • 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.

HomeDirMigrate_workflow (003).png 

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. 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 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. 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. KB004832

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.

    • 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. KB005479
  3. 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" -container "xxxxxxxx"
    • Notes: 
      • 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 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. KB005421
  2. Create the Source and Destination endpoints. Select Azure File System for the Source endpoint, and Dropbox for the Destination endpoint.
  3. Launch Document migration. Select All Products >Document Migration.

MigrationWiz Steps

  1. 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.
  2. Set the Project Advanced Options KB004834
    • 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 file share has 28GB of data, the migration will pause at 10GB,, and you will have to assign more licenses to the line item. The recommended maximum licenses to consume per line item for a document migration project is five (5) licenses per file share, which allows up to 50GB of data to be migrated per file share. The project will only consume the number of licenses for the amount of data migrated. If a line item has 28GB of data, only three out of the five licenses will be consumed, and two licenses will remain. KB004890
    • 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 file shares were uploaded in Step 3, under the Upload Files to Azure section of this guide.
    • Add InitializationTimeout=28800000 under Support/Support optionsKB005242
    • Add 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. KB005557
    • 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. 
  3. 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.
      • For the Destination, enter an email address of a Dropbox admin in the Email Address field.
  4. Run Verify Credentials. KB004511
  5. Purchase Document licenses.  Note: One Document license allows up to 10GB of data to be migrated. Therefore, for example, if your total data size = 78GB, this will require eight (8) document licenses to be purchased. In this example, you should also set the Advanced Option for maximum licenses to consume to be 8, otherwise your migration will pause at 10GB. KB004647
  6. Perform a Full Migration pass. Checkmark the box next to the Root Path >From the drop-down list, select the Start button >Select Full Migration > Click on the Start Migration button. KB004938

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. More information on Shared Folders and Team Folders can be found here.