This option allows administrators to move content from multiple Box Accounts to Office 365 Group Sites ("Documents" library) in a single operation.
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 Enterprise Admin access to the Box tenant.
·The account used to perform the migration into an Office 365 Group Site needs to be a Global Administrator in this Office 365 tenant.
·The person performing the migration will need to know the relationship (user mapping) between each user's Box user account and their corresponding Office 365 Group name and Office 365 user account.
·The Office 365 Group and its Site must already exist.
Once the requirements above are satisfied, you can proceed with your Box to Office 365 Group Site migration.
1.On the Drives tab, Click the Copy Box button, and select "Copy Box to Office 365 Groups".
2.Select a Profile and 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. You will return back to the migration configuration where a "Successfully connected to Box" message will appear.
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 Target Office 365 Connection Parameter section, enter your tenant SharePoint Administration Center URL, and then click Connect (i.e. https://tenant-admin.sharepoint.com).
6.When prompted, enter your Office 365 Global Administrator login and password. Click Connect. If you receive any message other than "Successfully connected to SharePoint Admin", double check the URL and make sure you are supplying a Global Administrator login for this tenant. If you are still experiencing issues, please contact Support for further assistance.
7.Click the Load from Box button to load in a list of available Box drives to include with this migration. For performance reasons, if you have a large number of Box drives in your tenant you may wish to create a single column CSV file with the user accounts and choose the option Load from CSV instead.
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.Select Re-Map Users option and load your mapping CSV file. Group mapping is required (user mapping may also be included) so the software can properly resolve the differences between your users' Box account and the corresponding Office 365 Group name as well as maintain content authorship. If your user accounts differ between Box and Office 365 then you will want to add your user mapping to this same file.
In the example below, lines 1-3 illustrate mapping a source Box to an Office 365 Group by name while lines 4-5 in the same file are used to map the Box user accounts to their respective Office 365 user accounts to maintain item authorship.
firstname.lastname@example.org,Office365 Group Name
If you wish to migrate one or more source accounts to a single Group library while also remapping the user account for the purpose of metadata and sharing, please use the following format in your mapping file.
email@example.com,Office 365 GroupName(firstname.lastname@example.org
The software will migrate the content from the source drive "email@example.com" to the Documents libary in the group "Office 365 GroupName". The metadata and shared permissions of Box user "firstname.lastname@example.org" will be mapped to the Office 365 user account "email@example.com".
10.Click Check Office 365 Groups in order to begin the validation process. This process will validate that the supplied user mapping is correct (Office 365 Groups were located) and check to determine if each Group currently has a Site provisioned. Click Next.
NOTE: If the group is not found, you may continue however no content for this mapping will be migrated. Alternatively, you may go back one page and remove the selected source Box account or modify your mapping file, reload the CSV and click the Check button again.
11.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 Office 365 Group Site versions. 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).
Skipped 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 Office 365 Group 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.
Skip files greater than - This provides the functionality to skip all files larger than the value specified. Unit of measure is configured for MB or GB.
Migrate to Folder - When this option is enabled, you can create a (or use an existing) root folder structure in the destination library where your source content will be migrated. You will need to define the path like this example:
/My Source Content/2017
In the above example, the folder "My Source Content" and subfolder "2017" will be created in the root library of your destination and all source content will be migrated to this folder location.
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.
Create User Specific Log File - If you would like a user specific log file (.txt format) created for each migrated Google Drive, that will be saved directly to that Group's "Documents" library, check this option before you finish. This log file will contain all the content that was included in the migration with both source and target URLs as well as any file renaming that took place and skipped files due to lack of ownership.
NOTE: Create user Specific log file is disabled if Azure Turbo Asynchronous mode is on. Supported only for CSOM or Azure Turbo Synchronous modes.
NOTE: Content permissions are not migrated because Office 365 Group permissions are maintained and enforced by the group membership and its roles (Owners, Members and Guests).
12. Click Finish to begin the migration.