1. BitTitan Help Center
  2. Perform a Migration
  3. GCC High Migrations
  4. Google Workspace

Google Drive to SharePoint (GCC/China) Migration Guide

This article will guide you through the steps for migrating folders and documents from Google Drive to  Microsoft SharePoint using the GCC/China endpoint. 

This is a one-to-many migration path. This means that data that belongs to one user will be migrated into a shared document library. This is a rare business case because individual data would then be accessible by multiple people.

If you are performing a Google Drive to OneDrive for Business migration, refer to the Google Drive to OneDrive for Business Migration Guide. This is the most common migration scenario for Google Drive migrations. 

First time?

This migration guide contains the necessary steps to perform the actual migration, but there are many steps to preparing for migration. 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 scenario.

MigrationWiz

MigrationWiz is a migration tool, not a syncing tool. If changes are made at the source after migration, they will not sync to the destination, nor will changes made at the destination sync to the source. We do not have “live” monitoring of changes (as with a sync agent) and cannot handle scenarios such as conflict resolution without user interaction.

MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all Agents besides those who are Inactive can view all migrations projects. 

We are not able to support migrations with two-factor or multifactor authentication. 

Prerequisites

Licensing

We recommend that you purchase User Migration Bundle licenses for this migration scenario. User Migration Bundle licenses allow the performance of multiple migrations with a single license. For questions on licensing, visit MigrationWiz Licenses.

To use your license by following the next steps:

  1. Purchase Licenses.
  2. Create a Customer.
  3. Apply Licenses.
  4. Review Considerations.
Purchase Licenses Create a Customer Apply Licenses Considerations

Purchase licenses by following the steps below:

  1. Sign in to your BitTitan account. 
  2. In the top navigation bar, click Purchase.
  3. Click the Select button and choose User Migration Bundle licenses.
  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.

Limitations

  • MigrationWiz is a migration solution (not a synchronization solution) and will NOT propagate updates, deletes, or moves of the items previously migrated in the first migration pass because 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.
  • Items and folders in "Shared with Me" will not be migrated.  Only items in "My Drive" will be migrated. To migrate "Shared with Me" items, they must be added to "My Drive".
  • MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all Agents besides those who are Inactive can view all migrations projects. 
  • We are not able to support migrations with two-factor or multifactor authentication. 
  • The maximum file size for migration through MigrationWiz varies by migration type and environment, but may never exceed 60GB.
  • This migration scenario will only migrate the content from the users' Google Drive accounts into the SharePoint document library. It will not migrate the permissions in the Source Google Drive shared documents. Make sure to deselect Document Permissions before submitting your migration pass.
Which items are migrated?
  • Folders
  • Folders you have shared
  • Permissions
  • G Suite native files
  • Code Files
  • Documents
  • Images
  • Executables
  • Videos
  • Audio Files
  • Templates (files that the template had been applied to are migrated)
  • Creation Date (Creation date gets changed to the "date of migration" date)
  • Scripts/Macros (Scripts are not converted to macros when going to documents)
  • Document History
  • Comments
  • File/Folder permissions
  • Items/folders in "Shared with Me”. These folders must be added to the user’s “My Drive” and the advanced option “DocumentBrowsingMode=FullCopy” must be enabled.
  • Shortcuts (Migrated in Google Drive to Google Drive scenarios only.)
  • Migrations of over 15GB are now supported, but this must be set up in Advanced Options. These settings will prevent timeout errors when a Speedster import takes more than 10 minutes to complete.
    • Set LargeFileMigrations=1
    • Set LargeFileMigrationsTimeout=7200000
      • 720000 value is an example; time is measured in milliseconds
Which items are not migrated?
  • Google Shared Drives (also known as Team Drives) are not supported with this migration type. To migrate Shared Drives, see the migration guide for that scenario. 

    • This is largely because Shared Drives uses a different root folder than Google Drive does. Shared Drives also follow different organization, sharing, and ownership models, so the same methods used to migrate Google Drive will not work to migrate Shared Drives.

  • Personal Free Google Drive is not supported
  • File/folder shortcuts

Prepare the Source Environment

Google Drive (Own Service Account) Endpoint 

The Google Drive (Own Service Account) connector launched in 2020 and requires the set up of a Google Service account. This significantly reduces the likelihood of the migration being throttled. This is the option we recommend for all Google Drive migrations. Follow the steps below under under OAuth2 Requirements for Google Drive (Own Service Account) to set up your environment for this endpoint.

All accounts being migrated must be in Active status in the tenant. Users that are set to a status of Inactive will not be able to fully migrate and will fail in the project.

OAuth2 Requirements for Google Drive (Own Service Account)

Prerequisites

  • Subscription to Google Cloud Platform.
  • Google Super Administrator account.
  • Ability to set up a service account on the G Suite tenant.
  • A Google service account must be set up before the MigrationWiz project is created.

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 haven't 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.
  3. When the new project creation completes, at the top of the screen next to the current project name, click Down icon and select the newly created project name from the list.

If you are not able to create a project here, it may be that the ability to create projects has been disabled for your tenant. To check this, navigate to the Google Admin Center and click on Apps > Additional Google Services and select the Google Cloud Platform. Once there, you should see a setting that can be toggled in order to allow users to create projects.

Enable APIs for Service Account

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

Make sure that the respective services are enabled within the Google tenant. You can control services for your users using the instructions on this page: Control who can access G Suite and Google Services.

Create Customer Tenant Service Account

  1. From the Google Cloud Platform Console, click Menu > IAM & Admin > Service accounts.
  2. Click + Create Service Account at the top middle of the screen and enter a name.
  3. Click Create.
  4. Assign the role of Owner to the new Service Account by selecting Owner from the Role drop down menu.
  5. Click Continue to move to the next step, then click the Done 
  6. You will now be returned to the "Service Accounts" page. 
  7. On ‘Service accounts' page, click vertical ellipsis under 'Actions’ column for the service account created above.
  8. Click Create key.
    1. Make sure that JSON is selected as "Key Type."
  9. Click Create.
  10. Click Close.

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 migration endpoint in the migration project.

Important

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 endpoint creation will fail.

Setting the Scopes for the Migration

From the Google Cloud Platform Console:

  1. Click Menu.
  2. Click IAM & Admin.
  3. Click Service Accounts.
  4. Find the service account that was set up in Step 3: Create Customer Tenant Account.
  5. Find and copy the service accounts Unique 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 similar to Administrator account passwords and handled securely.
  6. Go to the G Suite admin page at google.com.
  7.  Click Security.
  8. Click Advanced Settings.
  9. Under ‘Domain-wide delegation’, click Manage domain-wide delegation.
  10. On the Manage domain-wide delegation page, click Add new.
  11. In the Client ID field, paste the Unique ID copied above.
  12. In the OAuth scopes (comma-delimited) field, paste all scopes listed below: For source endpoint
    https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/drive.readonly
  13. Click Authorize.

 You should now see your specific Unique ID and the associate scopes listed.

Export mailboxes to CSV file(s)

From the Google Admin portal:

  1. Click Users
  2. Click ⁝ (3 vertical dots) 
  3. Download Users
  4. Download All Users
  5. Click OK 
  6. Save

Prepare the Destination Environment

  1. Create a SharePoint administrator or Site Collection administrator account to be used for migration, or use the global admin account for the tenant. Read the Manage administrators for a site collection article from Microsoft for more information.
  2. Create a SharePoint site.

    Important

    Make a note of the site URL where the document libraries will be stored. This will be entered when creating your MSPComplete Destination endpoint. There is no need to create the Document Libraries at destination. After creating the sites and subsites, MigrationWiz will automatically create the document Libraries specified in your project.

  3. Refer to the Training: Introduction to document libraries video from Microsoft for more information.
  4. Set up the app-based authentication in the Office 365 tenant. For specific instructions, see Sharepoint App-based Authentication.

MigrationWiz Steps

Create a Document Migration project

  1. Click the Go to My Projects button.
  2. Click the Create Project button.
  3. Select Document Migration
  4. Click Next Step.
  5. Enter a Project name and select a Customer.
  6. Click Next Step.

Endpoints

Endpoints are created through MigrationWiz. If you select an existing endpoint from the dropdown, it will only show ten endpoints. If you have more than ten, you may need to search it.

Consider that endpoint search is case and character-specific. For example, Cust0mer will not show up if the search is customer. We recommend keeping a list of endpoints you have created and any unique spellings or capitalization you may have used.

You may either use existing endpoints or create new ones. 

Create your Endpoints

Please review the following tabs to create your destination and source endpoints.

Source Endpoint Destination Endpoint

Create your source endpoint by following the next steps:

  1. Click New.
  2. Enter endpoint name.
  3. For the endpoint type, select Google Drive
  4. Enter the Google admin account email address and domain name in the appropriate fields.
  5. Click Add. 
  6. Click Next Step.

Region of Destination Tenant

The Region of Destination Tenant feature optimizes the migration performance and speed by choosing the region closest to the destination tenant. MigrationWiz displays a dropdown that allows you to select the destination region when configuring your destination endpoint. 

Tip

You can find the region of your destination tenant directly in the Microsoft Entra admin center by going to Identity > Overview > Properties, and using the Country or region or the Data location.

Country or region.png

For more information on this topic, review this article. In case you need the multi-geo information you can refer to this article.

Warning

If you do not complete this field you will not be able to save your project and the “This field cannot be left blank.” error will appear.

Add Users

Add the accounts (also referred to as "items") that will be migrated to the project. There are several ways to do this. 

Quick Add
This option allows you to add items one at a time. To do so, you only have to provide an email address if you entered administrative credentials when setting up the project. If you did not, enter the following user information:
  • An email address
  • Login name
  • Password
  • Mailbox status
Bulk Add

Bulk Add uses a CSV containing the source and destination email addresses for the users to add the users to the project. If migrating only a specific group from a tenant, we recommend using the Bulk Add option.

MigrationWiz allows you to bulk import mailboxes into the system.

To import one or more mailboxes:

  1. Sign in to your MigrationWiz account.
  2. Select the Project for which you want to perform the bulk import.
  3. Click Add.
  4. Click Bulk Add.
  5. Follow the instructions on the page.
Autodiscover

Autodiscover process within MigrationWiz can be used to discover items from the Source environment so that they can be imported into your projects. This can then be edited in the project to remove users not being migrated. All users are added with the source and destination email addresses set to match the source email.

This can be changed by using the Change Domain Name button at the top of the project page. If the usernames are changing during the migration, we recommend using the Bulk Add option.

There are few requirements in order for this to work:

  • The Source has to be Exchange 2007 or later, or Office 365, or G Suite. If you are using Autodiscover from G Suite, all G Suite domains must be added to the list of domains in the Endpoint.
  • The endpoint on the Source needs to use admin credentials.
  • The endpoint Administrator account on the source needs to be assigned the appropriate GSuite license in order for MigrationWiz to access Google Drive or Google Shared Drives for the Auto Discovery process.
  • For mailbox migration projects, the admin account that is specified within the Source endpoint needs to have a mailbox associated with it.
  • The admin mailbox must be listed in the public Global Address List (GAL).
  • The migration project type needs to be a Mailbox migration. For the exact steps to be followed during your migration, refer to the relevant Migration Guide. All Migration Guides can be found on the Help Center site.

One additional item to note here is that there is not a way to restrict the IP addresses that the connection will come from.  This means that the steps outlined in our IP Lockdown guide will not apply here.  If your environment requires that any IP addresses be whitelisted, it is recommended that items be added to your project using on of the other available options.

Autodiscover of items will not work while using Modern Authentication.

Autodiscovery exposes the following items:

  • For mailbox migration, autodiscovery will list all mailboxes at the Source.

Steps to Run Autodiscover

  1. Navigate to the project you want to import users into.

  2. Ensure that you have created an endpoint for the source project.

  3. Once in the project, on the top navigation bar, click on the Add drop-down, then select Autodiscover Items. This will begin the Autodiscover process.

  4. Once discovered, click on the Import button, to import the items into your MigrationWiz project.

Click Add and enter the email address of each Google Drive user for Source, and the corresponding document library name at the Destination that the Source documents will be migrated into.

If the document library is named "Documents" and the URL is listed as "xxxxxx.sharepoint.com/Documents/", enter Documents as the document library name.

If your document library is named "Documents" but the URL says "xxxxxx.sharepoint.com/Shared Documents/", the name of the document library that needs to be entered is Shared Documents.

Important

‘/' characters are not supported in the destination library name. Attempting to migrate any destination library with a '/' character will result in a migration failure.

Add Advanced Options

Under Support/Support options:

    • InitializationTimeout=8 - This increases the initialization timeout window to eight hours. Read the Cannot get folders from My Drive article for more information.
    • RenameConflictingFiles=1 - This automatically renames the files that have the same name. It will rename the files to their original file names, followed by a unique identifier hash so it does not interfere with the original name and search. Read the How do I migrate multiple files with the same name into OneDrive? article for more information.

    • DocumentBrowsingMode=FullCopy (Remove DocumentBrowsingMode=Moderate if there)- This option migrates all folders and files regardless of ownership. For more details, see the Google Drive Migrations FAQ article.

There are no spaces on either side of the "=" sign, and the entries are case-sensitive, so pay special attention to the capital letters in the commands above.

Run Verify Credentials

  1. Open the Project containing items you wish to validate​.
  2. Select the items you wish to validate.
  3. Click the Start button in your dashboard.
  4. Select Verify Credentials from the drop-down list.

Once complete, the results of the verification will be shown in the Status section.​ 

Notify Users

Notify users that a migration is occurring. Send email to all users telling them the time and date of the migration. During this time, they should not modify any documents in their Google Drive accounts, because any modifications will not be included in the migration.

Full (Delta) pass

Important

Deselect permissions before migrating. If permissions are left checked, this will result in errors during your migration, because permissions cannot be migrated for this scenario.

  1. Select the users.
  2. Click the Start button from the top.
  3. Select Full Migration.
  4. Click Start Migration.

Run Retry Errors

Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.

If problems persist, contact Support.

Request Statistics

Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics.

Post-Migration Step

To prevent users from inadvertently logging in and using their Google Drive accounts, decommission the Google Drive user accounts, or change their passwords.

 

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

Articles in this section