Google Drive Migration Steps - For Non-Own Service Account Migrations

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.

The original Google Drive connector uses a BitTitan Google service account. Since the service account is shared, the likelihood of throttling is higher compared to the new connector. This option may be chosen if you do not wish to set up your own account. 

Most Google Drive migrations now use the Own Service Account option and the steps for that are included in our migration guides. However, some still prefer the original endpoint. If this is the case, follow the steps below for your Google Drive environment preparation in place of the steps to set up the Own Service Account.

The rest of the migration will follow the migration guide for your chosen migration. 

Source Setup

Use these steps if your source is Google Drive and you do not wish to use the Google Own Service Account option. The following steps increase your risk of throttling during the migration.

  1. Enable OAuthentication 2.0 within your Google admin portal to grant MigrationWiz access to G Suite. This step will require a Google admin account. For guidance, see Enable access to G Suite using OAuth 2.0.
    • If you are migrating from multiple domains, repeat the steps for each domain.
    • Make sure there are no spaces before or after the scope entry, as they will cause the authorization to fail.
    • OAuth administrative credentials will not function properly with G Suite for Business Legacy free accounts, G Suite Legacy free accounts, or Google Apps Legacy free accounts. Unfortunately, migrating any Google Legacy free accounts is not supported.
  2. Go to the G Suite admin page at admin.google.com click on Security > Advanced Settings > Manage API Client Access.
    OR
    If your account shows the latest UI updates from Google, Go to the G Suite admin page at admin.google.com click on Security > Advanced Settings > Under ‘Domain-wide delegation’, click Manage domain-wide delegation > On the Manage domain-wide delegation page, click Add new.

  3. Export mailboxes to CSV file(s). From Google Admin portal > Click Users > Click ⁝ (3 vertical dots) > Download Users > Download All Users > Click OK > Save.

Destination Setup

Use these steps if your destination is Google Drive and you do not wish to use the Google Own Service Account option. The following steps increase your risk of throttling during the migration.

  1. Grant MigrationWiz OAuth2.0 access to authenticate to Google Drive. This step will require a Google admin account. For guidance, see Enable access to G Suite using OAuth 2.0.
  2. Add users to Google Drive. Instructions are located here

Create Project

Use these steps if your source is Google Drive and you do not wish to use the Google Own Service Account option. The following steps increase your risk of throttling during the migration.

  1. Click the Go To My Projects
  2. Click the Create Project
  3. Click on the type of project that you wish to create. For this scenario, select Document projects are used to migrate document drives from one cloud storage to another. Document migrations will maintain the folder hierarchy from the source to the destination.
  4. Click Next Step.
  5. Enter a Project name and select a Customer.
    If you have not already added the customer into MSPComplete, you will need to click New to create the Customer. For steps on creating customers, see View, Add, and Edit Your Customers.
  6. Click Next Step.
  7. Select a Source Endpoint from the Endpoint dropdown menu or create a new endpoint. 
    1. Click Endpoints
    2. Add Endpoint
    3. Enter endpoint name
    4. For endpoint type, select Google Drive.
    5. Enter the Google admin account email address and domain name in the appropriate fields.
    6. Both the source and destination domains will need to be listed in the endpoint for the migration to be able to connect properly.
    7. Both the source and destination domains will need to be listed in the endpoint for the migration to be able to connect properly.
  8. Select a Destination Endpoint from the Endpoint dropdown menu or create a new one using the steps above. 
  9. Click Save and Go to Summary.
    If setting up a Tenant-to-Tenant Coexistence mailbox project, check the box for Enable Tenant to Tenant Coexistence. Otherwise, leave that box unchecked.
Was this article helpful?
0 out of 0 found this helpful