Skip to content
← All Migration Paths

MIGRATION GUIDE

Migrate Microsoft Teams to Google Chat

Switching from Microsoft 365 to Google Workspace? MigrationFox moves Teams channels, messages, message attachments, and the channel's document library into Google Chat, preserving conversation history and channel structure. Files land in a dedicated Shared Drive owned by your organization, not anyone's personal Drive.

Before you plan a Teams source. Reading channel messages from a Teams source depends on Microsoft’s approval for its protected Teams APIs, so contact us before you plan a cutover. Slack to Teams doesn’t need it.
Who can read the migrated files. MigrationFox puts a team’s migrated files (message attachments and channel files) in one Shared Drive and automatically gives everyone in your Google Workspace domain read access to it, so attachment cards open for every space member. The domain is the one of the account MigrationFox acts as. Private and shared channels are included unless you leave them out, so files from a private channel become readable by anyone in your domain, not only that channel’s members. It isn’t public: people outside your domain can’t open them. To keep private-channel files private, leave those channels out of this migration, or remove the domain access from the Shared Drive in Google Drive after the migration and share it with the right people.

What Gets Migrated

What Doesn't Get Migrated

A few Teams features don't have direct equivalents in Google Chat and are intentionally skipped:

How Messages and Channel Files Are Copied

A Teams to Google Chat migration runs as two linked jobs:

  1. Chat migration job: walks Teams channels, creates Google Chat spaces, migrates messages, and stages message-attached files. This job creates the destination Shared Drive and renders attachment cards in the migrated Chat messages.
  2. Companion file job: auto-spawned alongside the chat job. Migrates the channel's SharePoint document library (the "Files" tab content) into the same Shared Drive under per-channel folders, the same way a SharePoint to Google Drive migration does.

Both jobs target the same Shared Drive, so you get one Drive at the destination with two sections: per-channel folders for the document library, and inline-attachment folders for files referenced in messages.

Step-by-Step: How to Migrate

Step 1: Sign up for MigrationFox

Create an account at app.migrationfox.com. Cloud migrations start with 2 GB of free credits, no credit card required.

Step 2: Prepare Google Workspace (4 prerequisites)

Google Chat migrations require a service account with domain-wide delegation. The Chat Migration wizard shows these inline before you connect, but the steps are:

  1. Create a service account in Google Cloud Console and download the JSON key
  2. Grant domain-wide delegation in Google Admin with three Chat scopes (chat.import, chat.spaces, chat.messages) plus Drive scopes for file staging
  3. Enable the Chat API in your Cloud project
  4. Configure your Chat app in the Chat API Configuration tab

The wizard walks you through each step with deep links. Full instructions are in the Google Chat setup article in the in-app help (sign in to your free account to open it).

Step 3: Connect Microsoft Teams

Go to Connections → New → Microsoft Teams and choose Connect with admin consent. A Microsoft 365 admin approves the MigrationFox Teams app once for the tenant, which lets MigrationFox read channels, messages, channel files and the team’s SharePoint document library. (You can bring your own Azure app instead.)

Step 4: Connect Google Workspace

Upload the service account JSON file from Step 2. MigrationFox checks that it can act for your users in both Google Chat and Google Drive. One service account covers both, because the Drive scopes are part of the same domain-wide delegation grant.

Step 5: Create the migration

Start a new Chat Migration. Pick your source team, select channels, and choose the impersonation user (the Google Workspace user the migration acts as). Optionally upload a CSV file mapping Teams user emails to Google Workspace emails for bulk user mapping.

Step 6: Run the migration

MigrationFox creates the destination Chat spaces (prefixed with the team name), migrates messages with attachment cards, and provisions the Shared Drive. The companion file job spawns automatically and starts uploading the channel document library in parallel. Both jobs surface live progress in the dashboard.

What the destination looks like

After migration completes:

Pricing

Teams to Google Chat migrations are billed by the gigabytes of file data transferred (message attachments + channel document library files). Messages themselves don't count against your quota. Every account starts with 2 GB of free credit on MigrationFox web, no credit card required. Discovery scans are always free.

Frequently Asked Questions

Do channel files migrate too, or only chat messages?

Both. Inline message attachments and the channel's broader document library both migrate, via two coordinated jobs that target the same Shared Drive. Files referenced in messages render as attachment cards on the destination Chat message; files from the document library land in per-channel folders for browsing.

Are original sender names and timestamps preserved?

The original Teams sender name and timestamp are preserved in a quote-block header above each message body. Google Chat's API doesn't allow third-party apps to post as other users, so the actual destination author is the Google Workspace service account, but the header text makes original attribution visible to anyone reading the migrated channel.

Where do channel files land at the destination?

In a new Shared Drive named MigrationFox - <TeamName>, organized into per-channel folders. Shared Drive ownership means files survive admin account churn. They don't disappear if the impersonation user leaves the org.

What about emoji reactions, Teams tabs, and @mentions?

Reactions are summarized as one line under each message (for example “Reactions: like×3”), not as live Google Chat reactions. Teams tabs (pinned SharePoint pages, Forms, websites) are skipped because they have no Google Chat equivalent. @mentions are preserved as plain text in the message body but not converted to live Chat mentions. System messages (joined, renamed, app added) are skipped to keep the destination clean.

Can I map Teams users to Google Workspace users in bulk?

Yes. The Chat Migration wizard step for users accepts a CSV upload with columns sourceEmail, destEmail (plus optional display names). MigrationFox merges CSV mappings with auto-detected email matches, then shows applied / added / skipped counts before you commit.

How long does a typical migration take?

Message migration runs in parallel across channels with throughput bound primarily by Google Chat's import-mode quotas. Each destination space is created once, then its messages are imported. Total time depends mostly on message count, file volume and Google’s quotas, so run a scan first to see the size of the team.

Start your Teams to Google Chat migration

Start free with 2 GB on MigrationFox web. No credit card required.

Start Free →