How to Migrate 1:1 Chat Messages Between Teams Tenants

This guide explains how to migrate one-on-one (1:1) chat messages between Microsoft 365 tenants using Cloudiway's Teams migration tool. The process preserves chat history while ensuring users can continue their conversations in the new tenant.

Overview

Microsoft Teams 1:1 chat migration transfers private conversations between individual users from one tenant to another. Cloudiway offers flexible options for how messages are delivered to the target tenant:

Prerequisites

Before starting the 1:1 chat migration, ensure:

• Source and target connectors are configured and tested
• User mapping is complete (source users mapped to target users)
• All users have valid Microsoft 365 licenses including Teams in both tenants
• Administrator accounts in connectors have Teams licenses
• The EntraID application has appropriate Teams permissions

Step 1: User Discovery

First, retrieve the list of users whose chat messages you want to migrate:

1. In the Cloudiway portal, navigate to your Teams migration project
2. Go to Group User List → MIGRATION
3. Select your Microsoft 365 pool from the dropdown
4. Click the GET LIST button to retrieve available users
5. The system will populate the list with users from your source tenant

Step 2: Configure Settings

Before migrating, configure how messages will be handled:

1. Navigate to Global Settings in your project
2. Locate the Teams 1:1 Chat section
3. Configure the following options:

Step 3: Start Migration

Once users are listed and settings configured:

1. Select the users you want to migrate from the list
   • Use checkboxes to select individual users
   • Or use "Select All" for bulk selection
2. Click the Migrate button
3. Confirm the migration when prompted
4. The migration will begin processing selected users

Message Handling

Here's how Cloudiway handles 1:1 chat messages during migration:

Recent Messages (Direct Injection)

• The 100 most recent messages per chat are injected directly into the Microsoft Teams chat in the target tenant
• Messages appear as native Teams messages
• Original timestamps are preserved
• Attachments and inline images are included

Older Messages (HTML Archive)

• The next 1,000 messages per chat (beyond the 100 direct) are exported to an HTML file
• HTML file is uploaded to the user's OneDrive
• Files are organized by conversation partner
• Format preserves readability with timestamps and sender information

Monitor Progress

Track your migration progress:

1. Select a user from the migration list
2. Click on the Logs tab
3. Review detailed information including:
   • Number of chats processed
   • Messages migrated per chat
   • Any errors or warnings
   • HTML archive file locations

Understanding Migration Status