Microsoft Teams Private Chat Migration moves personal (1:1 and group) Teams chats from one Microsoft 365 tenant to another, including text conversations, file attachments, and associated metadata where the migration path supports them. Migrating Teams chats across tenants is newly possible natively: Microsoft's Cross-Tenant Orchestrated User Data Migration — in public preview since December 2025 — bundles Teams chat migration with Exchange and OneDrive in one PowerShell-driven workflow, requiring Microsoft 365 E3/E5 on both tenants plus per-user Cross-Tenant User Data Migration licenses. Where the preview path or its prerequisites do not fit, IT Partner uses third-party migration tools (such as AvePoint or BitTitan) with Microsoft Graph API-level access. The service is $7 per user plus a $1,500 tenant fee, over 5 days.
Private Teams chats have long been the hardest data to carry through a tenant-to-tenant migration. That has changed: Microsoft's Cross-Tenant Orchestrated User Data Migration natively bundles Teams chat migration with Exchange mailboxes and OneDrive in one orchestrated workflow. It entered public preview on December 16, 2025 and remains in preview, and it comes with real prerequisites — cross-tenant setup between the two tenants, Microsoft 365 E3 or E5 licensing on both sides, and a per-user Cross-Tenant User Data Migration add-on license. IT Partner assesses whether the native preview path fits your tenants and risk tolerance; where it does not, established third-party migration tools (such as AvePoint or BitTitan) working through Microsoft Graph API-level access carry the chats instead. Either way the engagement covers assessment of both environments, migration tooling configuration, execution of the chat transfer, monitoring, remediation of issues, and post-migration verification of completeness and accuracy in the destination tenant.
Our team will thoroughly assess the source and destination environments to ensure a seamless migration process.
We will set up and configure the migration tool, customizing it to meet the specific needs of the migration.
Initiate the migration process, overseeing the transfer of personal Teams chats from the source to the destination tenant.
Constantly monitor the migration progress, intervening if any unexpected challenges arise, to ensure a successful outcome.
Verify the completeness and accuracy of migrated chats in the destination tenant, confirming that all critical communication records have been successfully transferred.
Assessment of the source and destination tenants, selection and configuration of the migration path, migration of personal (1:1 and group) Teams chats, monitoring during transfer, remediation of issues, and post-migration verification of completeness and accuracy in the destination tenant.
Yes — and natively, which is new. Microsoft's Cross-Tenant Orchestrated User Data Migration bundles Teams chat migration with Exchange and OneDrive in one orchestrated workflow. It has been in public preview since December 16, 2025, so IT Partner treats it accordingly: assessed per project, with third-party tools (such as AvePoint or BitTitan) as the alternative where preview status or prerequisites do not fit.
Cross-tenant migration setup between the two tenants, Microsoft 365 E3 or E5 licensing on both sides, and a Cross-Tenant User Data Migration add-on license per migrating user, per Microsoft's requirements. IT Partner identifies the licensing impact during assessment.
Text conversations, file attachments, and associated metadata where the selected path supports them. Some properties — reactions, edits, read receipts, pinned states, system messages, meeting context — may not recreate exactly; the assessment documents the fidelity limits of the selected path before execution.
The service is $7 per user plus a $1,500 tenant fee, over a 5-day engagement, quoted in writing before work begins. Microsoft licensing (including Cross-Tenant User Data Migration add-ons where the native path is used) is purchased separately by the client.
No — the scope is private chat data. Teams channel and structure migration is a separate service, as are SharePoint and OneDrive migrations. Notably, even Microsoft's native orchestration does not cover Teams channels or SharePoint sites, so those always require their own scope.
Dedicated licensed accounts in both tenants, granted permissions and Microsoft Graph API-level access for the migration tooling, user identity mapping for chat participants, and — if the native Microsoft path is selected — the cross-tenant setup and licensing Microsoft requires.
Five stages: pre-migration assessment, migration tooling configuration, migration execution, monitoring and validation, and post-migration verification. IT Partner intervenes on issues during transfer and reviews verification results with your team.
The migration is designed to minimize disruption — chats are extracted and written to the destination while users keep working. Expected user impact, timing relative to the wider tenant migration, and the communication plan are confirmed during assessment; a zero-impact migration is not guaranteed.
Yes. You define migration requirements with IT Partner during assessment, including timelines and priority users or chats, and the migration plan is built around them.
IT Partner monitors the transfer and performs post-migration verification of the completeness and accuracy of migrated chats in the destination tenant. The client then reviews and confirms the migrated data as part of closeout.
Teams channel conversations and team structures, tabs, apps, bots, Planner, OneNote, and Loop components; broader tenant migration workloads (Exchange, OneDrive, SharePoint, identity, Intune); content unavailable to the tooling (deleted, purged, retention-expired, or Graph-inaccessible items); custom development beyond the configured tooling; license purchases; remediation of pre-existing tenant issues; and formal compliance or chain-of-custody attestation. Each can be scoped separately where applicable.