Box to OneDrive for Business v2 Migration Guide

Introduction

This is the complete onboarding task flow for migrating folders and documents from Box to OneDrive for Business using the v2 endpoint.

The key difference for this type of migration scenario is that it requires an Azure subscription. This new v2 API leverages Azure to maximize migration speed and bypass throttling.

Complete each step in the order listed. Links to corresponding Knowledge Base articles are provided.

The Destination must be OneDrive for Business, not the personal OneDrive version.

If migrating to an Office 365 Small Business Tenant account, the processes will be very similar. However you will not be able to use administrator 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?.

• Note: We no longer support migrations to or from GoDaddy-hosted OneDrive.

To see what items are included in the migration, see What items are migrated with MigrationWiz? and What items are not migrated with MigrationWiz?

MigrationWiz is a migration solution (not a synchronization solution) and will NOT propagate updates, deletes, or moves of the items previously migrated in the first migration pass because 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. For more information, visit Project Sharing in MigrationWiz.

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 Source Environment

1. Create a Box user account that will be used for the migration, and grant main administrator privileges to that user. For more information see Transferring Admin Privileges to Another User.
2. Create a list of the Box user accounts that need to be migrated from the Source. This can be done by exporting the list of Box user accounts to a CSV file. Box has instructions to run various reports on this page. It may also be possible to use these instructions: From the administrator console, click the Users and Groups icon. Under the Managed Users tab, click Export Users.
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 Destination Environment

1. Create an administrator account in Office 365 to be used for migration, or use the global administrator 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 administrator 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 App-based Authentication. For specific instructions, see App-Based Authentication.
3. 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. Microsoft instructions
• By PowerShell script. TechNet article

Notes:

• MigrationWiz can provision a OneDrive (SharePoint) profile for each user being migrated, if the user does not already have a OneDrive profile created. However, it does not create the user accounts; they need to have already been created.
• MigrationWiz cannot provision a OneDrive profile for blocked users. If a user is blocked, this will result in a provisioning or access error.

MSPComplete Steps

1. Create the customer. For more information see View, Add, and Edit Your Customers
2. Create the Box Source and Office 365 Destination endpoints. View, Add, and Edit Customer Endpoints.
   Notes:
   • When setting up the Box endpoint, leave the radio button for Provide Credentials selected.
   • The OneDrive for Business endpoint will be set up using the App-based Authentication created during the Prepare the Destination steps.
3. Purchase User Migration Bundle licenses. User Migration Bundle licenses allow multiple types of migrations to be performed with a single license. Refer to these articles for more information:
   • How do I purchase licenses?
   • Migration License Types
   • Apply User Migration Bundle licenses to the Customer's Users

MigrationWiz Steps

1. Create the Document Migration project. Read the How do I create a new migration project? article for more information.
2. After creating the project, click the Save button. This will take you back to the Authorization page. Click the Request Access Token button. Enter the email address of the Box.com administrator, and the password of this Box.com account. Click the Authorize button. Click Grant Access to Box. Once the Source Authorization completes, click Save Project.
3. Add the accounts (items) that will be migrated to the project. For more information see How do I add items to my migration project?
4. Set the Project Advanced Options. For more information see What project Advanced Options are available?
   • Under Support/Support Options add:
     • InitializationTimeout=8 - This increases the initialization timeout window to eight hours. For more information see Cannot get folders from My Drive.
     • RenameConflictingFiles=1 - This automatically renames the files that have the same name. This will rename the files to their original file names, followed by a unique identifier hash so it does not interfere with the original name and search. For more information see How do I migrate multiple files with the same name into OneDrive?.
     • 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 on this setting, see MigrationWiz - SyncItems Migration Option.
       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.
     • BitTitan has no limitations to the number of Folders per migration. Any folder limits will be set by Microsoft.
5. Run Verify Credentials. For more information see How do I verify credentials?
6. 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 Box accounts, because any modifications will not be included in the migration.
7. 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. For more information, see How do I start a migration?
     • Pre-Stage pass. 
     • Full (Delta) pass. 
       Note: For large migration projects that are more than 50 users, we recommend Pre-Stage Migration strategy. This is a multiple-pass migration.
8. Click the bar 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

• To prevent users from inadvertently logging in and using their Box accounts, decommission the Box user accounts, or change their passwords.
• 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.