Skip Ribbon Commands
Skip to main content

Google Drive to Google Drive Migration Guide

Last Update: 7/21/2017 11:32 AM
This article has been moved to our new Help Center. Please update your bookmarks.
​​​​​​​​​Google Drive to Google Drive Migration Guide


Important: When you sign in to MigrationWiz, you are redirected to the Getting Started page in MSPComplete. To go to a migration project created before April 4, 2017, click the Go to Projects button on the Getting Started Page. To create a new project for the migration scenario documented in this article, go to the Delivery Center and add a Docs: Google Drive to Google Drive​​ service to the customer. Read the Delivery Center article for more information about adding services to a customer.


  • This is the complete onboarding task flow for migrating folders and documents from Google Drive to Google Drive.
  • Complete each step in order. Links to corresponding Knowledge Base articles are provided.
  • The Source and Destination must both be paid versions of Google Drive. Free Google Drive accounts are not supported.
  • This migration scenario could occur during a company acquisition, where the acquiring company and the company that is being acquired are both using Google Drive.

Prepare the Source Environment

  1. Enable OAuthentication 2.0 within your Google admin portal to grant MigrationWiz access to G Suite. KB005019
    • Notes:

      • If you are migrating from multiple domains, repeat these steps for each domain.

      • Under Authorized API clients > Client Name > Enter:

      • Under One or more API Scopes > enter the scope for G Suite as Source (read-only scopes):,,,,,,,


      • OAuth administrative credentials will not function properly with G Suite for Business Legacy free accounts. If a G Suite tenant is a G Suite for Business Legacy free account, end user credentials must be used. Refer to KB005124 for more information on migrating with end user credentials.

      • Make sure there are no spaces before or after the scope entry. This will cause the authorization to fail.

  2. Enable API Access. Log in to Google Admin portal > Security > API Reference > checkmark the Enable API Access button. Note: This extra step is mandatory when migrating from Google Drive.
  3. Export mailboxes to CSV file(s). From Google Admin portal > Click Users > Click on ⁝ (3 vertical dots) > Download Users > Download All Users > Click OK > Save.

Prepare the Destination Environment (Google Drive)

  1. Grant MigrationWiz OAuth2.0 access to authenticate to Google Drive. KB005019
    1. Note: G Suite as the Destination (full scopes):,,,,,,
  2. Add users to Google Drive. Instructions are located here.

MSPComplete Steps

  1. Create the customer. KB005421
  2. Create the Source and Destination endpoints. KB005427
    • For the Source endpoint:
      • Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select Google Drive.
      • Enter the Google admin account email address and domain name in the appropriate fields.
    • For the Destination endpoint:
      • Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select Google Drive.
      • Enter the Google admin account email address and domain name in the appropriate fields.

MigrationWiz Steps

  1. Create the Document Migration project. KB005070
    • Create the Document Migration project > Select the customer > Select the Source endpoint (Source Google Drive) > Select the Destination endpoint (Destination Google Drive).
  2. Add the accounts (also referred to as "items") that will be migrated to the project. Note: If using the Bulk Add option, only the Source and Destination columns need to be filled in. You can use the CSV file that was created under Step 3 of the Prepare the Source Environment section of this guide. KB004842
  3. Run an assessment to calculate the number of licenses required for your migration. KB005237
  4. Set the Project Advanced Options. KB004834
    • Set the value for maximum licenses to consume per item, per pass. The default value is one license per user, which allows up to 10GB to be migrated per user. However, if a user has 28GB of data, the migration will pause at 10GB, and you will have to assign more licenses to the user. The recommended maximum number of licenses to consume per user for a document migration project is five (5) licenses per user, which allows up to 50GB of data to be migrated per user. The project will only consume the number of licenses for the amount of data migrated. If a user has 28GB of data, then only three out of the five licenses will be consumed, and two licenses will remain. KB004890
    • Under Support/Support Options add:
      • InitializationTimeout=28800000 - This increases the initialization timeout window to eight hours. KB005099
      • FolderLimit=20000 - This increases the maximum number of folders for the migration to 20,000. Large companies might have more than 10,000 folders (the default) to migrate, so we recommend increasing the folder limit to 20,000. KB005557
      • Note: 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 detailed above.
    • Set the Advanced Option to send a notification to end users after the migration pass completes.
      • Notifications > Send successful migration and notification to: > Source email address (if users are still using the acquired company's G Suite Gmail) or Destination email address (if users have already been migrated to the acquiring company's G Suite Gmail).
      • Customize notification email. Checkmark the Customize "successful migration" email box. Add your own customization text and company name to this email.
      • Note: Notifications should only be set up before the final pass. If performing a single, Full pass, set this up now. If you are following a Pre-Stage migration strategy, only set this up prior to the final Full (Delta) pass.
  5. Run Verify Credentials. KB004511
  6. Purchase Document Migration licenses. KB004647
  7. 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 Source Google Drive accounts, because any modifications will not be included in the migration.
  8. Perform the migration using one of the following strategies:
    • For small- to medium-sized migration projects that have less than 500 users, we recommend a Big Bang Migration strategy. This is a single, full-pass migration.
      • Steps for a Full Migration pass:
        • Select the users > From the top navigation, click on the Start button > From the drop-down list, select Full Migration > Click on the Start Migration button. KB004938
    • For large migration projects that have more than 500 users, we recommend a Pre-Stage Migration strategy. This is a multiple-pass migration.
      • Steps for a Pre-Stage Migration:
        • Pre-Stage pass: Select the users > Click on the Start button from the top, and select Pre-Stage Migration > Under the Migration Scheduling section, from the drop-down list, select 90 days ago > Click on Start Migration. KB004938
        • Full (Delta) pass: Select the users > Click on the Start button from the top, select Full Migration > Click on Start Migration. KB004938
  9. Click on the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. KB004626

Post-Migration Steps

  1. To prevent users from inadvertently logging in and using their Google Drive accounts on the acquired company's G Suite platform, decommission the Google Drive user accounts, or change their passwords.
  2. Notify users once the migration has completed. Note: If you set the MigrationWiz Advanced Option for Notifications, they will receive an email upon migration completion.