Export Slack Data and Teams Archives Before a Business Closes

For many businesses, Slack or Microsoft Teams has replaced much of internal email. Decisions, handovers, problems and fixes are discussed in channels and chats. When a business closes, these workspaces are often lost as soon as the subscription ends. This guide explains how to export Slack data and Microsoft Teams archives, what UK GDPR means for them, and why these archives are now of interest to AI developers.

Why messaging archives matter

Messaging archives record how work actually happened. They show who raised a problem, how it was discussed, what was decided and what followed. For legal and regulatory purposes they may be needed as evidence. For AI developers they are examples of real collaboration that are hard to find elsewhere. They are also among the most sensitive business records, because they are full of personal information.

How to export Slack data

Slack's export options depend on the plan, and they change over time, so check Slack's current help pages before you start.

Public channels

Workspace owners and admins can usually export messages and file links from public channels on all plans, within the plan's history limits.

Private channels and direct messages

Exporting these usually needs a paid plan with the right export feature, and may need an application to Slack.

Enterprise Grid

Organisation owners have broader export and discovery tools.

Files

Exports often contain links to files rather than the files themselves. Download the files separately before the workspace closes.

History limits

Free plans may hide older messages. Upgrading temporarily before exporting may restore access. Check current terms.

How to export Microsoft Teams data

Teams data sits across Microsoft 365:

• Channel messages are stored in the Microsoft 365 group mailbox.
• Chats are stored in each user's mailbox.
• Files shared in channels sit in SharePoint, and files shared in chats sit in OneDrive.

Microsoft Purview eDiscovery is the usual way to search and export Teams content with its metadata. Make sure retention policies or holds stop content being deleted before you export, and keep licences active until the exports are verified.

Preserving context

A useful export keeps:

• channel and thread structure
• timestamps and edit history where available
• user identifiers, kept consistent across the export
• links to shared files, together with the files themselves
• reactions and replies that show agreement or follow-up

UK GDPR and messaging data

Messaging archives are dense with personal data, including names, opinions, and sometimes health or family details. Before any licensing:

• exclude HR, disciplinary and personal channels
• remove special category data
• replace names with consistent pseudonyms so conversations still make sense
• remove phone numbers, addresses and identifiers
• assess whether the use is compatible with what staff were told
• carry out a data protection impact assessment where needed

Read anonymising data before a sale for the techniques involved.

Staff and reputational considerations

Employees used Slack and Teams expecting them to be internal. Even with personal data removed, consider how former staff would view their conversations being licensed. Transparency, careful exclusions and a narrow permitted use all help.

Who might want messaging data

AI developers building workplace assistants and agents want examples of real collaboration linked to tasks and outcomes. Messages that connect to project tickets, CAD revisions or orders are more useful than isolated chat. See how to sell data to AI companies and Jira export and project-software data.

Step-by-step checklist

1. Confirm who holds owner or global admin rights.
2. Check plan limits and keep the subscription active.
3. Put retention holds in place.
4. Export messages, then files.
5. Verify the exports open and are complete.
6. Store them encrypted, with access logged.
7. Decide on retention, deletion or licensing.

If the company is insolvent

The office-holder controls the workspace data. See insolvency data: digital records in liquidation.

How McKays can help

McKays assesses whether communication archives could be licensed responsibly. We start with a description: the platform, the date range, the number of channels and users, and any exclusions. See the sector guides and for advisers.

Common mistakes

• Cancelling the workspace before checking which plan features export private content
• Exporting messages but not the shared files they refer to
• Forgetting guest accounts and shared channels with other organisations
• Losing the mapping between user IDs and roles, which is needed to understand conversations later even after pseudonymisation
• Keeping exports on an unencrypted personal drive

Shared channels with other organisations

Slack Connect channels and Teams shared channels include participants from customers, suppliers or partners. Their messages may be subject to those organisations' rights and confidentiality, and should usually be excluded or handled with particular care.

Verify before you switch off

After exporting, open a sample of the exported material and compare it with the live workspace. Check that older messages, threads, edits and files are present, and that dates and authors look right. Only cancel the subscription once you are satisfied.

FAQ

Can I export Slack DMs?

On some paid plans, and subject to Slack's policies. Check current Slack documentation for your plan.

Where are Teams chats stored?

In users' Exchange Online mailboxes, with shared files in OneDrive and SharePoint.

Do exports include files?

Slack exports usually include file links rather than the files. Teams files sit in SharePoint and OneDrive and need exporting separately.

Is it lawful to license staff messages?

Only with careful handling under UK GDPR, which in practice usually means heavy pseudonymisation and exclusions. Take advice.

What if the subscription has already lapsed?

Contact the provider quickly. Data may be held for a short period after cancellation.