Dropbox to OneDrive for Business Migration Guide

​​Introduction

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.

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.

Note: According 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 at this time.

If you are migrating to an Office 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. For more information, see Why does my Document Migration keep failing with Office 365 Small Business Tenant?

To enable folder mapping during your migration, see Folder Mapping From DropBox.

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. 

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

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.

To discover what items are moved with MigrationWiz in this scenario, and which items will not be moved, see Moved Items. Note that these items will vary by source and destination, so check the proper environment listings carefully.

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.

We are not able to support migrations with two-factor or multifactor authentication. 

 

Prepare Azure Environment

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

  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. For more information, see Estimate Azure Storage costs for migrations.
  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). For more information, see How do I buy an Azure subscription? 
  3. See How do I create an Azure Storage Account? to create your storage account. You will need to set up a STORAGE (General Purpose v1 or v2) account rather than a storage blob. 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 into the MigrationWiz migration project when specifying the Destination settings. We recommend that you create your 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.

Note: The access key information that is needed are these:

  • -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==”

 

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.
  3. Important, the v2 connectors 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 v1 connection instead of v2.
    Note: The invalid characters are: < > " ' &

 

Prepare the Destination Environment

  1. Create an administrator account in Office 365 to be used for migration, or use the global admin account for the tenant. For more information see How do I create an administrator account in Office 365, and then use this during migration?
    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. For more information, see Personal Site is not instantiated = PermissionsUserNotLicensed
  2. Set up accounts on Office 365 and assign licenses. These can be created in several ways:
    • Manually, one at a time.
    • By bulk import, via CSV file. For more information, see Microsoft instructions
    • By PowerShell script. For more information, see TechNet article
      Notes:
      • 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.
  3. Set up the app-based authentication in the Office 365 tenant. For specific instructions, see Sharepoint App-based Authentication.

 

MSPComplete Steps

  1. Create the customer. For more information, see View, Add, and Edit Your Customers
  2. Create the Source and Destination endpoints. For more information, see View, Add, and Edit Customer Endpoints
    • For the Source endpoint:
      • Click Endpoints Add Endpoint > Enter endpoint name > For endpoint type, select Dropbox.
      • Leave the radio button checked for Provide Credentials.
    • For the Destination endpoint:
      • Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select OneDrive for Business v2.
      • Add the URL for your OneDrive for Business.  For more information on finding this URL see How do I find the URL for my SharePoint Library or OneDrive for Business?
      • Enter the administrator username and password in the proper fields.
      • Enter the Azure Storage Account Name and Azure Access Key or select Microsoft provided Azure Storage.
  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. Create the Document Migration project. Read the How do I create a new migration project? article for more information.
  2. Add the accounts (items) that will be migrated to the project. For more information, see How do I add items to my migration project?
  3. Set Project Advanced Options. For more information see What project Advanced Options are available?
    • Under Support/Support Options add:
      • InitializationTimeout=8. This will increase the timeout initialization timeout window to 8 hours. For more information, see Cannot get folders from My Drive.
        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.
      • ShouldMigrateSharedWithMeFolderAsSource=1  For more information, see How do I migrate Dropbox Business team folders?
      • TeamFolderOwnerEmail=<team admin email address> - This migrates the team folder only under the defined team admin account. For more information, see How do I migrate Dropbox Business team folders?
      • If the migration project is a long-term project, it may be necessary to add an additional Advanced Option for use during the final migration pass to verify the contents of previously migrated items. For more information, contact Support.
    • Set the Preferred BitTitan Data Center. For more information, see How do I specify the data center to use for my migration?
    • BitTitan has no limitations to the number of folders per migration. Any folder limits will be set by Microsoft. 
  4. Run Verify Credentials. For more information, see How do I verify credentials?
  5. Notify users that a migration is occurring. Send an email to all users letting them know 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.
  6. Perform the migration, using one of the following strategies:
    • Full Migration strategy. For more information, see How do I start a migration?
      • For small migration projects that are less than 50 users, we recommend a Full Migration strategy. This is a single, full-pass migration.
    • Pre-Stage Migration Strategy:
      • Pre-Stage pass. For more information, see How do I start a migration?
      • Full (Delta) pass. For more information, see How do I start a migration?
        • For large migration projects that are more than 50 users, we recommend Pre-Stage Migration strategy. This is a multiple-pass migration.
  7. Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. For more information, see How do I request statistics for my migration project?

 

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?
0 out of 0 found this helpful