Introduction

This is the complete onboarding task flow for migrating folders and documents from Google Drive to Google Drive. Complete each step in the order listed. 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. The Source and Destination absolutely require a Google administrative account.

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

To see what items are included in the migration, see What items are migrated with MigrationWiz? and What items are not migrated with MigrationWiz?

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.

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. For more information, visit Project Sharing in MigrationWiz.

Prepare the Source Environment

Google Drive (Own Service Account) Endpoint 

This endpoint requires your tenant service account to be set up and Google APIs be enabled. Follow the steps below to set up your environment for this endpoint. 

Prerequisites:

• Subscription to Google Cloud Platform.

• Google Super Administrator account.

• Ability to set up a service account on the G Suite tenant.

• Service account must be set up before the MigrationWiz project is created.

 Step 1: 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.

 Step 2: 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.

 Step 3: Create Customer Tenant Service Account

1. From the Google Cloud Platform Console, click Menu > IAM & Admin > Service accounts.

2. Click Create Service Account 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 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 + Add Key.

9. Click Create New Key.

10. Make sure that JSON is selected as "Key Type."

11. Click Create.

12. Click Close.
    Notes:

    • 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 migration endpoint in the Mailbox 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 endpoint creation will fail.

Step 4: Setting the Scopes for the Migration

From the Google Cloud Platform Console:

1. 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 the Unique ID field for that service account by clicking the Column Display Options button in the right upper corner above Actions and copy the ID number. This is the Client ID number that will be used in a later step.
      Note:
      • 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. You will now have one of two options, depending on if the Google UI has been updated in your tenant.

   Old Google Tenant:

   • Go to the G Suite admin page at google.com
   • Click on Security
   • Click on Advanced Settings
   • Click Manage API Client Access.

   OR If your account shows the latest UI updates from Google, as shown below:

   • Go to the G Suite admin page at google.com
   • Click on Security
   • Click Advanced Settings
   • Under ‘Domain-wide delegation’, click Manage domain-wide delegation
   • On the Manage domain-wide delegation page, click Add new

    Once these steps are complete:

   5. In the Client ID field, paste the Unique ID copied above.
   6. In the OAuth scopes (comma-delimited) field, paste all scopes listed below:
      1. 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
         OR
      2. For destination endpoint (must include read-write scopes):
         https://www.googleapis.com/auth/admin.directory.group, https://www.googleapis.com/auth/admin.directory.user, 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,
         https://www.googleapis.com/auth/drive
   7. Click Authorize.

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

Prepare the Destination Environment

Google Drive (Own Service Account) Endpoint 

Follow the steps in this section under Prepare Source Environment.

MigrationWiz Steps

Create New Project

Google Drive (Own Service Account) Endpoint

To create a new migration project:

1. 1. Click the Go To My Projects button.
   2. Click the Create Project button.
   3. Click on the type of project that you wish to create. For this scenario, select Document. 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.
   1. Click Next Step.
   2. Enter a Project name and select a Customer.
      Note: 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.
   3. Click Next Step.
   4. Select a Source Endpoint from the Endpoint dropdown menu or create a new endpoint. 
      Notes:

      • Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select Google Drive (Own Service Account).

      • Click Select File > Navigate to and select the JSON file that contains the Google Service Account key that was saved during the service account setup process.

      • Enter the Google admin account email address. Please note that this admin email should match the end user domain.

   5. Select a Destination Endpoint from the Endpoint dropdown menu or create a new one using the steps above. 
   6. Click Save and Go to Summary.
      Note: If setting up a Tenant to Tenant Coexistence mailbox project, check the box for Enable Tenant to Tenant Coexistence. Otherwise, leave that box unchecked.

Once the project is created:

1. 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
2. Set the Project Advanced Options. KB004834
   • InitializationTimeout=8 - This increases the initialization timeout window to eight hours. KB005099
   • DocumentBrowsingMode=FullCopy. This option migrates all accessible content for a user along with associated permissions. Important: if a file owned by a user is located under a folder not owned by the same user, a redundant link will be generated for the file at the destination after the migration. 
     To remove these redundant links, run another pass of full migration using support advanced option RemoveRootParentLinkForGDrive=1
   • ShouldConvertToDestinationFormat=1 This command will keep migrated items in Google Format. For more information see How are format conversions handled from Google Drive to Microsoft OneDrive? And vice versa? 
   • If the migration project is a long-term project, it may be necessary to add an additional Advanced Option for use during the final migration pass to verify the contents of previously migrated items. For more information, contact Support.
     
     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.
3. 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. Check 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.
4. Run Verify Credentials. KB004511
5. Run an assessment to calculate the number of licenses required for your migration. KB005237
6. 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.
7. Perform the migration, using one of the following strategies:
   • Full Migration strategy. For more information, see How do I start a migration?
     • For small migration projects that are less than 50 users, we recommend a Full Migration strategy. This is a single, full-pass migration.
   • Pre-Stage Migration Strategy:
     • Pre-Stage pass. For more information, see How do I start a migration?
     • Full (Delta) pass. For more information, see How do I start a migration?
     • For large migration projects that are more than 50 users, we recommend Pre-Stage Migration strategy. This is a multiple-pass migration.
8. Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. KB004626

Migrating Shortcuts

Shortcuts are a new type of file introduced in Google Drive. A shortcut is a link referencing another file or folder. When you open a shortcut, you are accessing (opening) the file referenced by the shortcut. Downloading a shortcut will download the file the shortcut points to. Shortcut titles are visible to everyone with access to the folder or drive the shortcut is in; however, they may only open it if they have permissions to the original file.

Migrating shortcuts is not required. If you do not wish to migrate shortcuts in your Google Drive to Google Drive migration, simply skip this section. This migration type is only available for Google Drive to Google Drive migrations and will not function in any other scenario. 

Step 1 : Migrate documents & Permissions

Shortcuts cannot be migrated until the target documents & permissions referenced by the shortcuts are available at the destination. Hence, all relevant documents and permissions must be migrated before attempting to migrate shortcuts. Complete Step 1 of your migration, as displayed below (and explained above in the guide) with the shortcut option unchecked.

Step 2: Migrate Shortcuts

1. After all relevant documents and permissions have been migrated, you will run another migration pass. Click Step 2 under Start Full Migration. 

2. When Step 2 is selected, only Shortcut files will be migrated.

After successful completion of this migration run, shortcut files will be available at the destination for the relevant documents .

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.