Teams chats do not move with a team. Microsoft documents a chat import for 1:1 and group chats and offers a paid orchestrator that includes Teams chats. Some tools write chats into the new tenant and others save them to disk. Choose by whether people need the history inside Teams or only on record.
You move a team to a new tenant and the channels look fine. Then someone opens Teams and asks where their chats went. Months of 1:1 and group messages are missing, and the answer is not a quick yes or no.
I get this question on almost every Teams project. This guide explains whether Teams chat messages migrate between tenants, which routes exist, what every route changes and how to plan the move so nobody is surprised.
Do Teams Chat Messages Migrate Between Tenants?
They can, but not with a button. Teams has no simple copy chats button. Chats move only when you use Microsoft's migration orchestrator, build your own import with Microsoft Graph or use a tool that does it for you. Everything else leaves chats behind in the source tenant.
Channel messages are a different story. They sit inside a team and travel with it, which I explain in how to migrate Microsoft Teams to another tenant. Chats belong to people, so you need a user mapping before any chat can land.
Which Routes can Move Teams Chats Between Tenants?
Four routes exist. Choose by what you need at the destination, not by price alone.
| Route | What it does | Main limit |
|---|---|---|
| Microsoft 365 migration orchestrator | Moves Teams chats along with mailboxes and OneDrive | Per user license, identity mapping and duplicate threads possible |
| Microsoft Graph chat import | Your own app imports messages into an existing chat | Needs code, app only permission and mapped senders |
| Save chats to disk | Keeps sender, time and text as a record | Chats are not written back into Teams |
| Third-party tools | Some vendors say they write chats into the target tenant | Test the output on one chat first |
What does the Microsoft 365 Migration Orchestrator do With Teams Chats?
Microsoft's migration orchestrator overview lists four workloads you can select in a batch: Exchange mailboxes, OneDrives, Teams chats and Teams meetings. It moves content, not identities, and Teams and channels stay in the source tenant.
Microsoft sets conditions you should read before you plan. Cross-tenant migrations need a per-user license, a one-time fee. Identity mapping is required. Participant lists might change and duplicate threads might appear on both tenants. The original content stays at the source, and it might be in an edited form. The page does not break chats into 1:1, group and meeting types, so test with real users first.
What does the Microsoft Graph Chat Import Allow?
Microsoft documents a way to import messages into existing chats. Its page on importing messages into Teams chats and channels sets the rules, and the chat startMigration reference covers chats directly.
- App only access. The calling app needs the Teamwork.Migrate.All application permission. Delegated access is not supported.
- Migration mode. You put the chat into migration mode, import messages and then complete the migration. Only the app that started it can finish it.
- Chat types. Group and 1:1 chats are supported. Meeting chats are not supported on the chat startMigration page.
- Timestamps. Every message needs a createdDateTime that is later than the chat creation time, not in the future and unique to the millisecond.
- Senders. The from user must belong to the same tenant as the app, so every sender needs an account at the destination.
That is a developer project, not an admin task. It is also why the second route in the table needs code, testing and a plan for senders who no longer exist.
Can You Save Teams Chats to Disk Instead?
Yes, and for many projects it is the safest first step. RecoveryTools Teams Migrator captures 1:1, group and meeting chats per user, with the sender and send time intact. You can exclude chats a user already left and exclude guest accounts, which usually belong to the old organization. The software does not write chats back into the new tenant today, so treat the result as a record, not a live conversation.
A saved record answers the audit question, who said what and when. It does not give people a chat to continue in Teams. Be clear about that difference with your team owners.
Move Teams and Keep Chats on Record
RecoveryTools Teams Migrator copies entire teams or single channels between Microsoft 365 tenants with author and date on every message. It also saves 1:1, group and meeting chats to disk per user. Chats are saved, not written back, and guests stay with the tenant that invited them.
The trial unlocks every option and caps volume at 25 items per channel and per chat. Works on Windows 11, 10 and Windows Server.
How do You Plan a Teams Chat Migration Between Tenants?
Chats make a project longer, not harder. Follow this order and you avoid the surprises I see most.
- List the chat owners. Record which people have chats you must keep. Skip leavers and guests unless a legal need says otherwise.
- Map users. Match every source user to a destination user. Every route above needs this step, and unmatched users are where chats get skipped.
- Create and license the destination users. Chats cannot land in an account that does not exist yet.
- Choose live or saved. Decide whether people need chats inside Teams or only on record. This choice sets the route and the cost.
- Test with two or three users. Open the result in Teams and check sender names, dates and any threads that look doubled.
- Capture chats to disk before cutover. Save a record first, even if you also plan a live import.
- Tell people what to expect. Say which chats arrive, which are saved and which stay behind.
What should You Expect After Teams Chats Move?
Expect small differences. Microsoft says participant lists might change and duplicate threads might appear. The same page says Teams chat messages are never deleted from the source tenant after migration, so keep the source read only until you finish checking.
Teams meetings and their chats depend on one another, and Microsoft says the batch fails to start if you select Teams meetings without chats and mailboxes. For the full list of gaps, read what does not migrate in Microsoft Teams.
What are the Best Practices for Moving Teams Chats?
- Map users first. Chats follow people, so a clean mapping file saves the most rework.
- Save before you write. A disk record protects you if a live import goes wrong.
- Test small. Two or three users show you every surprise before it reaches thousands.
- Keep the source. Leave the old tenant read only until the owners sign off.
- Set expectations early. Tell owners which chats will not appear and why.
Which Mistakes Break a Teams Chat Migration?
Four show up again and again. First, promising users that chats will arrive before you choose a route. Second, skipping the user mapping. Third, forgetting that meeting chats are not supported by the Graph chat import. Fourth, closing the old tenant before anyone checks the result.
My Verdict on Moving Teams Chats
Chats can move, but only through Microsoft's orchestrator, a custom Graph import or a tool built for it. Decide whether people need chats inside Teams or on record, then choose the route that matches.
I always save a record first. A copy on disk costs little and answers every audit question later.
Frequently Asked Questions
Do Teams Chats Migrate With a Team to Another Tenant?
No. Chats belong to people, not to a team. Channel messages travel with the team, but 1:1, group and meeting chats need a separate route.
Can Microsoft Move Teams Chats Between Tenants?
Yes, through the Microsoft 365 migration orchestrator. It lists Teams chats as a workload, needs a per-user license and identity mapping and warns that participant lists might change and duplicate threads might appear.
Does the Graph Chat Import Support Meeting Chats?
No. Microsoft's chat startMigration page says group and 1:1 chats are supported and meeting chats are not.
Can You Keep Teams Chat History Without Writing It Into the New Tenant?
Yes. RecoveryTools Teams Migrator saves 1:1, group and meeting chats to disk per user with the sender and time, so the record exists even though the chats are not written back.
Do Chats Get Deleted From the Source Tenant After Migration?
No. Microsoft says Teams chat messages are never deleted from the source tenant after an orchestrator migration. Keep the source read only until you finish checking.
What Happens to Chats With Guests and Deleted Users?
Guests belong to the tenant that invited them, so the new tenant has to invite them again. A sender who has no account at the destination cannot be mapped, so decide in advance how those chats are handled.
How Long does a Teams Chat Migration Take?
It depends on message volume and Microsoft throttling. Microsoft calls its timing guidance only guidance, not an SLA, so test a small group first and size the window from the result.
Jamie blends strategic marketing insight with technical writing, turning migration and recovery topics into guidance that works for technical and general readers alike.
Published 16 October 2026. Chat import rules and orchestrator terms come from Microsoft's pages on the migration orchestrator, importing messages into Teams and chat startMigration. Product behavior comes from the RecoveryTools Teams Migrator page. Microsoft updates these pages often, so check them before you start.