SharePoint Online to Google Drive Migration Guide

Introduction

This is the complete onboarding task flow for migrating documents from SharePoint to Google Drive. This is a many-to-one migration path. This means that data that belongs to many users will be migrated into a single account. This is a rare business case. 

Follow the steps below to prepare for your migration. Once you have completed these steps, you are ready to begin your migration.

To discover what items are moved with MigrationWiz in this scenario, and which items will not be moved, see Moved Items. Note that these items will vary by source and destination, so check the proper environment listings carefully.

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 we cannot handle scenarios such as conflict resolution without user interaction.

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

 

Prepare Source Environment

  1. Obtain account credentials of a SharePoint Online administrator or Site Collection administrator account to be used for migration, or use the global admin account for the tenant. More information on these can be found here.
  2. Obtain the site URL.
  3. Obtain a list of libraries that need to be migrated, and the corresponding Google Drive accounts to migrate them into.
  4. Set up the app-based authentication in the Office 365 tenant. For specific instructions, see Sharepoint App-based Authentication.

 

Prepare Destination 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. 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:mceclip0.png

    • 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:

    1. In the Client ID field, paste the Unique ID copied above.
    2. 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

    3. Click Authorize.

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

MigrationWiz Steps

Create New Project

Google Drive (Own Service Account) Endpoint

To create a new migration project:

    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 items that will be migrated to the project. How Do I Add Items to my Migration Project?
    • Click Add > Quick Add,
    • Under Source, enter the Source library name in the field provided.
      Notes:
      • This does not require the whole URL, just the name of the library. The name that needs to be entered under the library field for both Source and Destination will be the text that is at the end of the site URLs.
      • This field is case-sensitive.
      • This may be different than the actual name that has been set for the Document Library. The examples below help explain this:
        • 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.
    • Under Destination, enter the name of the Google Drive account to migrate this library into.
  2. Add folder filters to entries.
    Note: This step is optional, and only required if only certain directories under a library need to be migrated into Google Drive accounts. How do I filter a folder?
    • For example, to migrate a folder named directory1 and its subfolders, define the following folder filter: ^(?!directory1)
      Notes:
      • Steps to add this filter: click the pencil icon (edit icon) on the right-hand side of the user dashboard > Advanced Options > Filter Folders > enter the following filter inclusion: ^(?!directory1)
      • This will create the directory on the Destination Google Drive account and migrate the files into that directory.
      • To migrate them into the root directory, add a folder mapping. Can I add folder mapping in MigrationWiz?
  3. Set the Project Advanced Options.
    Note: This step is optional because there are no specific recommended advanced options for this scenario. Options & Advanced Options FAQ
    • 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.
  4. Run Verify Credentials. Options & Advanced Options FAQ
  5. Perform the migration. Steps for a Full Migration pass:
    • Select the items > From the top navigation, click the Start button > From the drop-down list, select Full Migration > Click the Start Migration button. How do I start a migration?
      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.
  6. Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. How do I start a migration?

 

Post-Migration Step

  • To prevent users from inadvertently using the Source SharePoint libraries, decommission the Source SharePoint server, libraries, or user accounts.
Was this article helpful?
0 out of 0 found this helpful