Migrating chat messages from Teams using the new data migration service is currently in beta and subject to the Pre-General Availability Offerings Terms in the Google Workspace Service Specific Terms.
Here's how to address common issues encountered during chat migration from Microsoft Teams to Google Chat using the new data migration service.
- Can't start a migration
- Needs permission to access resources error
- Issues with users
- Error uploading migration map
- Migration fails to start
- Migration completes, but there are failed items
- Missing channels or messages
Can't start a migration
If you get an error when you try to start a migration, make sure that a Google Workspace user with super admin privileges sets up and initiates the migration.
Need permission to access resources error
If you get the Needs permission to access resources in your organization that only an admin can grant error, make sure that you're trying to connect to the Microsoft account using a valid Global Administrator account. For details, go to Connect to your Microsoft account.
Issues with users
Before you begin a migration, make sure you set up the user accounts in Google Workspace. For details on setting up user accounts, go to Requirements & setup steps for Google Workspace.
A user account that is not set up or set up incorrectly can cause the following issues in the logs. For information on how to access the logs, go to Download the logs & exit a completed migration.
| Issue | Shown in logs |
|---|---|
| Messages from the missing users and their replies don't migrate. | Logs show that the message didn't migrate and you might get an Empty message error. |
| User isn't added to spaces. | Logs show the user wasn't added to the space (where Target type is shown as Space membership). |
| If the user is a channel owner, the space won't be created. | Logs show the space failed to create (where Target type is shown as Space). |
Error uploading migration map
You might get one of the following errors when uploading a migration map:
- Upload sensitive CSV failed
- Validate CSV failed
- Bulk action initiation failed
To troubleshoot, verify that the following points are correct:
- The CSV file has only one column and the column has Source MicrosoftTeamsID as its header.
- The entries in the file are valid Microsoft Teams IDs.
- A team ID is not listed more than once.
Migration fails to start
If you get the To start migration, you must have super admin privileges and complete all previous steps error, make sure that a super administrator for your Google Workspace account starts the migration.
Migration completes, but there are failed items
- Click View report to download the migration report.
- Identify items that didn't migrate and the reasons for the failure. For details, go to Understand chat migration reports.
- Fix the issues and then run a delta migration.
Missing channels or messages
If you have a missing channels or messages after a migration, work through these steps:
- Check that the migration map lists the teams that own the missing channels. For details, go to Create a list of teams to migrate.
- Verify that your identity map contains the expected list of users. For details, go to Create & upload an identity map.
- Make sure that at least one owner of the channel has a user account in Google Workspace.
- Download the migration report. For details, go to Understand chat migration reports.
- Search for the missing channel using the Microsoft Channel ID. For details on IDs, go to Manage teams in the Microsoft Teams admin center.
- If the message shows as failed in the report, locate the error code in Common error codes & messages. Then, follow the instructions to troubleshoot the error message.
- Run a delta migration.
Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.
