This option allows Box and Office 365 administrators to migrate folders (and their subfolders and files) from within multiple Box Drives to one or more document libraries in a SharePoint Online Site Collection.
NOTE: If you attempt to connect or open a Box drive through the software and it does not respond, please review the section Alternate Framework.
This operation has the following requirements for use:
·The account used to perform the migration from Box needs to have Full Admin access to the Box tenant.
·The account used to perform the migration into SharePoint Online needs to have at minimuim Designer permissions to the destination Site Collection. Full Control or Site Collection Administrator are recommended to avoid potential permission related issues during migration.
·The person performing the migration will need to know the relationship between each user's Box user account and their corresponding Office 365 user account. Please see the User Mapping section for an overview on how to create a CSV User Mapping file.
·The destination sites and libraries must exist in SharePoint Online prior to migration.
Once the requirements above are satisfied, you can proceed with your Box to SharePoint Online migration.
1.On the Drives tab, Click the Copy Box button, and select "Copy Box to SharePoint".
2.Give your project a name.
3.Enter the username of your Box Administrator and click Connect.
4.When the Connect to Box popup appears. enter the Admin account's password and click Connect. If your Box authentication requires additional security steps (i.e. single sign-on) then click the "Claims" button and enter your Box Admin and Password credentials into the browser popup to continue.
NOTE: If you attempt to connect or open a Box drive through the software and it does not respond, you may require an alternate framework. Please review the section Alternate Framework for instructions on how to install the alternate framework.
5.In the SharePoint Connection Parameters section, specify the destination SharePoint Online site URL and then click Connect. When prompted, enter your Office 365 user login and password and then click Connect. If you receive any message other than successfully connected, double check the URL and make sure you are supplying a user login with sufficient permissions for this site. If you are still experiencing issues, please contact Support for further assistance.
NOTE: when connecting to a SharePoint Online Site in this step, please be aware that you may migrate content into any library within this site or any sub-site beneath it. If you want to migrate content to a different site collection, then you will need to configure a second migration.
6.Your next step is to click the Load from CSV button. This option is required in order to map which folders from Box are migrated into which specific document library in your SharePoint Online site(s).
The CSV format includes the following 5 headers and is specific to a single target SharePoint Online root location as defined in the SharePoint Site field.
1.Source User - This column defines the source Box user account which contains the folder that should be migrated. Your CSV file may contain one or more source Box user accounts.
2.Source Path - This column defines the path to the root folder (including all its child content) from Box that you wish to migrate. If you want to migrate all folders and root content from a Box user, simply enter a forward slash (/) in this column. Your CSV file may contain one or more source folder paths for each source Box user.
3.Target SharePoint Site - This column defines the site or sub-site you wish to use as your destination location. If you want to migrate to the root site as defined in the SharePoint Site URL, then simply enter a forward slash (/) in this column. If you wish to migrate to a sub-site of the root, then enter the relative path to your sub-site starting at the root level (i.e. /subsite1/subsite2). Please note that each defined target site or sub-site must already exist in SharePoint Online as this process will not create this new site. This will then result in an error during migration.
4.Target SharePoint List - Target SharePoint List - This column defines the document library you wish to use as your destination list. Please enter the library's Internal Name into this column. Please note that each defined target library must already exist in SharePoint Online as this process will not create this new library, if you do not do this, it will result in an error during migration.
5.Target folder path - This column defines the folder that you would like to use as your destination location. If you want to migrate to the root of the library defined in the Target SharePoint List column, then simply enter a forward slash (/) in this column. If you wish to migrate to a sub-folder of the root, then enter the relative path to your sub-folder starting at the root level (i.e. /folder1/folder2).
For an example CSV file downloaded from here. Please do not modify the first row (headers) of the CSV file, but do modify the remaining values starting in the second row to meet your needs.
7.Click the Check Box Users button in order to verify that the source users, as defined in the loaded CSV file, are found within your Box tenant. After the function is complete, all source users not found will be displayed in red font while users successfully located will remain in the default black font. This acts as a warning that you may have entered an invalid user or there is an issue locating the defined user(s). You may still proceed with the migration, however you should expect errors when trying to migrate from these users.
NOTE: Check Box Users only verifies if the source Box user account was located. It does not validate the existence or accuracy of any other value in the CSV file, so please be sure to visually confirm before proceeding.
8.Select the Box drives that you wish to include with this migration, or select the Load and Apply Report button, which allows you to load and apply an Analyze Box report, which then sets the Migration Priority for each user mentioned in the report. Click Next to continue.
NOTE: Each Migration Priority value can be changed if you click on the value in the Migration Priority columns (without user selection). It changes the migration queue but does not change the original report file. Priority in the wizard is not saved after the wizard has been closed.
9.The final page provides a few options to configure how the content portion of the operation should be configured.
Copy Content - A flag to determine if content is or is not included with this operation. When not included the remainder of the options will become disabled.
Include Versions - The process in which Box version history will be converted into SharePoint Online. You can specify whether All Versions or the specified most recent versions are included.
Incremental Copy - When enabled, the migration process will identify and migrate only that content which was created, modified or versioned within the defined interval (days, weeks or months).
Copy Permissions - Will convert Box folder permissions (known as Collaborators) into SharePoint Online folder permissions. Please refer to the following page for additional information: Box - Permissions and Mapping.
Skip Non-Owned Folders - This option addresses the scenario where folders appear in a user's Box account which are not owned by this user; meaning the user is a folder collaborator and not the folder "Owner". Skipping these folders will prevent duplicates from being migrated into SharePoint Online because the folder will be migrated only once when the folder "Owner" is migrated. Please refer to the in-application Help button for additional details.
Re-Map Users - Will allow both permissions (if included) and user metadata like Created and Modified By to be properly mapped from Box to Office 365. Please refer to the following page for additional information: User Mapping. Please note that this mapping file can also contain Box Groups to SharePoint Groups or federated Active Directory groups in Office 365. Please refer to the following page for additional information: Box - Group Mapping
Skip Files Greater Than - When enabled, this option will skip any source files that are greater than the value specified (in MB or GB). An entry will be added to the post-migration log indicating which file(s) were skipped due to this configuration.
Enable Azure Turbo Mode: When enabled, this option utilizes Microsoft's SharePoint Online Migration API to increase the migration performance and throughput. A recommendation for optimal use of this API is larger sets of data; the more content, the better the throughput. Please review the User Manual for additional information as well as recommended configuration as this process is a resource intensive operation.
Because this API uses Azure storage as a staging area for the migration, it requires that you provide an Azure storage location. The options are to either utilize Microsoft supplied storage or to provide your own Azure storage location. If you wish to use your own Azure account, you must provide both the Azure Account Name as well as the corresponding Acces Key. If you cannot supply this information, please search our online Knowledge Base, User Manual or contact Support for additional information before proceeding or consider using the Microsoft Supplied Storage option. For more information please see the Azure Turbo Mode section.
NOTE: this function is optional and is only used to increase the migration performance to SharePoint Online or OneDrive for Business in Office 365. It does not provide any additional functionality that is not available when this option is disabled.
·Microsoft Provided Storage: This option allows you to use Microsoft provided Azure storage instead of providing your own for the purpose of utilizing Azure Turbo Mode.
NOTE: the migration end result will not differ regardless of your selection between Microsoft or User provided storage.
·User Provided Storage: This option allows you to provide your own Azure Storage instead of using one provided by Microsoft for the purpose of utilizing Azure Turbo Mode. It requires that you provide both your Azure Blob Storage Account Name as well as its corresponding Access Key by clicking the "Select" button to the right. If you cannot supply this information, please search our online Knowledge Base, User Manual or contact Support for additional information before proceeding.
NOTE: that the migration end result will not differ regardless of your selection between Microsoft or User provided storage.
oDefer Upload to Azure: When enabled, this option does not upload and immediately queue the import process from Azure storage, but rather saves the packages to a file location to then be uploaded and imported at a later time. This will allow you to use another application (at any time) to upload the content to Azure.
§To make use of the Deferred Upload option, the following process takes place:
1.First, you should setup the operation as usual using the Azure Turbo option.
2.Then, check the Defer Upload to Azure option and then Select the location where you wish to store the packages. Please be sure that there is enough disk space to accommodate all the packages that will be created.
3.During this process, the packages will be created, saved to this location and empty containers will also be created in your Azure storage.
4.After the operation completes, you will need to upload (using whichever upload utility you choose) the contents of each local folder into the appropriate Azure container. The folder names created in your local file location will be named exactly the same as the containers in Azure.
5.Once all the content from each folder is uploaded to the appropriate container in Azure storage, open the Azure Turbo Queue and choose the Refresh option.
6.Select one or more of the "Pending" jobs, right click and choose Process. The Import process has now begun and the jobs should soon switch to the status Queued.
oSend Notification: When selected, this feature will send emails to the listed recipients once Migrations are completed.
10. Click Finish to begin the migration.