During a tenant-to-tenant migration, Teams chats and channel data need to be handled separately because Teams stores different types of content across Microsoft 365 services. Microsoft confirms that Teams chat data includes private messages and channel messages, while Teams files are stored through SharePoint and OneDrive.

With the Aryson Tenant-to-Tenant Migration Tool, the migration can be planned around the Teams workload along with other Microsoft 365 data. The key consideration is that 1:1 and group chat history is more complex than Teams/channel content, and the exact data that can be transferred depends on the migration method and Microsoft API capabilities.

What happens to Teams data?

• Teams and channels: Team structure and channel-related content can be migrated as part of the tenant-to-tenant project.
• Channel messages: Historical channel messages can be imported into existing Teams channels using Microsoft's migration APIs.
• 1:1 and group chats: These require dedicated Teams chat migration handling. Microsoft's current Graph migration APIs support importing historical messages into 1:1 and group chats under specific migration requirements.
• Teams files: Files shared in Teams are backed by SharePoint/OneDrive, so these workloads should be migrated alongside Teams rather than treated as ordinary chat messages.
• Message history: Where supported, migration APIs can preserve original authorship and historical timestamps when importing messages.
• Migration mode: Teams chats/channels can temporarily enter migration mode while historical messages are imported, after which migration is completed and normal access resumes.

In short: Aryson Tenant to Tenant Migration can be positioned as a solution for transferring Microsoft 365 workloads during tenant consolidation, merger, acquisition, or organizational restructuring, while Teams chats, channels, and their associated files should be assessed separately to determine exactly what can be migrated and how. Microsoft itself recommends planning Teams alongside Exchange because of workload dependencies.