Essentials for Office 365 2.15 - User Guide

Copy Google Shared Drive to SharePoint Online

This option allows administrators to move content of multiple Google Shared Drives to SharePoint Online default (Documents) libraries.

Pre-requisites

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

·The account used to perform the upload needs to be a minimum of Site Collection Administrator in this Office 365 tenant.

·A CSV file must have been created that maps each Google Shared Drive ID to the target SharePoint Online site.

·The person performing the migration will need to know the relationship (user mapping) between each source Google Shared Drive account and their corresponding SharePoint Online account.

·Each user account must have a SharePoint license assigned to it in Office 365.

To migrate content of Google Shared Drives, perform the following:

1.On the Drives tab click "Copy Google Drive" and select, Copy Google Shared Drive to SharePoint Online.

The Google Shared Drives to SharePoint Online wizard opens.

2.Enter a Project 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 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.

5. Click the Load From CSV or Load from Google Drive button. Note that Load from CSV will allow you to load users from a CSV file, which is the faster option as only the listed users are loaded.
 
Select the account(s) you wish to migrate.

6.Click Load from CSV and select the csv file containing Google Shared Drive to SharePoint Online mappings.  Click Check for sites to begin the validation process. This process will validate that the supplied site mapping is correct (Google Drive users and SharePoint Online sites were located).

7. Click Next.

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 SharePoint  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). You can select whether you would like to:

oInclude All Versions

oInclude The Most Recent Versions - this option allows you to specify how many recent versions you would like to copy the content from.

·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). To perform a Delta migration, enter zero in the field and select days as the time period. Delta migration is designed to be used in scenarios where both the source and destination may be modified during the course of the migration.

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

·Copy Permissions - When this option is selected, Google shared permissions will be converted to SharePoint Online permissions.

·Migrate to Folder - When this option is enabled, you can create, 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, for example:
/My Source Content/2017
In the above example, the folder "My Source Content" and sub-folder "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 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 into SharePoint Online.

·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 into the SharePooint Document library 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 enabled, the migration will identify these orphaned files and migrate them to the mapped  Document library.  In this library, a new folder named "Orphaned Files" will be created which will contain all the migrated orphaned files.  The use of this option can decrease overall migration performance.

·Re-Map Users - Use this option to load your user mapping CSV file (Please see this section for instructions on how to create a CSV User Mapping file for Google Drive). 

·Apply Filter - This feature allows the inclusion or exclusion of items by user defined criteria, such as date, size, file extension, file name, or file owner.

NoteS:
 
For the File Extension and Exclude Folders parameters only, you can use "," to set more than 1 criteria. For example, use this format "png,docx,pptx" to include multiple file extensions.
 
"Size" filter should have a whole number without decimals. It  is recommended that users not use the operators "Equal" and "Not Equal" to avoid difficulties with accurate file size, if the file size is greater than 1 MB.
 
Use the "Save Filter" option to save filter settings to a file and load them in different wizards or the Profile Manager.

Format Conversion:

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

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.

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. 

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.

Mapping Google Groups, Users, and Permissions to Office 365

This section provides instructions for mapping Google groups, users, and permissions when migrating to Office 365.

Google Group Mapping

When migrating from Google Drive to Office 365, it may be necessary to re-map your Google based groups into existing target 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. You can do so automatically using the Mapping Report wizard within Essentials, or manually with the following steps:

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, "EDI@domainname.com" is the group. When migrating this into OneDrive for Business or SharePoint Online, it will become "EDI At domainname.com".

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

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

Google User Mapping

When migrating from Google Drive to Office 365, it may be necessary to re-map your Google based user accounts into their target user accounts.

A migration example that may not require user mapping:

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

Based on the examples above, if your situation requires the use of a mapping file, please create it using the Mapping Reports wizard, or manually 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:
 

user1@companyA.com,user1@companyB.com

user2@companyA.com,user2@companyB.com

user3@companyA.com,user3@companyB.com

user4@companyA.com,user4@companyB.com

user5@companyA.com,user5@companyB.com

 
Click here to download an example user mapping file.