Dropbox to OneDrive for Business Migration Guide

​​This is the complete onboarding task flow for migrating folders and documents from Dropbox to OneDrive for Business. The Destination must be OneDrive for Business, not the personal OneDrive version.

  • Due to the latest Dropbox update, admin access is no longer automatic. Moving forward, to have access to a team folder by default, you will need to add yourself to the folder from the admin console. Admins will always have access to all team folders in the admin console on the Team Folders page.
  • Important: MigrationWiz does not support the migration of Dropbox Teams Folders from the home location at this time from the home location. If you want to migrate a Teams Folder, it has to be copied under the owner’s folder in the home location. Please see the Advanced Options section below for more details.
  • Important: MigrationWiz currently does not support migration for new Team Space in Dropbox.
    As per Dropbox help documentation, ‘Some teams have access to the new team folder structure. If you see a purple folder icon with one person on it on dropbox.com, you have the new team space.’
  • To enable folder mapping during your migration, see Dropbox Migration FAQs.
  • Note: When Dropbox is configured as the Source, shared folders and items are
    migrated to the destination but their shared permissions are not.

OneDrive migrations

Note that OneDrive data may not be accessible for a few days after migration, due to OneDrive's crawling and indexing process. We suggest having your users log in immediately after migration, but warn them that their data may not be available immediately. For this reason, it may be best to complete the migration on a Friday so the indexing can happen over the weekend.

If you are migrating to an Microsoft 365 Small Business Tenant account, the processes will be very similar. However, you will not be able to use admin credentials for your Destination endpoint and will, instead, be using end user credentials. 

Due to versioning, storage usage in OneDrive may be increased when migrating with permissions.

First migration?

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

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.

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. 

What items are and are not migrated?

Migrated

  • Folders
  • Shared Folders
  • Code Files
  • Documents
  • Images
  • Forms
  • Executables
  • Videos
  • Audio Files

Not Migrated

  • Dropbox shared folder permissions
  • Dropbox Notes
  • Dropbox Bookmarks
  • Dropbox Tags
  • Dropbox Teams
  • Version history
  • .paper files

Prepare the Azure Environment

If using Microsoft provided Azure storage, you can skip this section.

  1. Estimate Azure storage costs. This step is optional but is useful in providing the customer with upfront storage costs ahead of time.
  2. Buy an Azure subscription, or use the free one-month trial ( this option is only viable if you are performing a very small migration).
  3. 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. 
    1. Log in to https://manage.windowsazure.com
    2. Click Storage
    3. Click Manage Access Keys at the bottom of the screen. The access keys need to be entered when creating the MSPComplete Source endpoint. We recommend that you create an Azure Storage Account in the same Microsoft data center as the Destination Microsoft 365 tenant. 
    4. Take note of the Storage Account Name and the Primary Access Key as follows:
    5. -accesskey – This is the Storage account name for the Blob – example “accountname”
    6. -secretkey - This is the access key for the Storage account – example “W1RrDfkPNkfYfdVqizMNJjn5mXchwMP5uYBY8MsMqWTA7EubG911+4fZlki0Gag==”
  4. Create an Azure BLOB container. Take note of the name of the BLOB to be entered in the Bucket Name field in the project Advanced Options.

Prepare the Source Environment

  1. Create a Dropbox Business 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 guide from Dropbox.
  2. Create a list of the Dropbox user accounts that need to be migrated from the Source.

Important, the connectors for this migration do not support invalid XML characters.  The list of users will need to be checked for these characters and users with invalid characters will either need to be renamed or migrated using a GCC/China connection instead of v2. The invalid characters are: < > " ' &

Prepare the Destination Environment

Create admin account

Create an administrator account in Microsoft 365 to be used for migration, or use the global admin account for the tenant.

Important: The admin account must have a full license assigned to it in order to be able to provision OneDrive profiles for each user during the migration process. If this license is not assigned, MigrationWiz will return an error. To resolve this issue, assign a license to the administrator account, and resubmit the migration.

Create Accounts

Set up accounts on Microsoft 365 and assign licenses. These can be created in several ways:

Manually, one at a time.

MigrationWiz will provision a OneDrive (SharePoint) profile for each user being migrated. However, it does not create the user accounts; they must be already created.

MigrationWiz cannot provision a OneDrive profile for blocked users. If a user is blocked, this will result in a provisioning or access error.

Set up app-based authentication

Set up the app-based authentication in the Microsoft 365 tenant. For specific instructions, see Sharepoint App-based Authentication.

MSPComplete Steps

Create Customer

  1. Click the Add button in the top navigation bar
  2. Click the Add Customer button on the All Customers page
  3. In the left navigation pane, select the appropriate workgroup and then click All Customers.
  4. Click Add Customer.
  5. Enter the new customer’s information in the Add Customer form. Primary Email Domain and Company Name are required. The rest are optional.
  6. Click Save.
  7. Repeat steps 1 through 4 for each customer you want to add. 

Purchase licenses

We recommend that you purchase the User Migration Bundle license for this migration scenario. 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. For questions on licensing, visit MigrationWiz Licenses

To purchase licenses:

  1. Sign in to your BitTitan account. 
  2. In the top navigation bar, click Purchase.
  3. Click the Select button and choose User Migration Bundle licenses.
  4. Enter the number of licenses you want to purchase. Click Buy Now.
  5. Enter a Billing address if applicable.
  6. Click Next.
  7. Review the Order Summary and enter a payment method.
  8. Click Place Your Order.

Apply licenses

  1. Select the correct workgroup on the top of the left navigation pane. This is the workgroup that the customer and migration project were created under. Your account must be part of the workgroup if the project was not created under your account.
  2. On the left navigation pane, click Customers.
  3. Click the customer that employs the user to whom you want to apply a User Migration Bundle license.
  4. Click the Users tab at the top of the page.
  5. Check the box to the left of the email for the user(s) to whom you want to apply a license.
  6. Click the Apply User Migration Bundle License button at the top of the page. It is recommended that users be added to the Customer page with the vanity domain. Then have the User Migration Bundle Licenses applied, before editing to show the .onmicrosoft domain, if the .onmicrosoft domain will be used for the migration.
  7. If there is at least one unassigned User Migration Bundle license available for each selected user, click Confirm.

MigrationWiz Steps

Create a Document Project

  1. Log in to MigrationWiz.
  2. Click the Go to My Projects button.
  3. Click the Create Project button.
  4. Select the Document project type. 
  5. Click Next Step.
  6. Enter a Project name and select a Customer.
  7. Click Next Step.
  8. Select endpoints or follow the steps below to create new endpoints. 

Endpoints

Endpoints are now created through MigrationWiz, rather than through MSPComplete. The steps for this section outline how to create the endpoints in MigrationWiz.

If you are selecting an existing endpoint, keep in mind that only ten endpoints will show in the drop-down. If you have more than ten, you may need to search. Endpoint search is case and character specific. For example, Cust0mer will not show up if the search is customer. We recommend keeping a list of endpoints you have created, along with any unique spellings or capitalization you may have used.

You may either use existing endpoints, or create new ones. 

To create a new source endpoint:

  1. Click Endpoints
  2. Click Add Endpoint
  3. Select Dropbox. 
  4. Leave the Provide Credentials option selected.
  5. Click Add Endpoint. 

To create a new destination endpoint:

  1. Click Endpoints
  2. Click Add Endpoint
  3. Select OneDrive for Business. 
  4. Add the URL for your OneDrive for Business. 
  5. Enter the administrator username and password in the proper fields.
  6. Enter the Azure Storage Account Name and Azure Access Key or select Microsoft provided Azure Storage.
  7. Click Add Endpoint. 

Add Users

Add the user accounts that will be migrated to the project. MigrationWiz allows you to bulk import users into the system.

You may use Bulk Add, Quick Add, or add the accounts to the MSPComplete customer. 

Bulk Add

To import one or more accounts:

  1. Sign in to your MigrationWiz account.
  2. Select the Project for which you want to perform the bulk import.
  3. Click on Add .
  4. Click on Bulk Add .
  5. Follow the instructions on the page.

Quick Add

This option allows you to add items o​ne at a time. You need to enter an email address, login name, and password for each user if you didn't enter administrative credentials when setting up the project. You only have to provide an email address if you entered administrative credentials when setting up the project.

Add Advanced Options

Team folders are a feature of Dropbox Business that allows admins to create folders that are instantly shared with all members of their team or organization. However, unlike standard shared folders, team folders don't have an owner assigned to them in Dropbox, and so they are not migrated by default as part of a document migration project.

Under Support/Support options:

  • InitializationTimeout=8. This will increase the timeout initialization timeout window to 8 hours. 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. 
  • ShouldMigrateSharedWithMeFolderAsSource=1 
  • TeamFolderOwnerEmail=<team admin email address> - This migrates the team folder only under the defined team admin account. 
  • If App Based Authentication is in use at the Destination, add DestPersonalSiteIsProvisioned=1

Data Center

  • Set the Preferred BitTitan Data Center. 

Run Verify Credentials

  1. ​Sign in to your MigrationWiz account​.
  2. Open the Project containing items you wish to validate​.
  3. Select the items you wish to validate.
  4. Click on the Start button in your dashboard.
  5. Select Verify Credentials from the drop-down list.

Once complete, the results of the verification will be shown in the Status section.​ 

Notify Users

Notify users that a migration is occurring. Send email to all users telling them the time and date of the migration. During this time, they should not modify any documents in their Source Dropbox accounts, because any modifications will not be included in the migration.

Run Migration

For small migrations, we suggest skipping the pre-stage pass and simply performing the full migration. However, for large migrations with more than fifty users, we do recommend the pre-stage migration.

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.

Pre-Stage pass

  1. Select the users you wish to migrate
  2. Click the Start button from the top
  3. Select Pre-Stage Migration
  4. Under the Migration Scheduling section, from the drop-down list, select 90 days ago
  5. Click Start Migration.

Full pass

  1. Select the users
  2. Click the Start button from the top
  3. Select Full Migration
  4. Click Start Migration

Run Retry Errors

Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.

If problems persist, contact Support.

Request Statistics

Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics.

Post-Migration Steps

  • Suspend the Source Dropbox user accounts to prevent users from inadvertently logging in and using the wrong accounts. Follow the instructions in the How do I suspend a team member's account on my Dropbox Business team? article from Dropbox.
  • Delete all the Azure containers used for this migration. This will prevent incurring post-migration Azure costs for these containers. Be careful to only delete the containers created for this migration.

 

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