Google Sites Migration Guide

Follow the below steps for Google Sites to Microsoft 365 (SharePoint – Teams) 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 – Get Sites
      2. Specify Your Destination
      3. Global Settings
      4. Audit
      5. Pre-Processing
      6. Google Sites Migration
  1. Troubleshooting

1. Introduction

Google Sites migration projects are complex, customized projects. They cannot be performed on-demand in the self-service portal. These projects require Cloudiway product licenses combined with Consulting Services. The minimum timeline to start a Google Sites migration project is two weeks. Please contact your Sales Manager for more details.

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

Google Sites are migrated to SharePoint Modern Sites or to Microsoft Teams.

1.1. What is migrated

You will find the list of what can be migrated on the product page: Google Sites and SharePoint migration.

Regarding the limitations, you’ll find further information here, please don’t hesitate to contact us if you have any concerns.

Why File Licenses are needed for Google Sites Migration

1.2. Performance & Security

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

1.3. License Management

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

1.4. 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.5. 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 Google Workspace requires to set up OAuth authentications with appropriate permissions.

Please note: For both source and target, two-step authentication is not supported and will have to be bypassed before migration can start

  • Instructions to turn off 2-step authentication in Google Workspace here.
  • Deactivate MFA On Your Office 365 Migration Account here.

 

2.2. Mapping Table

In Microsoft SharePoint, 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.

2.3. Source Prerequisites

To perform the migration, you will need to create a Google Workspace migration account, and give it access to your Google Sites. If the migration account is tenant admin, by default, it will already have access to permissions.

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: Google Workpace Connector Configuration.

Cloudiway must whitelist your environment, it consists of manually login in a navigator from Cloudiway environment in order to authorize our IP addresses to access your Google Sites. You must contact Cloudiway at the beginning of your project to proceed to the whitelisting and, and may be necessary to perform it again during your project.

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 be configured with multi-factored authentication (MFA) and SSO (ADFS) turned off.

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

2.5. Web Part installation

As part of the solution, a custom Web Part has been developed to display the content of OneDrive folders within a SharePoint Sites.

Therefore, a OneDrive viewer Web Part provided by Cloudiway must be installed on the tenant before you start your migration.

Please refer to this article to install the Web Part.

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

4.1.1. Get Sites

New Google Sites are files stored in the personal Google Drive of the users. To build the list of sites, we need to connect to every user’s Drives and extract the sites. Cloudiway does it automatically, it’s the equivalent of the following command:

gam all users show filelist query “mimeType = ‘application/vnd.google-apps.site'”

Google Sites can reside in Users’ Google Drives, or in Shared Drives.
Cloudiway is able to pull the list of Sites that live in users’ Google Drives with no issues. However, in order to pull the Google New Sites that live inside a Shared Drive, Cloudiway needs to have access to the Shared Drive, by having the Cloudiway migration account (the account you provided in your source Google Connector) as a reader of the Shared Drives.

Therefore, in order to pull all the Google New Sites that are inside Shared Drives, the migration account needs to be a reader of all the Shared Drives you have in your Google Workspace.

Cloudiway provides a script that allows you to add your migration account as a reader of all Shared Drives in bulk, within a matter of seconds. Please download the script from here.

How to deploy the script:

  1. Log in to Google with a Super Admin account.
  2. Go to https://script.google.com
  3. Click on New Project

Google-Apps-Script-New-Project

This will open a text editor where you can input the Script provided by Cloudiway.

  1. Copy the script provided by Cloudiway and paste it into the text editor. You should overwrite the prewritten function provided by Google

Google-Apps-Script-New-Project-Title

  1. Click on the (+) sign next to Services and add the Drive API

Add-Drive-API

  1. Save and run your code. The first time you run your code, it will be a bit slow and it will ask you to give your consent to use the Google Drive APIs. You should click on Allow.

Google Authorization Required

Authorization Required Cloudiway

  1. Once your script runs, it will generate logs like the following:

Google-Apps-Script-New-Project-Logs

 

Step 1: Get Sites

From the Cloudiway Interface, use the Get Sites option to fill the list of Sites to migrate:

Get Sites

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

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

Step 2: Assign target

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.

 

4.1.2. Mass renaming (CSV Import)

If you wish to make modifications to the entire sites list, you can export the list, edit the CSV file and reimport it.

Learn more about the CSV format: How To Fill The Users/Groups CSV File?

Click on MANAGE, Import, select the CSV File, the Source and Target Connectors, then click Upload.

Import CSV

4.2. Specify Your Destination

You can migrate your Google Sites to 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.

Group PrefixAdd a Prefix to the Target?

You can add a Prefix to the Target Site Name and Target URL.

In the Site List, check one or multiple objects, go to MANAGE then click on the “Add Prefix” button.
Enter the Prefix in the pop-up then SAVE.

 

 

4.3. Global Settings

At this point, you are ready to migrate.

You can enable or disable the following points:

Gobal Settings Google Sites Migration

  • Migration of Permissions.
  • Migration of TermStore: TermStore is a SharePoint feature that doesn’t exist in Google. Therefore, it’s not used for Google Sites migration.
  • Migrate Version History: not used for Google Sites migration.
  • Migrate to: determine where files are migrated, we recommend to migrate to OneDrive. Files will be migrated to the OneDrive of the user and displayed in the SharePoint sites.
  • File Management: when you migrate to an existing destination, determine the behavior when files already exist on the target.

4.4. Audit

4.4.1. File audit

In order to be able to migrate the files embedded in Google Sites, all the user’s Drives need to be audited before the migration, this requires a Cloudiway File license for every user.

How to perform the File audit: Read more.

4.4.2. Site 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 Google Drive Documents
  • Etc.

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

Google Sites Migration Audit

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