Google Sites Migration Guide

Follow the below steps for Google Sites to Office 365 (SharePoint) Migration. If you wish to use the new platform, please contact us.

Overview:

  1. Introduction
  2. Prerequisites
  3. Create Your Connectors
  4. Google Sites Migration Settings
    1. Site List
    2. Specify Your Destination
    3. Mapping Table
    4. Global Settings
    5. Audit
    6. Pre-Processing
    7. Google Sites Migration
  5. Troubleshooting

1. Introduction

Google Sites can be migrated as part of your entire migration plan or as an independent project, depending on your business needs. You can migrate your Google Sites to Microsoft SharePoint Sites.

Note: Cloudiway migrates only from Classic Google Sites (not New Google Sites).

1.1. Performance & Security

For more information about security, please refer to this article.

For more information about migration performance, please refer to this article.

1.2. License Management

Cloudiway platform automatically assigns the licenses, for more details regarding the license management, check out this page.

1.3. Delta Passes

Delta migration is a Cloudiway functionality that allows you to migrate incrementally. Changes are migrated during delta passes. Deletions are not propagated.

1.4. Support

Although we provide support for our own products, we do not provide support for third-party products such as PowerShell nor SharePoint administration.

If you are concerned you might have any difficulty completing these steps, please consider a solution with our consulting team, contact us. This will ensure a fast, cost-effective, and stress-free implementation.

2. Prerequisites

2.1. How it works

The product uses the Google Drive APIs and native https calls to read the source and a mix of Graph APIs and CSOM calls to push the data to the target.

Migration from G Suite requires to set up an OAuth authentication with appropriate permissions.

2.2. Mapping Table

In Google Sites, there are permissions and metadata (createdby, modifiedby, etc.) that contain email addresses. During the migration, these addresses must be converted into target accounts.

To achieve this, Cloudiway uses a mapping table to perform the conversion.

Important: the mapping table must be exhaustive, any missing email address will not be converted, and would end up with the loss of permissions and metadata.

Prepare your mapping table for users and groups/teams in CSV format, ready to upload later on.

2.3. Source Prerequisites

To perform the migration, you will need to create a G Suite migration account, and give it access to your Google Sites. Also, native Google Drive documents are accessed using Google Drive APIs. Therefore, you need to give permissions (Google feeds) to use these APIs.

Read more: G Suite Connector Configuration.

2.4. Target Prerequisites

We recommend creating an Office 365 account dedicated to the migration, that can be deleted once the migration is completed.

  • It must be SharePoint administrator.
  • It must not be configured with multi-factored authentication (MFA) or SSO (ADFS).
  • Legacy Authentication must be turned on.

Cloudiway automatically creates the Sharepoint site, therefore they don’t have to exist prior to the migration. If they already exist, it will be used and data appended to it.

2.5. Azure Active Directory Application

Graph APIs calls are performed through an Azure Active Directory Application which is granted specific permissions.

You can either create an Azure Active Directory Application manually or let the platform create one for you.

Please consult our How To Create Azure Apps Registration page to create the Azure Active Directory Application and associated permissions.

3. Create Your Connectors

For Cloudiway to migrate your Sites, it needs to be able to communicate with both your source and target domains. To do this, Cloudiway uses connectors. You will need to set up a connector for each source tenant and each target tenant. Please refer to this page to configure your connectors.

For large projects, it’s possible to create multiple connectors that will be used in parallel. Please contact Cloudiway consulting services if you need to set up such configuration.

4. Google Sites Migration Settings

Note: to test the migration, you can use a Trial License, please consult this article to assign a Trial License.

4.1. Site List

To perform the migration, navigate to Sites > Site List

Cloudiway Site List

Use the Get Sites option to fill the list of Sites to migrate:

Get Sites

This will connect to Google Sites and retrieve all available sites.

Select the connector you want to connect, click on GET.

Note: you can monitor the progress of this task in the Global Logs.

Once the list is retrieved, you need to assign a target connector to the entries.

Select the entries, click on MANAGE, then Assign Target.

Google Sites List Manage

Select the Office 365 connector, click on Assign.

Add a site manually

You can manually add the details of a site to your list on the Cloudiway platform.

Click on MANAGE > Create and enter the following details:

Google Sites Manage Create

4.2. Specify Your Destination

You can migrate your Google Sites to Classic or Modern SharePoint Sites.

Click on the item to edit the different fields (see picture above).

By default, the target Site prefix Address chosen by the platform is /sites, you can select /teams instead.

4.3. Mapping Table

Mapping Table

Click on Mapping Table.

You can upload a User or Group list via CSV (use IMPORT) or CREATE your entries manually.

A template of CSV file is available on the platform when you click on IMPORT.

FirstName;LastName;SourceEmail;TargetEmail;DisplayName;EntryType;

  • User example: test;user1;test@source.com;test@target.com;test user;0
  • Group example: ;;testgroupe@source.com;testgroup@target.com;testgroup;1

EntryType: enter 0 for user, 1 for group.

FirstName and LastName: Leave blank for group.

4.4. Global Settings

At this point, you are ready to migrate.

You can Enable or disable the Migration of Permissions:

Google Sites Migration Global Settings

Note: TermStore is a SharePoint feature that doesn’t exist in Google. Therefore, it’s not used for Google Sites migration.

4.5. Audit

The Audit feature allows you to collect various information about the sites:

  • Site Name
  • Site URL
  • Author
  • Last Modified Date
  • Number of Pages
  • Number of Web Pages
  • Number of File Cabinets
  • Number of List Pages
  • Number of Announcement Pages
  • Number of Attachments
  • Number of Google Drive Documents
  • Number of Gadgets
  • Etc.

To Audit a site, in Site List, select it and click on MIGRATIONAudit.

Google Sites Migration Audit

4.6. Pre-Processing

The pre-processing tool creates the SharePoint site at the target if necessary.

What does the pre-processing tool do in detail?

At the target:

  • It creates the SharePoint sites and libraries.
  • It uses the graph APIs (Client ID and Client Secret) and gives the owner role to the migration account defined in the target connector.
  • It migrates membership and ownership.

To pre-process a site, in Site List, select it and click on MIGRATIONPre-Processing.

The site is now ready to be migrated.

4.7. Google Sites Migration

Before starting the migration, you must run the pre-processing (see step above) of the site.

To start the migration, in Site List, select it and click on MIGRATIONStart.

This will schedule the migration. The migration will start as soon as there is a free spot on the platform.

You can monitor your migration by clicking on the entry in the Site List.

Microsoft Teams Migration Logs

5. Troubleshooting

Cloudiway provides an extensive knowledge base with many resources, including common error messages, video guides, and downloads.

Please visit the knowledgebase here: https://help.cloudiway.com/

 

Cloud Migration Cloudiway
Want to try?
BOOK A DEMO
Cloud Migration Questions
Any questions?
Contact