Chat now with support
Chat with Support

Metalogix Essentials for Office 365 2.7 - User Guide

Copyright Tool Overview
General Tool Configuration Profile Manager Proxy Mode Azure Turbo and CSOM Creating User Mapping Creating User and Template Reports Support and Troubleshooting Activation Modes of Migration
Home Tab Migration Analysis Tab Migrator Tab
Interface Connect to Resources Copy Sites Live Compare Copy Lists and Libraries Copy, Move, and Tag SharePoint Content Copy Alerts In-Place Tagging of SharePoint Items Incremental and Delta Copy Forms Migration Workflow Migration Save Site to XML
File Manager Tab Drives Tab
Interface Overview Migration Job Structure Connecting to Resources Copy Google Drive Copy File Share Copy My Sites to OneDrive for Business Copy Tenant Copy Box Copy Dropbox Nintex Deployment
Security Manager Tab Term Store Manager Tab Administrator Tab Backup Tab
Interface Overview Backup Job Structure Advanced Search Retention Policies Storage for Backup Import/Export Backup Archives Connecting to SharePoint and OneDrive for Business Connecting to Cloud Storage Hyper vs Classic Backup Setup Hyper SharePoint Online Backup Hyper OneDrive Backup Hyper Office 365 Groups Backup Smart Backup Classic SharePoint Online Backup Classic OneDrive Backup Classic Office365 Groups Backup Classic Mailbox Backup Change Properties for Backup Admin Management Scheduling Backup Jobs Backup Project Conversion
Help Tab View Tab Architect Tab Public Folders for SharePoint Tab Informant Tab Scripts Appendix About

Box- Unsupported Objects

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

·Box Notes

·Box Bookmarks

·Comments

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

Copy Box to an Office 365 Group

This option allows administrators to move content from multiple Box Accounts to Office 365 Group Sites ("Documents" library) in a single operation.

info

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 minimum of Site Collection 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".
copy box to office0001

2.Select a Profile and give your project a name.
copy box to office001

3.Enter the username of your Box Administrator and click Connect.
copy box to office2

4.When the Connect to Box popup appears, enter the Admin account's password and click ConnectYou will return back to the migration configuration where a "Successfully connected to Box" message will appear.
copy box to sharepoint3

info

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

6.When prompted, enter your 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.
copy box to office4

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

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.

info

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.

Analyze OneDrive 4

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.
 
sales@company.com,Office365 Group Name
marketing@company.com,Office365 MarketingGroup
IT@company.com,IT Group
scott@company.com,swilson@contoso.com
bill@company.com,bgeorge@contoso.com
 
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.
 
user@box.com,Office 365 GroupName(user@contoso.com
 
The software will migrate the content from the source drive "user@box.com" to the Documents libary in the group "Office 365 GroupName".  The metadata and shared permissions of Box user "user@box.com" will be mapped to the Office 365 user account "user@contoso.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.

info

NOTE: If the Group does not exist on the target it will be created using the migration administrator as the owner.

copy box to office6

11.The final page provides a few options to configure how the content portion of the operation should be configured.

Content Options:
copy box to office7

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.

Advanced Options:
advanced options in Drives wizard

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.

info

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.

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

info

NOTE: User Provided storage will give you access to Azure logs for a longer period of time than Microsoft provided storage. It will also allow you to perform the migration faster with less throttling.

Send Notification: When selected, this feature will send emails to the listed recipients once Migrations are completed. Enter a specific user email address. For two or more, separate each email address with a comma. Set up User Notifications here in order to use this feature. 

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

info

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.

Copy Box to Microsoft Teams

This option allows Box and Microsoft Teams administrators to copy content from within multiple Box Drives to their respective Microsoft Teams sites in a single migration.

info

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 Microsoft Teams needs to be a minimum of Site Collection 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 Microsoft Teams user account.

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

Once the requirements above are satisfied, you can proceed with your Box to Microsoft Teams Site migration.

1.On the Drives tab, Click the Copy Box button, and select "Copy Box to Microsoft Teams".
copy box to MSteams0001

2.Give your project a name.
copy box to microsoftteams001

3.Enter the username of your Box Administrator and click Connect.
copy box to microsoftteams2

4.When the Connect to Box popup appears, enter the Admin account's password and click ConnectYou will return back to the migration configuration where a "Successfully connected to Box" message will appear.
copy box to sharepoint3

info

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

6.When prompted, enter your 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.
copy box to office4

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

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.

info

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.

Analyze OneDrive 4

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 Microsoft Team name as well as maintain content authorship.  If your user accounts differ between Box and Microsoft Teams 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 a Microsoft Team by name while lines 4-5 in the same file are used to map the Box user accounts to their respective Microsoft Team user accounts to maintain item authorship.
 
sales@company.com,MicrosoftTeams Name
marketing@company.com,MicrosoftTeams MarketingGroup
IT@company.com,IT Group
scott@company.com,swilson@contoso.com
bill@company.com,bgeorge@contoso.com
 
If you would like to migrate source accounts to a target Teams channel, use the following mapping.
 
scott@company.com,swilson@contoso.com,ChannelName
 
The third column in this CSV will map the users to the specific target channel.

info

NOTE: When using the Teams Channel, keep the following in mind:

·When adding a Teams Channel to your CSV be sure to enter the name exactly, it is case sensitive. If the name is entered improperly Essentials will assume it is a folder and will create a folder with this name on the target site collection.

·When the channel column is missing in the mapping then the migration will use the General channel by default.

·When the channel is missing on the target, then a folder will be created with the channel's name in the Shared Documents section of MS Teams.

10.Click Check MS Team in order to begin the validation process​. This process will validate that the supplied user mapping is correct (MS Teams were located) and check to determine if each Team currently has a Site provisioned.  Click Next.

info

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.

copy box to microsoftteams5

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

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 Microsoft Team 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 Microsoft Teams 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.
 

info

NOTE: The 'Migrate to folder' option can be used when migrating to a MS Teams Channel. This option will create a new sub-folder in the channel or use an existing sub-folder by this name.

Advanced Options:
advanced options in Drives wizard

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.

info

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.

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

info

NOTE: User Provided storage will give you access to Azure logs for a longer period of time than Microsoft provided storage. It will also allow you to perform the migration faster with less throttling.

Send Notification: When selected, this feature will send emails to the listed recipients once Migrations are completed. Enter a specific user email address. For two or more, separate each email address with a comma. Set up User Notifications here in order to use this feature. 

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

info

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.

Copy Dropbox

Metalogix Essentials for Drives provides a simplified, wizard driven experience to migrating content in, out, or between various drive management systems (local or cloud based).  It can also provide additional functionality to managing some or all OneDrive for Business sites within a specific Office 365 tenant.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating