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.

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. 

First Migration?

This migration guide contains the necessary steps to perform the actual migration, but there are many steps to preparing for migration. If this is your first time performing a migration, we have created a Migration Planning & Strategy Guide to walk you through planning, set-up, and general migration best practices. If you have never performed a migration before, we suggest reading that before beginning the steps outlined in this scenario.

Prerequisites

Please consider meeting the following prerequisites before starting your migration process.

Licensing

We recommend that you purchase User Migration Bundle licenses for this migration scenario. User Migration Bundle licenses allow the performance of multiple migrations with a single license. For questions on licensing, visit MigrationWiz Licenses.

To use your license by following the next steps:

  1. Purchase Licenses.
  2. Create a Customer.
  3. Apply Licenses.
  4. Review Considerations.
Purchase Licenses Create a Customer Apply Licenses Considerations

Purchase licenses by following the steps below:

  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.

Limitations

  • 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.
  • MigrationWiz does not support the migration of Dropbox Teams Folders from the home location at this time. 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.
  • 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.
  • 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 a 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 instead will use end-user credentials. 

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

Migrated Items

Please click the bars below to check the migrated and non-migrated items. We are constantly working to create a better migration experience for you so these items may change over time.

Which items are migrated?
  • Folders
  • Shared Folders
  • Code Files
  • Documents
  • Images
  • Forms
  • Executables
  • Videos
  • Audio Files
Which items are not migrated?
  • Dropbox shared folder permissions
  • Dropbox Notes
  • Dropbox Bookmarks
  • Dropbox Tags
  • Dropbox Teams
  • Version history
  • Last Modified
  • .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 perform 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://portal.azure.com
    2. Go to the Storage account you have created for Migration purposes.
    3. Click Access Keys for the access keys that need to be entered when creating the Destination endpoint. We recommend that you create an Azure Storage Account in the same Microsoft data center as the Destination Office 365 tenant. 
    4. Take note of the Storage Account Name and the Primary Access Key as follows:
      • -accesskey – This is the Storage account name for the Blob – example “accountname”
      • -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

Please consider the following information when preparing your source environment.

  • Users being migrated need to be licensed to use OneDrive in the source tenant.
  • Users being migrated must not be blocked from signing into the source tenant.
  • Source OneDrives must not be set to read-only. This is initially for setup. Steps for setting up for read-only can be found under the Run Verify Credentials section later in the guide.

OneDrive Prerequisites

  • Create an admin account in Microsoft 365 for the migration, or use the global admin account for the tenant.
  • The easiest approach to follow is to use the global admin account. This was set up at the time of tenant creation. However, if you do not wish to use this global admin account during migration, then a new user account can be created instead. This will then need to be granted full access rights to each user.
  • The admin account must have a full license assigned to it, to provision OneDrive for Business profiles for each user during the migration process. 

Application Permissions for OneDrive

Continue configuring your destination environment by selecting one of these application permissions options and following the steps to enable permission levels at the destination.

Delegated Authentication App-Based Authentication

The easiest approach is to use the global admin account set up at the time of tenant creation. However, if you do not wish to use this global admin account during migration, then a new user account can be created instead. This user account needs to have a license assigned that includes OneDrive and be granted Site Collection Administrator privileges to OneDrive in the project.

  1. Create a user in Microsoft 365 and assign a license that includes SharePoint. For step-by-step instructions, see the Microsoft article Add users individually or in bulk to Office 365.
  2. Set the administration privileges. Grant one of the permission levels listed below to the user account to be user as the administrator for the endpoint in the project.
  3. Add the admin account, created in step 2, as a Site Collection Admin to the endpoint.

    Important

    The Global Admin or SharePoint Admin role does not automatically grant Site Collection Administrator rights to a SharePoint or OneDrive site.
  4. Go to MigrationWiz-SharePoint-Delegated and consent to the app access when prompted. Once you click on Accept, you will be redirected to the BitTitan login page. This is normal and the page can be closed.

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

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 created through MigrationWiz. If you select an existing endpoint from the dropdown, it will only show ten endpoints. If you have more than ten, you may need to search it.

Consider that 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. 

Create your Endpoints

Please review the following tabs to create your destination and source endpoints.

Source Endpoint Destination Endpoint

Create your source endpoint by following the next steps:

  1. Click SOURCE SETTINGS.
  2. Click New
  3. Under Endpoint Type, select Dropbox. 
  4. Leave the Provide Credentials option selected.
  5. Click Add Endpoint. 

Region of Destination Tenant

MigrationWiz displays a dropdown to select the Preferred Region of the Tenant at the destination endpoint. This value updates the Preferred Region of the Destination Tenant field in the project's Advanced Options, and vice versa. You will notice that both values are always the same.

The Region of Destination Tenant feature optimizes the migration performance and speed when choosing the region closest to the destination tenant.

Tip

You can find the region of your destination tenant directly in the Microsoft Entra admin center by going to Identity > Overview > Properties, and using the Country or region or the Data location.

Country or region.png

For more information on this topic, review this article. In case you need the multi-geo information you can refer to this article.

Warning

If you do not complete this field you will not be able to save your project and the “This field cannot be left blank.” error will appear.

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. 

Quick Add
This option allows you to add items one at a time. To do so, you only have to provide an email address if you entered administrative credentials when setting up the project. If you did not, enter the following user information:
  • An email address
  • Login name
  • Password
  • Mailbox status
Bulk Add

Bulk Add uses a CSV containing the source and destination email addresses for the users to add the users to the project. If migrating only a specific group from a tenant, we recommend using the Bulk Add option.

MigrationWiz allows you to bulk import mailboxes into the system.

To import one or more mailboxes:

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

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, so they are not migrated by default as part of a document migration project.

Support Tab

  • 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. 
  • DestPersonalSiteIsProvisioned=1 Use this advanced option if App-Based Authentication is used at the Destination.

Performance Tab

Set the Preferred Region of the Destination Tenant. This value should be set during the creation of the project, but you can always change it here. 

Run Verify Credentials

  1. ​Sign in to your MigrationWiz account​.
  2. Open the Project containing items to validate.
  3. Select the items 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 an 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.

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