Skip Ribbon Commands
Skip to main content

Google Sites to SharePoint Online Migration Guide

Last Update: 3/2/2017 10:50 AM

​​​​​​​​​​​​​​​​​​​Google Sites to SharePoint Online Migration Guide

   Introduction

  • This is the complete onboarding task flow for migrating folders and documents from Google Sites to Microsoft SharePoint Online.
  • Complete each step in order. Links to corresponding Knowledge Base articles are provided.
  • Only files on Google Sites that are of the "File cabinet" page type can be migrated.
  • The migration includes both documents and document permissions.
  • Licenses for this migration scenario are included in the "Google Migration Bundle" SKU. This can be found on the Purchasing page of MSPComplete, under "Collaboration Migration", "Mailbox Migration" and "Document Migration". Since the SKU includes Google Sites, you should purchase licenses based on the number of Google user accounts to be migrated; this will provide enough licenses for all of the Google Sites to be migrated. Each license for Google site migrations will allow up to 10GB of data to be migrated.

Prepare the Source Environment

  1. Enable OAuthentication 2.0 on your Google admin portal, to grant MigrationWiz access to Google Apps. KB005019
    • Notes:

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

      • Under Authorized API clients > Client Name > Enter: 794841909041-4ujv1ss1o7m7kqm3gtqd06bklietmmde.apps.googleusercontent.com

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

        https://mail.google.com/, https://www.google.com/m8/feeds, https://www.googleapis.com/auth/contacts.readonly, https://www.googleapis.com/auth/calendar.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/drive, https://sites.google.com/feeds/

        Important:  When following the instructions in KB005019, where you are directed to insert the API scopes that are listed in the Knowledge Base article, you must also include one additional scope not listed in the article: https://sites.google.com/feeds/. This is included as the last entry in the scopes above. 

      • OAuth administrative credentials will not function properly with Google Apps for Business Legacy free accounts. If a Google Apps tenant is a Google Apps 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 the Google Admin portal > Security > API Reference > checkmark the Enable API Access button.

Prepare the Destination Environment

  1. Create 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. Create SharePoint site. Note: Make a note of the site URL where the document libraries will be stored. This will be entered when creating your MSPComplete Destination endpoint.
  3. Before beginning the migration project, create the structure of the document libraries, and also create the actual document libraries on the Destination SharePoint Online site. Note: Refer to this Microsoft training video for more information on the steps: Create your document library.

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 Sites.
      • Enter the URL for the Google Site.
      • Enter the administrator email address.
      • Enter the domain name.

Important: The administrator account that is entered must be a site owner. Steps: More actions > Site permissions > Add account as owner. They will then be sent an email invitation to the site. If they don't have a Google account, they must create one and verify it before trying to sign in to the site.

    • For the Destination endpoint:
      • Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select SharePoint.
        • Enter the URL for the top-level SharePoint document library,
        • Enter the administrator username and password in the fields. Note: This must be either a Global administrator, SharePoint Online administrator, or a Site Collection administrator account.

MigrationWiz Steps

  1. Create the Collaboration Migration project. KB005070
    • Create the Collaboration Migration project > Select the customer > Select Source endpoint > Select Destination endpoint > Click on the Save button.
  2. Add the accounts (items) that will be migrated to the project. KB004842​​
    • Click Add and enter the library name for the Source Google Site, and the corresponding document library name at the Destination that the Source documents will be migrated into. Repeat these steps to add an extra item for each additional Google site library that you want to migrate.
      • Note: The name that needs to be entered under Destination in MigrationWiz will be the text that is at the end of the site URL. 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.
  3. 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 item, which allows up to 10GB to be migrated per item. However, if a user has 28GB of data, the migration will pause at 10GB and you will have to assign more licenses to the item. The recommended maximum licenses to consume per item for a document migration project is five (5) licenses per user, which allows up to 50GB of data to be migrated per item. The project will only consume the number of licenses for the amount of data migrated. If an item 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
      •  RenameConflictingFiles=1 ​​- This automatically rename the files that have the same name. This will rename the files to their original file names, followed by an unique identifier hash so it does not interfere with the original name and search. KB005006.
      • 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 above.
  4. Run Verify Credentials. KB004511
  5. Perform the 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
  6. Click on the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. KB004626

Post-Migration Step

To prevent users from inadvertently accessing the Source Google Site, decommission the Google Site.