Microsoft Teams or Slack consolidation: archiving the platform you drop

Why archive instead of migrating everything?#

Archiving instead of migrating everything keeps old conversations complete while letting people start clean in the platform they will actually use. Migration tools differ in how they carry authorship, threads, edits, reactions, file links and timestamps, and a partial migration can produce history that looks complete but is not.

The archive-don't-migrate rule is simple: move channels with active work and recent decisions, and archive everything in the old platform's native export format. People search the new platform for current work and ask the records custodian for anything older.

The rule also cuts cost and risk. Migrating years of channels means paying for migration capacity, re-permissioning private spaces, and explaining to employees why old messages may now appear under a migration account instead of the original author.

Which channels move, and which stay in the archive?#

Channels move to the new platform only when people will keep working in them. Every channel goes into the archive, including the ones that also move, because the archive is the record of the old platform exactly as it stood on the cutover date.

Agree on the list with department heads before cutover. People overestimate how many old channels they need live, and a short list makes the migration faster and cleaner.

How do you archive a Slack workspace you are retiring?#

Archiving a Slack workspace you are retiring starts with your plan, because Slack's export options depend on it. Slack says Workspace Owners and Admins on every plan can export messages and file links from public channels, while exports that include private channels and direct messages are offered only on Business+ and Enterprise plans and require owners to apply.

Do not use a third-party app pulling data through the API as your archive method. Slack's API terms bar providers of externally offered apps from bulk exporting message and file data or using it to train a large language model, except where an additional agreement allows it. An admin export from your own workspace is the cleaner record.

Finish before the contract ends. Slack's customer terms say that after subscriptions end, Slack may delete all customer data in its systems unless legally prohibited.

• 1Confirm who holds the Primary Owner and Owner roles, and add an owner from the acquiring company.
• 2Check retention settings and pause any custom deletion before you start.
• 3Apply early for the fuller export if your plan supports it and you need private channels or direct messages.
• 4Run the export, then collect files separately, since Slack's export contains links to files rather than the files themselves.
• 5Hash the export and the file collection, record the date range covered, and store two copies.

How do you archive Microsoft Teams when you move to Slack?#

Archiving Microsoft Teams when you move to Slack means collecting from several Microsoft 365 locations, because Teams does not keep everything in one place. Microsoft says chat messages sit in a hidden folder in each participant's mailbox, channel messages in a hidden folder in the team's group mailbox, files shared in chats in the sharer's OneDrive, and channel files in the team's SharePoint site.

That layout shapes the archive. Use eDiscovery to export chat and channel messages, and export the SharePoint sites and OneDrive accounts that hold files. Before removing licenses from departed employees, check retention settings: Microsoft says deleting the mailbox of a user covered by an active Teams retention policy turns it into an inactive mailbox that keeps the Teams data, but without such a policy that history may not survive.

Keep the tenant, or at least the affected mailboxes and sites, until the archive is verified. Consolidating inside one Microsoft 365 tenant carries less risk than dropping a whole acquired tenant, which follows Microsoft's subscription lifecycle once cancelled.

Who owns the archive after consolidation?#

The archive belongs to the legal entity that owned the old workspace, which after an acquisition may still be the acquired subsidiary rather than the parent. That matters for legal holds, for the employee notices that covered the old platform, and for any later decision to license records.

Name a records custodian, usually in IT or legal, and write down the access rule: who may search the archive, for what purposes and with whose approval. Store the archive read-only with an index of channels, date ranges and hashes so anyone can confirm later that nothing changed.

What else belongs in the archive besides messages?#

Besides messages, the archive should hold the context that makes messages readable later: the member list with display names and roles, channel names and purposes, and the files and links people shared. Without the member list, an export full of user IDs is hard to interpret and harder to search.

Write a short archive note at cutover. It saves the records custodian from reverse-engineering the export when a hold, an audit or a licensing question arrives long after the IT director who ran the export has moved on.

• 1Member and guest lists with roles, plus join and leave dates where available.
• 2Channel list with names, purposes, privacy status and archive status.
• 3Files shared in conversations, collected separately and matched to their messages.
• 4Integration and workflow settings, kept for reference when rebuilding them.
• 5Retention settings and any legal holds in force at cutover.
• 6The export method, the date range covered and any known gaps.

Illustrative example: an engineering firm folds Slack into Teams#

Illustrative: a fictional structural engineering firm is acquired by a larger design group that runs on Microsoft 365. The acquired firm used Slack for years, with a channel per project, RFI channels for active jobs and a long-running channel where principals reviewed difficult submittals.

The IT director migrates active project channels into Teams and archives everything else. Because the firm is on a Business+ plan, the owners apply for the full export to capture private channels, then collect linked files from Slack and from project folders on the file share. The export is hashed, indexed by project number and handed to the group's records team.

Later, group leadership asks whether the archived design review history could support a data license. Because the archive is complete and owned by the acquired entity, counsel can review client contract terms project by project, and client deliverables are carved out before any fit check.

How SourceX treats a retired chat archive#

SourceX treats a retired chat archive as one possible record family, assessed with metadata first: platform, date range, channel types and which teams used it. Under the SourceX five-step transaction, the Rights step covers employee notices, customer confidentiality and the entity that owns the archive before any Preparation work removes personal and confidential details.

Chat history alone is rarely the strongest package. It tends to rank higher when it links to tickets, projects or code reviews, which is one more reason to index the archive by project or customer rather than keep it as one undifferentiated export.