This is the complete onboarding task flow for migrating folders and documents from Box to Microsoft SharePoint Online using the v2 Endpoint.
The key difference for this 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.
This is a one-to-many migration path. This means that data that belongs to one user will be migrated into a shared document library. This is a rare business case because individual data would then be accessible by multiple people.
If performing a Box to OneDrive for Business migration, refer to Box to OneDrive for Business Migration Guide.
SharePoint Online has certain limitations. You need to be aware of these limitations before migrating. They are documented in the following article: What limitations of SharePoint Online or OneDrive for Business should I be aware of when migrating?
This migration scenario is free and requires no MigrationWiz licenses.
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.
- 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.
- 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?
- 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
- Create a Box user account that will be used for the migration and grant main admin privileges to that user. For more information see How do I create an administrator account in Box to be used for migration?
- Create a list of the Box user accounts that need to be migrated from the Source. You can do this by exporting the list of Box user accounts to a CSV file. From the admin console, click the Users and Groups icon. Under the Managed Users tab, click Export Users. Then add the users to the Customer page with the instructions in this article: View, Add, and Edit Customers' Users
- 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
- Create a SharePoint Online administrator or Site Collection administrator account to be used for migration, or use the global admin account for the tenant. More information on these can be found here.
- Create the SharePoint site.
Note: Make a note of the site URL where the document libraries will be stored. This will be entered when creating your MSPComplete Destination endpoint.
- Create the structure of the document libraries, and also create the actual document libraries on the Destination SharePoint Online site, before beginning the migration project.
Note: Refer to this Microsoft training video for more information: Create your document library.
- Create the customer. For more information see View, Add, and Edit Your Customers
- 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 Box.
- Leave the radio button checked for Provide Credentials.
- For the Destination endpoint:
- Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select SharePoint v2.
- Enter the URL for the top-level SharePoint document library. For more information on finding the URL for the SharePoint library, 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.
- For the Source endpoint:
Note: This must be either a Global administrator, SharePoint Online administrator, or a Site Collection administrator account.
- Create the Document Migration project. Read the How do I create a new migration project? article for more information.
- 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.
Note: The name that needs to be entered under Destination in MigrationWiz will be the text that is at the end of the site URL. This may be different than the actual name that has been set for the Document Library. The examples below help explain this:
- If the document library is named "Documents" and the URL is listed as "xxxxxx.sharepoint.com/Documents/", enter Documents as the document library name.
- If your document library is named "Documents" but the URL says "xxxxxx.sharepoint.com/Shared Documents/", the name of the document library that needs to be entered is Shared Documents.
- Click Add and enter the email address of each Box.com user for Source, and the corresponding document library name at the Destination that the Source documents will be migrated into.
- Under Support/Support Options add:
InitializationTimeout=8- This increases the initialization timeout window to eight hours.
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.
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.
- Select the users > From the top navigation, click the Start button > From the drop-down list, select Full Migration > Click the Start Migration button.
- This will change the status to Waiting For User. An email will then be sent to the Source email address user with a subject: ACTION REQUIRED: Information required for your migration. The user will need to open the email and then grant approval for the migration by following the steps detailed in the email.
- 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.