Chat now with support
Chat with Support

Metalogix Essentials for Office 365 2.2.3 - User Guide

Metalogix Essentials for Office 365 User Guide
Administrator Architect Backup
Interface Overview Common Functions
Connecting to SharePoint and OneDrive for Business Connecting to Cloud Storage Hyper Backup Creating a Full Backup Creating an Update Backup Creating an Exchange Online Mailbox Backup Creating an Office 365 Group Backup Creating a OneDrive for Business Backup Backup Resume Backup Search Restore from Backup Scheduling Backup Jobs Import/Export Backup Archives Moving the Backup Location Backup Project Conversion
Interface Overview Common Functions
Connecting to Drives Copy Google Drives to OneDrive for Business Copy Google Drive to an Office 365 Group Copy Google Drive to Microsoft Teams Copy File Shares to OneDrive for Business Copy File Shares to SharePoint Online Copy File Shares to an Office 365 Group Copy File Share to Microsoft Teams Copy My Sites to OneDrive for Business Copy OneDrive for Business to OneDrive for Business Copy Box to OneDrive for Business Copy Box to SharePoint Online Copy Box to an Office 365 Group Copy Box to Microsoft Teams Copy Dropbox Business to OneDrive for Business Copy Dropbox to an Office 365 Group Copy Dropbox to Microsoft Teams OneDrive Management Progress Tab Hyper Migration Path Length Overflow
File Manager Informant Migrator
Interface Common Functions
Connect to SharePoint and OneDrive for Business Copy Sites Live Compare Copy Lists and Libraries Copy, Move, and Tag SharePoint Content Copy Alerts Pre-Migration Analysis Azure Turbo Mode In-Place Tagging of SharePoint Items Incremental Copy Nintex Workflow Migration Orphaned Users Copy Preserving Content Authorship and Approve/Reject Statuses Reprocess Failed Items Save Site to XML Using Scripts and Integration With Windows Task Scheduler
Profile and Global Variables Public Folders for SharePoint Reporting and Re-Mapping Users and Templates Security Manager Term Store Manager Scripts Wizards Appendix

Copy Box to OneDrive for Business

This option allows Box and Office 365 administrators to copy content from within multiple Box Drives to their respective OneDrive for Business sites in a single migration.


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 OneDrive for Business needs to be a Global Administrator or SharePoint Administrator Role 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 user account.

·Each user account must have either a SharePoint or OneDrive license assigned to it in Office 365 and can not be in 'Blocked' status.

Once the requirements above are satisified, you can proceed with your Box to OneDrive for Business migration.

1.Switch to the Drives tab and click the Copy Box option and select "Copy Box to OneDrives" migration button.
copy box to onedrive1

2.When the wizard appears, enter the username of your Box Administrator and click Connect.
copy box to onedrive3

3.When the popup appears, enter this Admin account's password and click Connect.  Then "Grant access to Box" and you will return back to the migration configuration where a "Successfully connected to Box" message will appear.
copy box to onedrive4


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.

4.In the Target Office 365 Connection Parameters section, specify your tenant SharePoint Administration Center URL and then click Connect (i.e.  When prompted, enter your Office 365 Global Administrator or SharePoint 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 or SharePoint Administrator login for this tenant.  If you are still experiencing issues, please contact Support for further assistance.
copy box to onedrive7

5.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.  
copy box to onedrive8

6.Select the Box drives that you wish to include with this migration and click Next to continue.
copy box to onedrive9

3.Select Re-Map Users option and load user mapping CSV file.  User mapping is required so the software can properly resolve the differences between your users' Box and Office 365 accounts. Please see the User Mapping section if you require further instructions on created a CSV file for user mapping.
copy box to onedrive10

4.Click Check for users personal sites in order to begin the validation process. This process will validate that the supplied user mapping is correct (Office 365 user accounts were located) and check to determine if each user currently has a OneDrive for Business for site provisioned.  If any of the valid users do not have a OneDrive for Business site currently provisioned,  you can select them and check Create personal sites for the selected users option.
copy box to onedrive11

5.Click Next to continue.

6.The final page provides a few options to configure how the content portion of the operation should be configured.
Content Options
copy box to onedrive12

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 OneDrive for Business versions.

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 permissions (known as Collaborators) into OneDrive for Business 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 OneDrive for Business 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 - 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.
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.

Advanced Options
copy box to onedrive13

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.

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.
copy box to onedrive14


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).

6.Click Finish to begin the migration.

Box - Group Mapping

This may be necessary when you have a Collaboration group assigned to a Box Folder that you want to translate into an Azure Active Directory group in your Office 365 environment.

Finding the Box Group to map:

1.In the Box application, right click on the shared folder which contains the group you want to map the Office 365 group from, and select Share>Manage Collaborators.
copy box to onedrive groups1

2.As is displayed in the following image, the group for this example is "Box Dev".copy box to onedrive groups2

3.When migrating this as is (with no mapping) into OneDrive for Business, a SharePoint group will be created with the same name "Box Dev".

If you would like to translate this Box Group into an Azure AD Group, we first need to locate the "Account" name of the Azure AD group you would like to map the Box Group to. You can do this by following these steps:

1.On your SharePoint Online site or OneDrive for Business Site, select the cogwheel settings tab, and then click Site Settings.
copy box to onedrive groups3

2.Select "People and Groups" under User Permissions.
copy box to onedrive groups4

3.Click on the name of the Azure Group AD for which you wish to find the Account ID for user mapping.
copy box to onedrive groups5

4.The Azure Group AD account ID will be the set of numbers and characters listed beside "Account". Copy this sequence.
copy box to onedrive groups6

Make a new entry in your User Mapping file for the Group
copy box to onedrive groups7

As you can see, use the information from the Box side on the leftmost column and use the information from your SharePoint side on the rightmost column. When you use this mapping file, your group should map from Box group to your existing group in OneDrive for Business.

Box - Permissions and Mapping

Due to the differences between permissions in Box versus those in OneDrive for Business, the following permission mapping is performed during the migration.  If you wish to not include permissions, simply deselect the Copy Permissions option during configuration.

By Default, The "Copy Permissions" option only migrates Collaborators' permissions assigned to Box Folders. Files that are migrated to OneDrive for Business will inherit permissions from the folder that they reside in; linked and/or shared file permissions will not be retained.

However, you can include file level permissions by enabling the option in the Profile Manager.
Navigate to the Help tab, select Profile Manager, Box Options, and then select Copy File Level Permissions.
file level permissions

This option will allow you to copy file level permissions from the source account to Office 365 Locations. In order to do this, the above checkbox must be enabled and the Copy Permissions option must be enabled in the copy wizard.


NOTE: The Copy File Level Permissions option will not work, even if it is enabled in Profile Manager, when the Copy Permissions option is disabled in the copy wizard.

Box Access Level

OneDrive for Business Permission Level




View Only



Viewer Uploader (note 1)


Previewer Uploader (note 1)





Full Control


Full Control


NOTE: Viewer Uploader/Previewer Uploader -  Please note that the "Contribute" permission level in OneDrive for Business grants the user or group the ability to Delete whereas in Box this is not allowed.

Box- Unsupported Objects

The following Box objects are not supported when migrating to OneDrive for Business or SharePoint Online.

·Box Notes

·Box Bookmarks


·Custom Terms of Service

oIf the Box tenant has a Custom Terms of Service configured and a user has not Accepted the Terms of Service, then their Box account cannot be accessed and therefore their content cannot be migrated.

·External users (permissions and metadata)

·File and Folder descriptions

·Google Documents

·Google Spreadsheets

·Objects in the "Trash"

·Office documents created in Box with a size of 0 KB cannot be migrated using Azure Turbo

·"Tags" and Favorite labels

oThe item can still be migrated, however these labels will not be retained.

·Version history when a more recent version has a created date earlier than a previous version cannot be migrated using Azure Turbo.

·Mass migration from Box to Office 365 preserves file information available in the Version history section only, the original information from file shares gathered in the File Information section is not supported during migration.

Related Documents