Google Shared Drives to SharePoint Online Migration Guide

This article outlines the workflow for migrating Google Shared Drives to SharePoint Online document libraries. This migration scenario uses the Shared Document License type. We are not able to support migrations with 2-factor or multifactor authentication. The SharePoint Online destination endpoint does not support GCC High migrations.

Additional scenarios with known behavior and limitations are described at the end of this article.

First time?

If this is your first time performing a migration, we have created a Migration Planning & Strategy Guide to walk you through planning, set-up, and general migration best practices. If you have never performed a migration before, we suggest reading that before beginning the steps outlined in this guide. 


MigrationWiz is a migration tool, not a syncing tool. We do not have “live” monitoring of changes (as with a sync agent) and we cannot handle scenarios such as conflict resolution without user interaction. 

The maximum file size for migration through MigrationWiz varies by migration type and environment, but may never exceed 60GB.

Which items are migrated?

In the following tabs, you can find the migrated and non-migrate items.

Migrated Non-Migrated

Below you can find a list of migrated items.

  • Files
  • Folders
  • Permissions
  • Versions (up to 25)
  • Metadata
    • File/Folder name
    • Modified (based on the modified date of the latest version migrated)
    • Modified by
    • Created (based on the created date of the latest version migrated)
    • The description is migrated to the ‘Title' column at the destination. Migrated value is limited to the existing character limit of the 'Title’ field.
    • ‘Creator’ metadata is migrated but in some cases, this value may not be accurate. This is a current limitation without a workaround.
  • Shortcuts are migrated as a .URL file to the destination document library - if the target file exists within the same shared drive. Shortcuts are to be migrated as a subsequent migration step, after migrating all relevant documents & permissions.

Prepare the Source Environment

Set up the Google service account and API scopes

Create a Google Project

  1. Go to the Google Cloud Platform (GCP) Console and sign in as a super administrator. Choose one of the options below:
    • If you have not used the Google Cloud Platform Console before, agree to the Terms of Service and click Create Project.
    • If you have used Google Cloud Platform Console before, at the top of the screen next to your most recent project name, click Down to open your projects list. Then, click New Project.
  2. Enter a project name and click Create.

If you cannot create a project here, the create projects permissions might be disabled for your tenant. To check this, navigate to the Google Admin Center, click Apps > Additional Google Services, and select the Google Cloud Platform. Once there, you should see a toggled setting to allow users to create projects.

Enable APIs for the Service Account

  1. Click Menu > APIs & Services > Library, from the Google Cloud Platform Console.
  2. Enable the following APIs by selecting the specific API and clicking Enable.
    Repeat for each API listed below:
    • Google Drive API
    • Admin SDK

Create the Customer Tenant Service Account

  1. From the Google Cloud Platform Console, click Menu.
  2. Click IAM & Admin.
  3. Click Service accounts.
  4. Click Create Service Account and enter a name.
  5. Assign the role of Owner to the new Service Account by selecting Owner from the Role dropdown menu.
  6. Click Done to complete the service account creation.
  7. On the ‘Service accounts' page, click the vertical ellipsis under the 'Actions’ column for the service account created above. 
  8. Click the Create key.
  9. Make sure that JSON is selected and click Create.
    • Make sure that you download the key as a JSON file and make a note of the name and location of the file. This JSON file will be used when setting up the source endpoint in the migration project.
    • The JSON file must contain information in the following fields: “type”, “private key”, and “client email”. If these mandatory fields are empty, the file upload during the endpoint creation process will fail.

Setting the Scopes for the Migration

  1. From the Google Cloud Platform Console, click Menu.
  2. Click IAM & Admin.
  3. Click Service accounts.
  4. Find the service account that was set up in Step 3.
  5. Find the Unique ID field for that service account and copy the ID number. This is the Client ID number that will be used in a later step.
    • This field often needs to be added to the view. Click on the Column display options button and add a checkmark to Unique ID, then click OK.
    • This Client ID should be considered as confidential as Administrator account passwords and handled securely.
  6. Go to the G Suite admin page at
  7. Click on Security Access and Data Controls > API Controls.
  8. On the API Controls page, locate the section Domain-wide delegation.
  9. Click Manage domain-wide delegation.
  10. Click Add New.
  11. In the Client Name field, enter the Service Account Unique ID.
  12. For OAuth scopes, enter the scopes listed below:
  13. Click Authorize.

Source Shared Drive Membership Permission Requirements

  • Ensure that the source Shared Drives have an active member on the source tenant with a permission role above Viewer/Commenter.
  • For best results, we recommend at least one active member of the source tenant should be a member of the Shared Drive with the permission role of the Manager.

Prepare the Azure Environment

Microsoft-provided Azure Storage

We recommend using Microsoft-provided Azure storage for this migration. Refer to Microsoft documentation for more details. If you choose this option, skip to Prepare the Destination Environment.

Own Azure Storage

If you plan to use your own Azure storage, refer to the following steps to prepare your Azure environment. We recommend that you create your Azure storage account in the same Microsoft data center as the destination Office 365 tenant. You do not need to create any Azure containers for this migration.

  1. Estimate Azure storage costs. This step is optional but is useful to provide the customer with up-front storage costs ahead of time. 
  2. Buy an Azure subscription (or use the free one-month trial, but be aware that this option is only viable if you are performing a very small migration). 

Create an Azure Storage Account

You will need to set up a STORAGE (General Purpose v2) account rather than a storage blob.

  • Take note of the storage account name and the primary access key. (In Azure, from the storage screen, click Manage Access Keys at the bottom of the screen.) These need to be entered into the MigrationWiz migration project when specifying the destination settings. 

To create the Azure storage account, visit the Azure portal and follow the steps below.

  1. Click New.
  2. Select Storage.
  3. Select Storage account.
  4. Enter a name for your storage account.
  5. Choose Resource Manager for the Deployment model.
  6. Choose STORAGE (General Purpose v2).
  7. Record the storage account name (-accesskey, example: “accountname”) and primary access key (-secretkey, example: “W1RrDfkPNkfYfdVqizMNJjn5mXchwMP5uYBY8MsMqWTA7EubG911+4fZlki0Gag==”)
  8. In the Replication field, select Locally Redundant Storage (LRS).
  9. Select the subscription in which you want to create the new storage account.
  10. Specify a new resource group or select an existing resource group.
  11. Select the geographic location for your storage account.
  12. Click Create to create the storage account.

Now the storage account appears in the storage list.

Prepare Destination Environment

  1. Create a SharePoint Online administrator or Site Collection administrator account to be used for migration or use the global admin account for the tenant.
  2. Create the SharePoint site and make a note of the site URL where the document libraries are stored.
  3. Create the document libraries on the destination SharePoint Online site (optional). To do so, follow the steps from Microsoft: Create your document library.
  4. Ensure all necessary users/groups (including external users, if any) are set up at the destination SharePoint site and are available for your destination document library.

Application Permissions for SharePoint

Follow the steps to enable permission levels at the destination. This authentication process gives you control over who is entitled to use the destination.

  1. Ensure you are signed in as a Global Admin.
  2. Go to MigrationWiz-SharePoint-FullControl and consent to the app access when prompted.
  3. Create a new Security Group named “MigrationWiz” on the Office 365 Admin Portal.
  4. Create a new user.
  5. Add the new user to the previously created MigrationWiz security group as a member.
  6. Record these credentials for use during destination endpoint setup.

Steps to remove these permissions are provided below in the Post-Migration section.  

MigrationWiz Steps


This migration scenario uses the Shared Document License type. 

  • One license per line item in a project (e.g., per Google Shared Drive to SharePoint Online document library migration).
  • Data limit: 50 GB per license.

Purchase Licenses

  1. Sign in to your BitTitan account. 
  2. In the top navigation bar, click Purchase.
  3. Click the Select button and choose the license type you need.
  4. Enter the number of licenses you want to purchase. Click Buy Now.
  5. Enter a Billing address if applicable.
  6. Click Next.
  7. Review the Order Summary and enter a payment method.
  8. Click Place Your Order.

​​Licenses are released once payment has been received:

  • Via credit card, licenses will be available immediately upon payment.
  • Via wire transfer (100+ licenses), licenses will be available once payment has been received and accepted.

Set up a Document Migration Project

  1. Sign in to your MigrationWiz account.
  2. Click Go To My Projects.
  3. Click Create Project.
  4. Click on Document Project to create a new project.
  5. Click Next Step.
  6. Enter a project name and select a Customer. 
  7. Click Next Step.
  8. Select a Source endpoint from the endpoint dropdown menu. Otherwise, follow the steps below in the Create a Source Endpoint section.
  9. Click Next Step.
  10. Select a destination endpoint from the endpoint dropdown menu. Otherwise, follow the steps below in the Create a Destination Endpoint section.
  11. Click Save and Go to Summary.
  12. Click Save Project.

Create a Source Endpoint

If you have not already added the source endpoint, you need to click New to create the source endpoint and complete the fields below with the proper information.

  1. Name: Type any name you want for the endpoint. We suggest recording this name somewhere if you have multiple endpoints, as only the top ten will show when searching.
  2. Endpoint Type: Select Google Shared Drives from the source endpoint type drop-down list.
  3. Service account credentials: Select the JSON file created for the service account.
  4. Super Administrator Username: Enter the email for the super administrator for the source tenant.
  5. Click Add.

Create a Destination Endpoint

If you have not already added the destination endpoint, you will need to click New to create the destination endpoint and complete the fields below to set up the destination endpoint.

  1. Name: Type any name you want for the endpoint. We suggest recording this name somewhere if you have multiple endpoints, as only the top ten will show when searching.
  2. Endpoint Type: Select SharePoint Online from the destination endpoint type drop-down list.
  3. SharePoint Online Tenant URL: Enter the URL for the destination SharePoint tenant. (This is not the SharePoint Admin Center URL. Examples can be found further down in this guide)
  4. Office 365 Username / Password: Enter the email for the user authorized to run the migration for the destination tenant. 
  5. Use the credentials of the Office 365 user which was added to the MigrationWiz security group for the destination tenant.
  6. Click Add.

Add Line Items

There are three options for adding items. Choose which one you will use, then follow the steps below.


The Autodiscover option can be used to discover Shared Drives available from the Source environment. Once discovered, these can be imported to your project as line items. Associated Shared Drive IDs will also be linked to the line item.

The endpoint Administrator account on the source needs to be assigned the appropriate GSuite license for MigrationWiz to access Google Drive or Google Shared Drives for the Auto Discovery process.

The line item imported to your project will set the destination document library with the same value as that of the source shared drive. Please edit the line items and update the destination with appropriate values or document library path. Please refer to the next section on capturing the destination document Library path.

Bulk Add

This option allows you to add multiple items at once by copying and pasting from a spreadsheet or by importing a CSV file.

Quick Add

This option allows you to add items one at a time. You have to enter the Source Shared Drive name, drive ID, and destination document library path for each line item.

  • For Source - The drive ID field is optional. However, this drive ID must be entered correctly if the source tenant has a duplicate shared drive name.
  • For destination - Please ensure you enter the correct document library path (refer to examples in the next section).

Capturing the Destination Document Library Path for Line Item Setup

We recommend you to use the URL's document library path to ensure smooth migration. The following examples show the breakdown of different types of URLs and how to capture the correct document library path:


Example 1: Document library located under a site:


Example 2: Default Document library located under a site:


Example 3: Document library located under a subsite:


Example 4: Default Document library located directly under SharePoint Online root site:


Example 5: Document library located directly under SharePoint Online root subsite:GSD_7.png

Example 6: Site and Document Library names may contain special characters, but the URL may not reflect the same. The document library path must be captured correctly from the URL.



Advanced Options

The following advanced options show you some options that will help you to perform or complete a migration.

Support Tab

Consider that each Support Option includes the "=" character and is to be entered under the Support tab in the section named Support Options.

Add additional blank fields for new Support Options by clicking on the "+" button. In case you want to delete a field click the trash can icon.

  • InitializationTimeout=8 This increases the initialization timeout window to eight hours. This value is in hours, up to a maximum of 100 hours. Values above 100 are in milliseconds. This is useful for large migrations. For example:​
    • InitializationTimeout=2 will increase the timeout to 2 hours.
    • InitializationTimeout=8 will increase the timeout to 8 hours.
    • InitializationTimeout=14400000 will increase the timeout to 4 hours.
    • InitializationTimeout=21600000 will increase the timeout to 6 hours.
  • InvalidCharacterReplacementString=a (where 'a' is the string used to replace unsupported characters in file names)
    • SharePoint Online does not allow some characters to be used as file names. The advanced option attempts to replace instances of unsupported characters in file names with the specified string provided by the advanced option. (e.g. a)
    • Please refer to Microsoft's documentation for unsupported characters
  • LargeFileMigrations=1 and LargeFileMigrationsTimeout=7200000
    Migrations of over 15GB are now supported. These settings will prevent timeout errors when a Speedster import takes more than 10 minutes to complete.


    Values for LargeFileMigrations and LargeFileMigrationsTimeout are measured in milliseconds. The value of 720000 is only an example.

  • MigrateMembersToStandardGroups=1 Use this AO in case Google Shared Drive shared members are also migrated along with permission mapping to the standard groups.
  • RenameConflictingFiles=1 OneDrive/SharePoint does not allow files with duplicate names in the same folder. If your shared drive has multiple files with the same name in a folder, then use this advanced option to handle such conflicting files.
  • RenameConflictingFolders=1 Microsoft does not support duplicated names of folders and files, unlike Google Workspaces. Therefore, this AO enables the migration of folders with duplicated names from Google Drive as a Source into Microsoft destinations. With this AO, folders with duplicated names will be migrated with a suffix.
  • ShrinkFoldersMaxLength=200 The maximum path length before shrinking is 200.

    • When migrating to SharePoint Online, the path length limitation is a common issue. Refer to this KB to understand how this advanced option works.
    • Please note that, if the folder path is too long, even the truncated path using the advanced option may not be short enough to reach the SharePoint path length limit - in such case an error will be logged and the associated item will not be migrated. In this case, our recommendation would be to reduce the number of nested folders at the source to shorten the path.
  • UseGoogleAPIV2=1 This configuration avoids migrated items corruption and missing items issues. This is a default option. 
  • UserMapping="abc_user1@source-domain->pqr_user5@destination-domain"
    • The User Mapping command requires one line per user. Click the + to add additional lines. Replace the UPN addresses in the example with the actual UPN addresses.
    • By default, we match users from the source to the destination based on the prefix in their User Principle Name (UPN). For example, if the user UPN is “”, we match the “name” portion.

    • We recommend using  UserMapping=">" to set the new or correct name for each user when:

Source/Destination Tab

  • Set the number of versions to be migrated per project requirement and click Save.
    • The minimum number of versions to migrate is 1, the maximum number is 25. 
    • The default selection for the number of versions is 1. Please update this value as per your requirements.
  • Migrating Shared Drive membership permissions to Document Library level permissions.
    • By default, Shared Drive membership permissions are not migrated to Document library-level permissions. If you wish to migrate the Shared Drive membership permissions to Document library-level permissions, select Migrate Shared Drive membership permissions to document library permissions and click Save.


      Custom permissions at the destination will be retained. However, if a document library inherits from the site, this inheritance is broken, and the destination library permissions are set with migrated permissions (original inherited permissions are lost).
      Please consider the following behavior when using the Migrate Shared Drive membership permissions to document library permissions option.
      • When you use it by itself, all files and folders should “still” contain the three standard groups even when the file or folder inheritance is broken to add individual users to the folder or file.
      • When the library level inheritance is broken to add the members to the library, the three standard groups should still be included in the unique permissions on the library. In this case, the three standard groups would remain empty giving the SharePoint admin the option to add users to the three standard groups to grant access to all content, when desired.


    In case you use MigrateMembersToStandardGroups=1 AO, you will not be able to use the Migrate shared drive membership permissions to document library permissions option.

Verify Credentials

You may verify the credentials of the endpoint and any items in the MigrationWiz project without migrating data or consuming any licenses.

  1. Open the project containing the line items you wish to validate.
  2. Select the items you wish to validate.
  3. Click on the Start button in your dashboard.
  4. Select Verify Credentials from the drop-down list.
  5. Once complete, the results of the verification will be shown in the Status section.

Run Migration

To initiate the migration of document libraries:

  1. Open the project containing the items you wish to migrate.
  2. Select the line items to migrate.
  3. Click on the Start button in your dashboard.
  4. Select Full Migration from the drop-down list.
  5. Ensure that the Documents and Permissions checkboxes are selected.GSD_11.png
  6. Click Start Migration.
  7. Once complete, the results of the migration will be shown in the Status section.

Migrating Shortcuts

  1. To migrate shortcuts to the destination (as a .url file type), run another pass following the full migration steps above, this time with ‘Step 2’ selected.
  2. Step 2 should be run only after all relevant documents and permissions have been migrated.
  3. Please note Step 2 is not mandatory. This should be run only if you wish to migrate shortcuts to the destination (as .url file type).

Run Retry Errors

Look through the user list and click any red "failed migration" errors. Review the information and act accordingly. For more information review the Document Migrations article.

If problems persist contact Support.

Post-Migration Steps

Own Azure Storage

Delete all the Azure containers used for this migration, if any. This will prevent incurring post-migration Azure costs for these containers. Be careful only deleting the containers created for this migration.

Remove App Permissions

  1. Remove the newly created user.
  2. Remove the MigrationWiz Security Group.  

To remove the app from the source or destination, perform the following steps:

  1. Launch PowerShell.
  2. Connect PowerShell to Office 365.
  3. Enter the command: Connect-AzureAD
  4. Enter the admin credentials in the prompt.
  5. Enter the command: Get-AzureADServicePrincipal -SearchString Migration
  6. Look for the ObjectId of the app you want to remove and enter the following command: Remove-AzureADServicePrincipal -objectId <the object id> 

Known Behavior and Limitations

Shared Drive Memberships

Shared Drives will not be migrated if the source shared Drive doesn’t have at least one active member from the source tenant (either a direct user member or as part of a group).

Migration of Restricted Files

Google Shared Drive allows settings that can restrict downloading files for users with Viewer and Commenter permissions. For such files to be migrated, the shared drive must have an active member of the source tenant with permissions higher than Viewer/Commenter.

Format Conversions

Google proprietary format type file conversions are handled in the following ways:

  • Google documents will be converted into Microsoft Word (.docx) format.
  • Google spreadsheets will be converted into Microsoft Excel (.xlsx) format.
  • Google presentations will be converted to Microsoft PowerPoint (.pptx) format.
  • Google drawings are converted into .jpg format. However, those converted documents are not editable, once migrated.
  • Google forms are converted to .zip format (containing .html & .csv).
  • Google Jamboard will be converted to PDF format. However, those converted documents are not editable, once migrated.
  • Google Sites, Maps, and Apps Script are not migrated.

Google proprietary format files (e.g. Google Docs, Sheets, Slides) containing comments may, when converted to Office 365 format, display some additional wordings such as ‘Text Wrapping Break’.

Permission Mapping

Google Shared Drive (Source)

SharePoint Online Document Library (Destination)


Full Control

Content Manager










Commenter/Viewer with download disabled

Restricted View (Only for Documents)

Duplicate Folder Names

The RenameConflictingFiles=1 advanced option is not applicable for duplicate folder names. 

Use the RenameConflictingFolders=1 advanced option to enable the migration of folders with duplicated names from Google Drive as a Source into Microsoft destinations. With this AO, folders with duplicated names will be migrated with a suffix.

Multi-pass Behavior

During the first migration pass/run, a file and its associated versions will be migrated to the destination. In subsequent passes, the destination will be overwritten with the latest version only if the source file has a new version at the source.


If the source file content has not been modified in subsequent passes, files & versions will not be migrated, i.e. there will be no change at the destination.

Folders (new, renamed, or existing) will get migrated to the destination.

    • New folders, not previously exported, will be created at the destination on the subsequent pass.
    • Folders renamed at the source, after the initial migration pass, are treated as new folders and will be created at the destination on the subsequent pass. New files not migrated previously will also get migrated under this folder.

New files created at the source after an initial migration pass (i.e. files without watermarks) will get migrated to a destination under their current source folder on a subsequent pass.

Previously migrated files that are renamed (or any other changes in the file, like metadata) will not get migrated.

If the content of a file migrated by MigrationWiz in the initial pass is updated by users at the destination, then the subsequent migration pass will not overwrite this file even if the source file has a new version available.

MigrationWizId Columns at the Destination

As part of the migration, additional columns named MigrationWizId, MigrationWizIdPermissions, and MigrationWizIdVersion are created at the destination as part of the watermark for migrated data.

Similar watermarks will also be added for versions and be displayed as part of the version history.


  • If the source files have a version that is an empty file, then such versions are not migrated as they are ignored by migration API.
  • Folders and shortcuts in Google Shared Drives do not support versions.


  • Folder Shortcuts may not be migrated if the target folder name has been truncated using the advanced option ShrinkFoldersMaxLength
  • Shortcut files when migrated to the destination as .URL file, will not retain direct permissions applied to target files at the source.

Setting up destination endpoints with SharePoint site URL (on-need basis)

If you are migrating to document libraries under a single destination site, you may prefer to set up the endpoint URL in this format: 

When your destination endpoint is set up with a SharePoint site URL, the destination line item should only include the library name from the URL. Please note that the actual document library name may be different from the library name value in the URL. You must use the library name value from the URL as shown below.GSD_13.png



Was this article helpful?
0 out of 0 found this helpful