- This Migration Guide provides the procedures to be followed for migrating home directories from File Servers to Dropbox.
- If you are migrating file shares to Dropbox accounts, refer to the File Server (File Shares) to Dropbox Shared Folders Migration Guide for more information.
- MigrationWiz now supports the capability to share migration projects across a Workgroup. Migration projects are no longer tied to individual accounts, they are tied to Workgroups. When Workgroup Administrators turn on the Project Sharing feature, all Agents besides those who are Inactive are able to 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
- 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.
- 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.
- 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. 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: -directory.metadata and -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. Read the How do I Create an Azure Storage Account? article for more information.
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.
Notes: 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 the domain admin account, with local admin rights to the machine.
- Download the UploaderWiz utility and extract it into the
- 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. Read the How do I restrict users to read-only access to their Home Directories? article for more information.
- 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). Read the Using BitTitan UploaderWiz for File Server Migrations article for more information.
UploaderWiz -accesskey "xxxxxxxx" -secretkey "xxxxxxxxxxxxxxxxxxxxxxx" -type azureblobs -rootpath "xxxxxxxx" -homedrive true
- If there are problems with the upload, and you need troubleshooting help, read the How do I troubleshoot UploaderWiz? article.
- 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. Read the View, Add, and Edit Your Customers article for more information.
- Create the Source and Destination endpoints. Select Azure File System for the Source endpoint, and Dropbox for the Destination endpoint.
- Launch Document migration. Select All Products >Document Migration.
- Set up the Project. Read the How do I create a new migration project? article for more information.
Note: At 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.
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. Read the What project Advanced Options are available? article for more information.
- Under Support Options add:
InitializationTimeout=8Read the Cannot retrieve folders from "folder" article for more information.
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.
- 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. Read the How does UploaderWiz overcome Microsoft restrictions to Azure container names? article for more information.
- Remove access to the Source home directories.
- Provide training on Dropbox.
- Decommission file server. Perform this step only after migrating all data from the file server, such as file shares, and 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.
Note: 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 home directories and have a create date from the date of the upload.