How to Export a Teams Chat (2026): Every Method That Works

How to Export a Teams Chat

Microsoft Teams has no export button for chats. There is no "Save conversation" or "Export to file" anywhere in the Teams client - a gap that surprises everyone who needs a chat in writing for the first time. Exporting a Teams chat is still possible, but the method depends on who you are (the chat participant or an admin) and, critically, on whether the person whose chat you need still works at the organization. This guide covers every method that actually works in 2026, verified against Microsoft's current documentation, including the scenario that fills the Microsoft Q&A forums: getting a departed user's Teams chat out in readable form.

Method 1: Manual Copy (Participants, Small Chats)

For a chat you are part of and only need occasionally, the low-tech options work:

• Select and copy. Click the first message, scroll, Shift-click the last, copy, and paste into Word or OneNote. Formatting partially survives; images and reactions mostly do not.
• Print to PDF. With the chat open in the Teams web client, the browser's print function captures what is currently loaded on screen - which for long chats means scrolling up repeatedly first to load history.

Fine for a one-off. Useless for compliance, for long histories, and for any chat you are not a member of.

Method 2: Purview eDiscovery (Admins - the Supported Route)

Teams chat messages are journaled into the participants' Exchange Online mailboxes as compliance records, which is why Microsoft's supported export path for Teams chats is the same eDiscovery flow used for email:

1. Go to the Microsoft Purview portal (purview.microsoft.com) with an account holding eDiscovery permissions.
2. Create a case and a search; scope the data source to the user's mailbox and add keywords or date ranges to find the conversation.
3. Run an export. Two options matter for Teams content: "Include Teams and Viva Engage conversations" pulls in messages posted around each matching item so threads stay coherent, and "Organize conversation into HTML transcript" assembles chat messages into a readable, threaded HTML transcript rather than hundreds of individual message files.
4. Download the export package from Process manager in the browser.

The transcript option is the closest Microsoft gets to "export a Teams chat in a readable format." It works for 1:1 chats, group chats, and channel messages (channel messages are journaled to the Team's group mailbox). For the mailbox side of the same workflow, see how to export an Office 365 mailbox to PST.

Worth knowing: the old PowerShell export command (New-ComplianceSearchAction -Export) was retired by Microsoft in May 2025, and the classic Content Search interface followed in August 2025 - guides describing either are out of date.

Method 3: The Microsoft Graph Export API (Developers)

Microsoft provides Teams Export APIs in Microsoft Graph that can programmatically retrieve chat messages, including for deleted users. They are protected APIs: access requires a formal application to Microsoft justifying the use case, and message retrieval is metered and billed per message. This is the route for ISVs and large enterprises building their own tooling - not a practical answer for an admin who needs one conversation this week.

The Hard Case: Exporting a Teams Chat After the User Has Left

This is the scenario behind the most-viewed forum threads - literally titled things like "how to export a Teams chat conversation in a readable format after a user has left the organization." The answer depends entirely on what happened to the departed user's account:

• Account still exists (licensed or on litigation hold): the eDiscovery method above works. The chat compliance records are in their mailbox, searchable and exportable.
• Licence removed, account deleted: the mailbox - and the Teams chat records journaled inside it - follows the deletion clock. Once the account is permanently deleted (30 days after deletion, by default), those chat records are gone. No eDiscovery search can find a mailbox that no longer exists.
• The workaround Microsoft offers is keeping the mailbox alive: hold a licence for the account, or place it on hold and convert to an inactive mailbox - both of which carry licensing requirements and keep the data inside a system built for lawyers, not for the manager who just needs to read a conversation.

In other words: whether a departed user's Teams chat is exportable is decided at offboarding time, months before anyone asks for it. If the account was simply deleted to save the licence, the answer to "can we get the chat?" is no.

Retention Policies Are Not Export

A common misconception: "we have a Teams retention policy, so the chats are backed up." Retention policies control how long Teams messages are kept or deleted - they stop users purging history and enforce deletion schedules. What they do not do is give you a copy: there is no export in a retention policy, the retained data still lives inside the user's mailbox (with the same departed-user problem above), and reading it still requires the eDiscovery workflow. Retention answers "how long does it exist?" - not "can I have it in a file?"

The Automated Alternative: Archive at Offboarding

Chipmunk closes the departed-user gap by making the archive decision automatic. When an account is disabled in Microsoft Entra ID, Chipmunk archives the user's Teams chats, Exchange mailbox and OneDrive into Azure Blob Storage in your own subscription - then the licence can be reclaimed without destroying the data.

When the request for a chat arrives later, there is no eDiscovery case and no PST: open the departed user's archive, search or browse to the conversation, read it threaded, and export it for legal, HR, or the manager who asked. Every access is captured in an audit trail, retention and immutable storage tiers are available in your own Azure, and the archive stays searchable across every departed user at once. Chipmunk deploys from the Azure Marketplace into your own environment - the full workflow is in the Microsoft 365 departed user archiving guide.

Frequently Asked Questions

How do I export a Teams chat conversation? For a chat you participate in, copy-paste or print-to-PDF from the Teams web client are the only built-in options - Teams has no export button. For anything bigger, an admin exports via Purview eDiscovery: search the participant's mailbox (Teams chats are journaled there as compliance records) and export with the "Organize conversation into HTML transcript" option for a readable, threaded transcript.

How do I export a Teams chat after the user has left the organization? Only if their mailbox still exists. If the account is licensed or was placed on hold (inactive mailbox), Purview eDiscovery can search and export their chats as HTML transcripts. If the account was deleted and the deletion window has passed, the chat records went with the mailbox and cannot be recovered. Tools like Chipmunk avoid this by archiving Teams chats, mailbox and OneDrive automatically at offboarding, so the conversation is retrievable from your own Azure storage regardless of what happened to the account.

Does a Teams retention policy back up chats? No. Retention policies control how long messages are kept or deleted - they prevent premature deletion but provide no export and no separate copy. The retained messages still live in user mailboxes, so a departed user's deleted account still takes its chat history with it, retention policy or not.

Can I export a Teams chat to PDF or a text file? Not directly from Teams. The practical paths are print-to-PDF from the Teams web client (participants, short chats), the eDiscovery HTML transcript export (admins - HTML opens in any browser and prints to PDF cleanly), or an archiving tool that stores chats in readable, exportable form.

Related reading

• How to export an Office 365 mailbox to PST
• Microsoft 365 departed user archiving: the full workflow
• How to archive a shared mailbox
• Inactive vs shared vs archive mailbox

Decide at Offboarding, Not at the Request

Whether a departed user's Teams chat can ever be exported is decided the day they leave. See how Chipmunk archives Teams chats automatically - it deploys from the Azure Marketplace into your own Azure environment. Questions: sales@smikar.com.