GOOGLE SITES MIGRATION GUIDE

1. Google Site Migration Overview

2. Google Sites Migration Prerequisites

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

2.4.1 Create a target Office 365 service account

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.2. Target 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 how to create the Azure Active Directory Application and associated permissions.

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

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 can reside in Users’ Google Drives, or in Shared Drives:

  • in order to pull all the Google New Sites that are inside the Users’ Google Drives, 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’”

  • However, in order to pull the Google New Sites that live inside a Shared Drive, Cloudiway needs to have access to every Shared Drives, by making the Cloudiway migration account (the account you provided in your source Google Connector) a reader of the Shared Drives. Cloudiway can help you add the migration account as Reader of all Shared Drives. Please contact our services team to get assistance in this matter.

Step 1: Get Sites

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

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

Cloudiway Site 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 MANAGEImport, select the CSV File, the Source and Target Connectors, then click Upload.

Cloud Import

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.

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

Cloudiway Site Global Settings
  • 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. Perform an Audit

4.4.1. File audit

In order to be able to migrate the files embedded in Google Sites, all the user’s Drives and all Google Shared Drives need to be audited before the migration, this requires a Cloudiway File license for every drive. The audit consumes the Cloudiway file license. (The reason is that the audit task may be long for large drives and will consume a lot of resources charged to Cloudiway by Azure).

4.4.2. Site audit (optional)

The audit is optional and purely informative. It consumes the Cloudiway license. You do not have to run it, unless you wish to see how many files and folders you have in the source site.

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.

Cloudiway Site Manage -Audit
4.5. Perform 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. Activate and monitor your 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.

Cloudiway Teams Migration Logs