This article will guide you through the site page migration from Google Sites to Microsoft 365 SharePoint Sites.

You need to set up a Document Project and use the Shared Documents license to migrate the site structure and embedded documents from Google Sites to your desired Microsoft 365 SharePoint Site. Only the Shared Document 50GB or Shared Document 100GB can be utilized for this migration project.

MigrationWiz

MigrationWiz is a migration tool, not a syncing tool. If changes are made at the source after migration, they do not sync to the destination, nor do the 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 does not support auto-provisioning of SharePoint Site at the destination for this migration type. The destination SharePoint site must pre-exist.

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

The maximum file size for migration through MigrationWiz varies by migration type and environment but may never exceed 60GB.

Prerequisites

It is important to highlight the following prerequisites for a smooth migration project.

• The Google Site needs to be configured with the Public setting.
• The Google Site pages must be in the new Google Site format. Classic Google Site is not supported.
• The account used for the source endpoint must have super admin privileges and must be the owner of the source Google Site to perform the migration.

Licensing

The Google Sites to Microsoft 365 SharePoint Site migration is supported by the Shared Document License type.

• Both licenses Shared Document 50GB or Shared Document 100GB can be utilized.
• Each license allows up to the maximum quantity of data it permits to be migrated per Site.
• If more than 100GB of data per Site is being migrated, purchase enough licenses to cover the total data being migrated. For example, if you have six Sites and two have 200GB of embedded data you must purchase eight licenses. 

Limitations

The following are some limitations for Google Sites to Microsoft 365 SharePoint Site migrations. Some of them are an inheritance from the APIs used as well as the capabilities of the current destination.

• MigrationWiz only supports migrations to the SharePoint Team Site and Communication Site.
• Permissions are not migrated by default when the site is created.
• Files migrated from Google Shared Drive and Google Drive to SharePoint or OneDrive Sites, will not be linked to the original files.

• MigrationWiz can only migrate a Google Site with a Public setting. It cannot migrate a Google Site with a Private setting.

• Google Sites font type and size are not migrated to the Destination due to formatting in the SharePoint Site.

• As SharePoint Sites do not support collapsible content, the collapsible content in Google Sites is migrated over as plain text.

• As SharePoint Sites do not support embedded HTML webpages, the layout and content from Google Sites may be distorted.

• Google Sites supports an unlimited depth of menu layers, while SharePoint only supports a menu depth of two layers. As such, menus in the third layer onwards are migrated to the same hierarchy as the second menu layer.

• Google Sites supports up to four columns in a section, while SharePoint Sites only supports three columns in a section. As such, the fourth column is migrated as the first column in a new section below.

• MigrationWiz migrates the Google Site in plain text format. No other format is supported for export.
• Some errors may appear during the migration process, please see the list below:
  
  • “Error while creating image", this error usually indicates there was an issue while creating an image at the destination. Please ignore this error since testing indicates that the migration of all image files has been completed successfully without any issues when this error message appears.
  • "Your migration failed while checking destination credentials. Please verify the MigrationWIZ Full Control App or Delegate App is available at Azure portal", this is a false error. When an incorrect username or password is provided, the system prompts the message above. The appropriate message should be “Your migration failed while checking source or destination credentials. The administrator username or password seems to be invalid”.

Migrated Items

In the following sections, you can find all the migrated items in a Google Sites to SharePoint Sites migration besides the mapping migration.

Prepare the Source Environment

Google Sites Endpoint

This endpoint requires your tenant service account to be set up and Google APIs to be enabled. 

Prerequisites

• Subscription to Google Cloud Platform.
• Google Super Administrator account.
• Ability to set up a service account on the G Suite tenant.
• The service account must be set up before the MigrationWiz project is created.
• The Administrator has Google Drive access privileges.

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

Enable APIs for Service Account

1. Access the Google Cloud Platform Console and click Menu () > APIs & Services > Library.
2. Enable the following APIs by selecting the specific API and clicking Enable. Repeat for each API:
   • Google Drive API
   • Google Calendar API
   • Admin SDK API
3. Confirm that the respective services are enabled within the Google tenant.

You can control services for your users by following the instructions on this page: G Suite and Google Services Access.

Create a Customer Tenant Service Account

1. Click Menu > IAM & Admin > Service accounts, from the Google Cloud Platform Console. 
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. On the ‘Service accounts' page, click the vertical ellipsis“⋮” under the 'Actions' column for the service account created above, and click on Manage Keys.
7. Click + Add Key.
8. Click Create New Key.
9. Make sure that JSON is selected as "Key Type."
10. Click Create.
11. Click Close.
    • 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 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.
12. From the service account that was set up in Step 3: Create a Customer Tenant Account.
    • Find the Unique ID field for that service account by clicking the Column Display Options “|||” button in the upper right corner above Actions.
    • Select the Unique ID checkbox.
    • Click Ok.
    • Copy the unique ID number. This is the Client ID number that will be used later on.
      • This Client ID should be considered similar to Administrator account passwords and handled securely.

Setting the Scopes for the Migration

From the Google Admin Dashboard, follow the steps outlined below.

1. Click on Security.
2. Click on API Controls.

3. On the API Controls page, locate the section Domain-wide delegation.

4. Click on Manage domain-wide delegation.

5. Click on Add new.

6. In the client Name field, enter the Service account's Unique ID.

7. For OAuth scopes, enter the scopes listed below:

   • admin.directory.group.readonly
   • admin.directory.user.readonly  
   • calendar.readonly
   • drive
8. Click Authorize.

Prepare Destination Environment

Prepare the destination environment by following the steps below:

1. Create the SharePoint site and make a note of the site URL where the document libraries are stored.
2. Create the document libraries on the destination SharePoint Online site (optional). To learn how to create it, follow the steps from Microsoft: Create your document library.

3. Ensure all necessary users/groups (including external users, if any) are set up at the SharePoint site and available for your destination document library.

Application Permissions for SharePoint

Continue configuring your destination environment by selecting one of these application permissions options and following the steps to enable permission levels at the destination.

Steps to remove these permissions are provided below in the Post-Migration section.  

MigrationWiz Steps

Set Up a Document Migration Project

Please follow these steps to perform a Google Sites to SharePoint Sites migration.

1. From the MigrationWiz dashboard, click Go To My Projects.

2. Click Create Project.

3. Select a Document Project migration type. 
4. Click Next Step.
5. Enter a project name and select a Customer from the list. To create a new customer, follow the next steps:
   1. Click New, and provide the required details, such as primary email domain and company name
   2. Click Save.

6. Click Next Step.

7. Select the Google Modern Sites endpoint from the source drop-down menu. If an endpoint has not been created, follow the next steps.
   1. Click New and enter a name in the Endpoint Name field.
   2. Select Google Modern Sites from the Endpoint Type drop-down menu.
   3. Upload the JSON file for your service account setup.
   4. Provide a valid super administrator email address for the Google Suite account that matches the end user domain.
8. Select the SharePoint Sites destination endpoint from the destination drop-down menu. If an endpoint has not been created, follow the next steps.

   1. Click New and enter a name in the Endpoint Name field.

   2. Select SharePoint Sites from the Endpoint Type drop-down menu.
   3. Write down the SharePoint Sites URL.
   4. Enter the Microsoft 365 administrator credentials such as username, and password.

9. Click Save And Go to Summary.

10. Click Save Project.

Add Sites

Add the accounts that will be migrated, which are also referred to as items, to a project using one of the following options:

• Quick Add: This option allows you to add items one at a time. Provide the Site addresses for the source and destination respectively.
  

• Bulk Add: This option allows many Sites to be added to the project via the CSV template. For more information regarding this topic, please review the Bulk Add section of the  Advanced Options & General Options article.

In any case, go to your project dashboard, click Add, and select Quick Add or Bulk Add.

Advanced Options

Support Tab

Recommended Options

The following options are most valuable for this migration scenario:

• UseApplicationPermission=1 Add this support option in case you select App-Based Authentication. Otherwise, you will not be able to perform the migration.

Verify Credentials

1. Open the project containing the items you wish to validate.

2. Select the line items to validate.

3. Click the Start button in your dashboard.

4. Select Verify Credentials from the drop-down list.

5. Once complete, select the Status section and view the verification results.

Performing a Migration

Run Retry Errors

Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.

If the issues persist contact Support.

Multi-pass Migration

MigrationWiz overwrites the entire SharePoint Site at the destination in a multi-pass migration. MigrationWiz cannot watermark individual HTML pages or sections of pages. Therefore, any edits done at Source causes all site pages to be overwritten at the destination. This only applies to the page structure and page content.

The embedded document is handled separately in a multi-pass situation. According to the existing workflow, individual files are watermarked. Therefore, only documents edited at source are being migrated in a multi-pass migration. Files at the destination will not be overwritten.

Considerations

Keep in mind the following points when performing a multi-pass migration from Google Sites to SharePoint Sites.

• MigrationWiz allows you to enable the reset feature whenever you want. Besides, this feature does not affect the multi-pass migration process and helps you fix any errors or exceptions that might come up during the migration process.
• MigrationWiz cannot watermark individual HTML pages or sections of pages, therefore, you can watermark at the source, applying the change to the destination. 
• The multi-pass migration overwrites everything on the site except documents. This means that

  the site's content and images are replaced with the ones from the source. However, any new or edited documents added to the source since the last migration are brought to the destination. 

Post Migration Steps

Remove the Authentication App

You can remove the Authentication App in Entra Center.

1. Sign in to Microsoft Entra admin center.
2. Select Microsoft Entra ID.
3. Go to Identity > Applications > Enterprise applications, in the left bar of the window.
4. In the Manage section, select All applications, look for the application permission you configured (MigrationWiz-SharePoint-Delegated or MigrationWiz-SharePoint-FullControl), and select it.
5. Go to Manage > Properties, and select Delete from the properties bar.