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

Google Group Mapping

When migrating from Google Drive to OneDrive for Business it may be necessary to re-map your Google based groups into existing Office 365 groups.

This may be necessary when you have a group on your Google document that you want to translate into another group in your Office 365 environment.

1.In your Google Drive, open the 'share' pane of the file that you want to map the group from.
As is shown in the image above, "" is the group. When migrating this into OneDrive, it will become "EDI At".

2.Find the Group that you want to map this Google Drive group to in Sharepoint. On this screen, copy the Account for the group that you want to map into within OneDrive.

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

As you can see, use the information from the Google 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 Google Drive to an existing group in OneDrive.

Google User Mapping

When migrating from Google Drive to OneDrive for Business it may be necessary to re-map your Google based user accounts into their new Office 365 user accounts.

A migration example that may not require user mapping:

Google User Account

Office 365 User Account

Both the username (user1) and domain ( are identical between Google and Office 365.  (If you are using a email to authenticate against Office 365, then you will need to map all users even if the usernames and domain are identical.)

A few migration examples that would require the use of a mapping file:

Google User Account

Office 365 User Account

The username (user1) is the same between Google and Office 365, however the domain has changed ( |

Both the username (user1 | and the domain ( | is different.

The domain is the same (, but the username has changed (user1 |

Based on the examples above, if your situation requires the use of a mapping file, please create it using the steps below.

1.Create a new blank worksheet in Excel.

2.In Column A, enter the list of Google User Accounts.

3.In Column B, enter the list of Office 365 User Accounts next to their respective Google Accounts.

4.When complete, save this to a CSV file.

If you are not using Excel, then please create this mapping in a text file and then change the file extension to CSV when complete.  The file format should look similar to this when viewed in a text editor:,,,,,

Click here to download an example user mapping file.

Google Permission Mapping

The application provides options to map domain and default Google permissions to SharePoint.

To enable migration of Google permissions, select the Copy Permissions option under Advanced Options in the copy wizard. The unique permissions granted to documents will be preserved unless you chose to map Google Permissions to SharePoint.

good drive copy permissions1

Copy Google Drive to an Office 365 Group

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


NOTE: If you have not already performed the prerequisite steps in Google, please go to this section first.  Once the prerequisite configuration is complete, return here to continue with the migration.

This operation has the following requirements for use:

·The Google Drive pre-requisites must be configured successfully prior to the migration.

·The account used to perform the migration into Office 365 Groups 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 source Google Drive account and their corresponding Office 365 Group name and Office 365 user account.

·The Office 365 Group and its Site must already exist.

To migrate the content of multiple Google Drives to Office 365 Groups, perform the following:

1.On the Drives tab click Copy Google Drive and selec "Copy Google Drive to Office 365 Groups".
Copy Google to office01
The Google Drives to Office 365 Groups Migrator wizard opens.

2.Select a Profile and provide your Google Admin login, P12 Key File and Service Account in the Google connection parameters area. This information is gathered directly from your Google environment, so if you have not already please refer to this section for the required steps.  Once the values are entered, click Connect.  If you receive any message other than Successfully connected to Google Drive, double check the prerequisite steps and then entered values.  If you are still experiencing issues, please contact Support for assistance.
Copy Google to Office2

3.Specify your tenant SharePoint Administration Center URL​ and then click Connect.  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 URL, 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 Google to Office3

4.Click Load from Google to load a list of available Google Drive accounts from your environment.


NOTE: For a large number of Google Drives (>1000), the Load from Google option may take several minutes to complete.

Copy Google to Office4

5.S​elect the Google Drive accounts that you wish to include with this migration and click Next to continue.

6.Check the Re-Map Users option and load your Group mapping CSV file (Please see this section for instructions on how to create a CSV Group Mapping file for Google Drive to Office 365 Group, user mapping may also be included in this CSV)
copy google to microsoft teams05
The CSV for Group mapping is required so that the software can properly resolve the differences between your users' Google account and the corresponding Office 365 Group name as well as maintain content authorship.  If your user accounts differ between Google Drive 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 Google Drive to an Office 365 Group by name while lines 4-5 in the same file are used to map the Google user accounts to their respective Office 365 user accounts to maintain item authorship.,Office365 Group Name,Office365 MarketingGroup,IT Group,,
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.,Office365GroupName(
The software will migrate the content from the source drive "" to the Documents library in the group "Office365GroupName".  The metadata and shared permissions of Google user "" will be mapped to the Office 365 user account "".

7.Click Check for 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.
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 Google Drive or modify your mapping file, reload the CSV and click the Check Office 365 Group button again.
Copy Google to Office5

8.If necessary, change content and file format conversion options 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 Google revision history will be converted into Office 365 Group versions.  Please note that this option is only referring to the major revisions (those shown as the "less detailed revisions") and not those that are automatically generated within Google Drives (those shown as the "more detailed" revisions).

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 Files - This addresses the possible scenario where content exists in the user's Google Drive "My Drive" area which is not owned by this user.  Skipping these objects will prevent duplicate content from being migrated to the destination.

Include First Reference File Only - This option addresses the possible scenario where a user creates reference objects (links using Shift + Z in Google Drive) of a file in various locations throughout their Google Drive environment.  Skipping these additional references will prevent duplicate files from being migrated to the destination by migrating only the first reference found.  Please note that the "first" reference is defined by a list of parent folders returned from Google Drive and the first may not always be the same one on subsequent or incremental migrations.  Please also note this option is only applicable to files, all referenced folders will be copied.

Include Orphaned Files - For the purpose of this option, an orphaned file is defined as a file that was created in a folder that was shared with this user and after the file was created, their permission to the shared folder was removed.  The file still exists in the user's Google Drive, however it does not reside in any visible folder path and can only be located using the Google Drive Search Bar.  When this option is enabled, the migration will identify these orphaned files and migrate them to the mapped Office 365 Group Site's Documents library.  In this library, a new folder named "Orphaned Files" will be created which will contain all the migrated orphaned files.


NOTE: The use of this option can decrease overall migration performance.

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.

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

Format Conversion:
Copy Google to OneDrive8

This set of options allows you to determine how Google formatted content will be converted into Microsoft compatible content.

Advanced Options:
Copy Google to OneDrive9

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

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

9.Click Finish to begin the migration process.

Please visit the following link to view the list of unsupported Google Drive objects.

Please visit the following link for an overview on how to script and schedule jobs such as Copying Google Drive to Office 365 Group.

Related Documents