This option allows administrators to move content from multiple Google Drives to Microsoft Teams 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 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 source Google Drive account and their corresponding Microsoft Teams group name and Office 365 user account.
·The Microsoft Team Group must already exist.
To migrate the content of multiple Google Drives to Microsoft Team Groups, perform the following:
1.On the Drives tab click Copy Google Drive and select "Copy Google Drive to Microsoft Teams".
The Google Drives to Microsoft Teams Migrator wizard opens.
2.Select a Profile and give your project a name.
3.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.
4.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.
5.Click Load from Google to load a list of available Google Drive accounts from your environment. Select the accounts you want included in this migration.
NOTE: For a large number of Google Drives (>1000), the Load from Google option may take several minutes to complete.
6.You can also choose to Load and Apply report option, which allows you to load and apply an Analyze Google Drive 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.
7.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 Microsoft Teams, user mapping may also be included in this CSV).
The CSV for Group mapping is required so that the software can properly resolve the differences between your users' Google account and the corresponding Microsoft Teams Group name as well as maintain content authorship. If your user accounts differ between Google Drive 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 Google Drive to an Microsoft Teams 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.
email@example.com,MicrosoftTeams 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.
The software will migrate the content from the source drive "firstname.lastname@example.org" to the Documents library in the group "MicrosoftTeamsGroupName". The metadata and shared permissions of Google user "email@example.com" will be mapped to the Office 365 user account "firstname.lastname@example.org".
8.Click Check MS Team 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 MS Team button again.
9.If necessary, change content and file format conversion options as described below.
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 Microsoft Teams 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).
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.
Skipped Non-Owned Objects - 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.
Apply Filter - Optionally, select from a series of filterable parameters to include or exclude specific content during migration.
This set of options allows you to determine how Google formatted content will be converted into Microsoft compatible content.
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).
10. 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 Microsoft Teams.