Google Chat to Teams Migration Guide

Overview

This Google Chat to Teams Migration Guide shows you how to migrate your Google Chat messages and Google Spaces to Microsoft Teams. Cloudiway ensures that your messaging migration runs smoothly while preserving conversation history and metadata.

Migration Features

What's Migrated

The following items are migrated during a Google Chat to Teams migration:

Limitations

Meeting-linked Google Spaces are not supported. These are automatically created by Google Meet whenever a Calendar event has Meet attached. The avatar is a small calendar/document icon, and the name typically includes the meeting date or a recurring-meeting label.

Prerequisites

Before you start, ensure you have the appropriate permissions and accounts configured.

Google Prerequisites

Google feeds need to be granted. Administrator credentials are required.

Microsoft 365 Prerequisites

Migration uses a mix of Graph APIs and CSOM calls, which require specific permissions. An Entra ID application needs to be installed, and global tenant admin credentials are required.

Cloudiway Prerequisites

Two types of licenses are required for Google Chat to Teams Migration:

• Licenses for migrating the Spaces
• User licenses (CAL) for migrating the Google Chats

Contact Cloudiway Sales to request pricing and quotes.

Migration Process

The Google Chat to Teams migration follows these steps:

1. Create the source and target connectors
2. Discover the Spaces and users or upload your list from a CSV file
3. Configure the target location and Target Connectors
4. Fill the Mapping Table
5. Optionally run an Audit to count the number of messages in each Space
6. Run the Pre-Processing task to create the target teams and migrate the permissions
7. Run the Google Chat to Teams migration
8. Close the Team

Step 1: Create Connectors

To facilitate the Google Chat to Microsoft Teams migration, the Cloudiway platform needs to communicate with both your source and target domains. You will need to set up a connector for each source tenant and each target tenant.

Google Connector

To configure your Google connector, follow the steps in the Google Workspace connector configuration guide.

Microsoft 365 Connector

Follow the Microsoft 365 connector configuration guide to create the Microsoft 365 connector.

Step 2: Discovery

There are three ways to retrieve or upload your Google Spaces: Run a Get List, upload a CSV, or manually create a single entry. We recommend running the Get List task as it will automatically fill your migration list.

Option 1: Get List

The discovery task retrieves the list of all users of your tenant (for all domains defined in the Google Source connector). For each user, it discovers their Google Spaces and stores them in the list.

Select the Group List tab under the Sites product.

Under MIGRATION, click on the Get List option:

In the popup window, select your source connector and the type of elements you wish to retrieve (Google Spaces), then click Get to start the process.

Once the list is retrieved, you need to define the target locations for each entry.

Option 2: CSV Import

The second way to edit the migration list is to upload a CSV file.

Check the CSV file format guide for generating the CSV file correctly.

Click MANAGE > Import. Select the CSV File, the Source and Target Connectors, then click Upload.

After uploading a CSV file, there is no need to define the source and target location.

Option 3: Manual Creation

You can also manage and create your list manually. Click the MANAGE tab, and from the drop-down list click Create, then fill all the required fields.

Step 3: Configure Target Location

You can choose where to migrate your Space:

1. Into a team (General channel of the team)
2. Into a specific channel
3. Into a private channel

If you want to migrate into a specific channel, set the name of the team in the Target Name field, and the name of the channel in the Target Channel Name field. If you leave these fields blank, the Space will be migrated into the General channel of the team.

If the team or the channel doesn't exist in the target, it will be created during the pre-processing task.

Merging Multiple Google Spaces into a Single Team

If you want to merge several Google Spaces into a single Team in the target, migrating each Google Space into a separate Team channel, you have to specify the same:

• Target Name
• Target Email Address Nickname

These both parameters refer to the target Team.

In each migration line item, specify a different Target Channel Name where each Google Space will be migrated into.

Mass Modify Your List

If you have run a discovery and pulled all your Spaces, but don't want to edit the list one by one, you can use mass modification options:

• Assign Target: Automatically assign a target connector to the selected entries
• Add Prefix: Automatically rename and add a prefix to selected entries
• Change Target Recipient: Automatically set the Recipient Type

In the Group List, check one or more objects that you want to modify, then go to MANAGE and select the action.

Step 4: Mapping Table

Permissions and metadata may contain email addresses. During the migration, these addresses must be converted into target accounts. The conversion is automatically done by the platform using the mapping table.

Cloudiway automatically populates the mapping table during the Discovery process. However, it is your responsibility to check and validate the mapping table before starting the migration, as entries may be missing or emails may be different at the target.

Step 5: Audit (Optional)

The audit is optional and purely informative. It connects to the source Space and counts the number of messages, replies, and files.

To run the Audit, in Group List, select an entry and click MIGRATION > Audit.

Step 6: Preprocessing

The pre-processing tool performs two tasks:

1. It connects to the Source Space and adds the migration account defined in the Google connector as owner of the space. This is mandatory by Google APIs, otherwise the migration account cannot access the space.
2. It creates the team at the target if it doesn't already exist:
   • It uses the Graph APIs and gives the owner role to the migration account defined in the target connector
   • It migrates membership and ownership

To pre-process a Space, in the Group List, select an entry and click MIGRATION > Pre-Processing.

Step 7: Migration

The Google Chat to Teams migration tool leverages Microsoft Teams Import APIs to maximize throughput. Learn how Microsoft Teams Import APIs work.

In Group List, select an entry and click on MIGRATION > Start.

The migration will start as soon as there is a free spot on the platform. You can monitor your migration by clicking on an entry and checking the logs.

Step 8: Post-Migration (Close the Team)

When your migration is completed, run the Post Migration Task. This will close the Team that has been created in import mode.

Chat Messages Migration

From the group user list, simply select a user and start the migration to migrate their chat messages.

Troubleshooting

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

Please visit the knowledge base: https://help.cloudiway.com

Support tickets are opened through the platform. Once logged in, go to your project and select Help > Support. The chatbot will ask you a couple of questions and then open a support ticket.

More information regarding our support program is available on our Support Home Page.

Frequently Asked Questions