SharePoint Online to Google Drive Migration Guide

Introduction

This is the complete onboarding task flow for migrating documents from SharePoint to Google Drive. This migration type is known as "many to one", which means that data belonging to many users is being migrated into a single account. This migration type does not require licenses. 

First migration?

We’ve created a guide on scoping, planning, and managing the migration process for your use. If this is your first migration, we recommend reading this guide carefully.

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

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

Prepare Source SharePoint Online 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 Google Drive 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.
      • 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 admin.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 admin.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

    Step 5:

    Once these steps are complete, return to MigrationWiz for the following steps: 

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

    MSPComplete Steps

    Create Customer

    1. Click the Add button in the top navigation bar
    2. Click the Add Customer button on the All Customers page
    3. In the left navigation pane, select the appropriate workgroup and then click All Customers.
    4. Click Add Customer.
    5. Enter the new customer’s information in the Add Customer form. Primary Email Domain and Company Name are required. The rest are optional.
    6. Click Save.
    7. Repeat steps 1 through 4 for each customer you want to add. 

    MigrationWiz Steps

    Create a Document Project

    Document migrations will maintain the folder hierarchy from the source to the destination.

    1. Log in to MigrationWiz.
    2. Click the Go to My Projects button.
    3. Click the Create Project button.
    4. Select the Document project type. 
    5. Click Next Step.
    6. Enter a Project name and select a Customer.
    7. Click Next Step.
    8. Select endpoints or follow the steps below to create new endpoints. 

    Endpoints

    Endpoints are now created through MigrationWiz, rather than through MSPComplete. The steps for this section outline how to create the endpoints in MigrationWiz.

    If you are selecting an existing endpoint, keep in mind that only ten endpoints will show in the drop-down. If you have more than ten, you may need to search. 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, along with any unique spellings or capitalization you may have used.

    You may either use existing endpoints, or create new ones.

    To create a new source endpoint:

    1. Click Endpoints
    2. Click Add Endpoint
    3. Select SharePoint.
    4. Enter the URL for the top-level SharePoint document library, i.e., the site URL.  
    5. Enter the administrator username and password in the fields. This must be either a Global administrator, SharePoint Online administrator, or a Site Collection administrator account.
    6. Click Add Endpoint. 

    To create a new destination endpoint:

    1. Click Endpoints
    2. Click Add Endpoint
    3. Select Google Drive (Own Service Account)
    4. Click Select File

    5. Navigate to and select the JSON file that contains the Google Service Account key that was saved during the service account setup process.

    6. Enter the Google admin account email address and domain name in the appropriate fields. Please note that this admin email should match the end user domain.

    7. Click Add Endpoint.

    Add Users

    For this migration, we suggest using the Quick Add option. 

    1. Click 
    2. Click Quick Add.
    3. Under Source, enter the source library name in the field provided. 
      1. 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.
      2. This field is case-sensitive.
      3. This may be different than the actual name that has been set for the Document Library. The examples below help explain this:
      4. If the document library is named "Documents" and the URL is listed as "xxxxxx.sharepoint.com/Documents/", enter Documents as the document library name.
      5. 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.
    4. Under Destination, enter the name of the Google Drive account to migrate this library into.

    Advanced and Support Options

    There are no specific recommended advanced options for this migration scenario. However, if you wish to apply folder mapping or filters, follow the steps below. This step is optional, and only required if only certain directories under a library need to be migrated into Google Drive accounts.

    Filtering

    1. Click on the Advanced Options button.
    2. Under Filtering, specify a filter.
    3. Click Save.

    To migrate them into the root directory, add a folder mapping, as outlined below.

    For example, to migrate a folder named directory1 and its subfolders, define the following folder filter: ^(?!directory1). This will create the directory on the Destination Google Drive account and migrate the files into that directory.

    Folder Mapping

    1. In the Support Option section, add this support option:
      FolderMapping="^SourceFolder->DestinationFolder"
      Replace "SourceFolder" and "DestinationFolder" with the names of the folders in the Source and Destination environments.
    2. Click the "+" sign to add the folder mapping.
    3. Click Save.

    Long-term projects

    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.

    Run the Migration

    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.

    Full pass

    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

    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