This article provides instructions on configuring a migration batch for migrating Microsoft 365 Teams to Spaces in Google chat. Before proceeding, ensure you have completed the steps in the Migration Guide to set up your migration project and added your Microsoft Teams migration batch.
Prerequisites
Before you begin your migration, ensure you have completed the following essential setup steps:
- CloudM Project Setup: You must have already configured your CloudM Migrate project following the Migration Guide and added your Spaces batch.
- Google Chat API: The Google Chat API must be enabled and correctly configured for the destination environment. Please follow the instructions in our Enable and Configure the Google Chat API guide.
- User Licensing: All migrating users must have an active Google Workspace license and the Google Chat service enabled in the destination.
- Drive Migration: To ensure all supported attachments migrate correctly, you must first migrate all user documents with Record Document Mappings enabled. This step must be completed before you begin the Teams to Spaces migration.
- Migrate Licensing: Each destination Google Space (unique import name) will require a CloudM Migrate license.
Migration Scope
Understanding what data is included is critical for setting expectations.
What is migrated?
- Public channel messages.
- Public channel attachments.
- Private and shared channel messages.
- Private and shared channel attachments.
- Message created date/time.
- The below reactions. These will be posted as the space owner.
- Channel Members (mapped to the corresponding Google Space).
- Inline images.
What is not migrated?
- External members.
- Attachments added using the "Add from OneDrive" or "Browse Team Channels" options.
Understanding Google's "Import Mode"
This migration process uses Google's "Import Mode", which has specific behaviors you must understand.
- Activation: When the migration begins, the destination Space is placed into Import Mode.
- Visibility: While in this mode, the Space is not visible to end-users in the destination. Only the migration service can add content.
- Finalization: To make the Space visible and usable, you must run a final delta migration with the Finalize Spaces import mode migration option enabled.
- Consequences of Finalization: Once a Space is finalized, you can no longer migrate historical messages to it. Only messages created after the finalization time can be migrated in subsequent deltas. This step is irreversible.
The below diagram represents this further.
How does this work?
There are two aspects to a Teams to Spaces migrations, the conversations and the files (attachments).
Attachments
In order to facilitate the migration of attachments, CloudM Migrate will transfer the files from the source Microsoft Team (all document libraries in the backend SharePoint site) to a designated Shared Drive at the destination. The Shared Drive will be named according to the Import Name specified in your configuration. Subsequently, the items within the shared drive will be linked to the respective posts within the Space.
Team Channel to Spaces Mappings
Each Channel within the Team will be transferred to its own Google Space and will be prefixed with the name of the Team. For instance, if there is a Microsoft Team called "Marketing" and a channel called "General", a Space will be created in the destination named "Marketing_General". This Space will include the posts from the General channel of the Marketing Team.
Migration Process
As mentioned above, please ensure you have migrated your users and SharePoint Sites to ensure all supported attachments are migrated.
Follow these steps to configure and run your Spaces migration.
1. Adding Items to Migrate
When adding items to migrate Microsoft 365 groups to corresponding accounts at the destination, follow the format below:
- *Export Type: Microsoft Team
- *Export Name: Mail Nickname of the Source Microsoft Team
- *Import Type: Google Space
- *Import Name: Prefix for the destination Google Space
- Given Name: Not required
- Family Name: Not required
- Documents Path: Not required
- Documents Destination Path: Not required
*Mandatory Field
Further instructions on adding entities to your batch can be found here: Adding Items to a migration batch
For each entity added, you can select the specific data types you wish to migrate. Ensure the 'Migrate' checkbox is enabled for all entities you intend to include in the migration run.
2. Configuration Settings
General Settings
In the General Settings section, ensure all domain mappings are configured correctly to facilitate replacing the source domain with the destination domain during the migration.
You can also apply date range filters for various data types to migrate information within a specific timeframe. Specify the date ranges you wish to include.
Source Settings
For a standard Microsoft 365 Teams to Google Spaces migration, it is recommended to keep most of the source settings at their default values.
For more detailed information on each available source setting, please review the below article.
Microsoft 365 - Source Settings
Destination Settings
For this migration type, you will need to modify the below settings.
- User -> Finalize Spaces import mode migration: Enable this to ensure the spaces are finalised after the migration. This will take the spaces out of import mode leaving them accessible in the destination.
For more detail on additional destination settings, please review the below article.
Google Workspace - Destination Settings
Advanced Settings
For a Microsoft 365 Team to Google Spaces migration, consider the following:
- Address Replacement: It is highly recommended to upload an address replacement CSV that maps source users, aliases and groups to the destination. For more information, please refer to the Address Replacements article.
- Reporting -> Record Document Mappings: Enable this to ensure attachments to be migrated successfully.
3. The Migration Process
The settings described above apply to a single pass migration. If you need to execute multiple migration passes to transfer additional data during a delta, ensure that the User -> Finalize Spaces import mode migration destination setting is enabled only for the final migration pass.