Metalogix Essentials for Office 365 2.2.3 - User Guide

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.

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 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 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 satisified, 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".

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

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

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

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

6.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.  Select the Box drives that you wish to include with this migration and click Next to continue.

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

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

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

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.

Advanced Options:

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.

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

10.Click Finish to begin the migration.

Copy Dropbox Business to OneDrive for Business

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

This operation has the following requirements for use:

·The account used to perform the migration from Dropbox Business needs to have Team Admin access to the Dropbox Business 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 Dropbox 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 Dropbox Business to OneDrive for Business migration.

1.Switch to the Drives tab and click the Copy Dropbox button, then select "Copy Dropbox to OneDrive".

2.When the wizard appears, enter the username of your Dropbox Administrator, and enter the Access Token associated with your Dropbox Business tenant.  If you do not currently have one, please review the steps in the Dropbox Business Access Token section in order to continue. Once all of the Dropbox connection parameters have been entered, Click Connect.

If you receive any message other than Successfully connected to Dropbox, double check your supplied information and try again.  If you are still experiencing issues, please contact Support for further assistance.

3.In the Target Office 365 Connection Parameters section, specify your tenant SharePoint Administration Center URL and then click Connect (i.e. https://tenant-admin.sharepoint.com).  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.

4.Click the Load from Dropbox button to load in a list of available Dropbox Business drives to include with this migration.  For performance reasons, if you have a large number of Dropbox Business 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.  Select the Dropbox Business drives that you wish to include with this migration and click Next to continue.

3.Select the Re-Map Users option then click the Load button in order to load user mapping CSV file.  User mapping is required so the software can properly resolve the differences between your users' Dropbox Business and Office 365 accounts.

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 site provisioned.  If one or more valid users do not have a OneDrive for Business site currently provisioned, select them and check Create personal sites for the selected users option. Click Next.

5.If required, modify your Content Option settings​ as described below.
 
Content Options:

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 Dropbox Business 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 Dropbox Business folder permissions into OneDrive for Business shared folder permissions.  Please refer to the following page for additional information. Dropbox Business - Folder Permissions and Mapping

Skip Non-Owned Folders - This option addresses the scenario where folders appear in a user's Dropbox Business account which are not owned by this user; meaning the user has folder access (Editor or Viewer) but is 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.
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.

Apply Filter - Optionally, select from a series of filterable parameters to include or exclude specific content during migration.

Advanced Options:

 
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.

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

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.

6.Click Finish to begin the migration.

Dropbox Business - Access Token

In order for the software to access and migrate content from all users' Dropbox Business drives, you will need to generate and supply an Access Token which grants access to the Dropbox Business API.

To generate your Dropbox Business Access Token, please perform the following steps:

1.Login to https://www.dropbox.com/developers/apps using your Team Admin account.

2.Go to the My apps section and click Create App

3.On the new app creation page, select the following options

§Choose an API:  Dropbox Business API

§Choose the type of access you need:  Team member file access

§Name your app:  enter any name

Click Create App.

4.When the app is created, it should open the App Settings page.  If it does not, return back to the My apps section and open this newly created app and click on the Settings tab.

5.Locate the "Generated access token" option and click the Generate button.

6.Copy the access token that appears to a file for safe keeping.  This token is required for connection.

Dropbox Business - Group Mapping

This may be necessary when you have a Dropbox Business team group assigned to a shared folder that you want to translate into an Azure Active Directory group in your Office 365 environment.

First, open the Shared view of the folder that you want to map the group from.

As we can see in the screenshot above, "TestGroup" is the group. When we would migrate this as-is (with no mapping) into OneDrive for Business a SharePoint group will be created with the same name "TestGroup".

If you would like to translate this into an existing Azure AD Group, we first need to locate the "Account" name of this Azure AD group.  You can find the "Account" value by opening the User Information view for this group in either a SharePoint Online or OneDrive for Business site.

Copy the Account out of this screen for the group that you want to map into.

Make a new entry in your User Mapping file for the group.

As you can see, use the information from the Dropbox Business 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 the Dropbox Business group to your existing AD group in OneDrive for Business.