What happens to your Slack history when you downgrade to the free plan?

Does downgrading to the free plan delete Slack history?#

Downgrading Slack to the free plan hides most history at once and deletes the oldest part of it. As of October 2026, Slack's help center says free workspaces can view and search messages and files from the last 90 days; older content is hidden, and messages and files more than one year old are permanently deleted.

The deletion rule is recent. Slack states that starting August 26, 2024, customer data such as messages and file history older than one year may be deleted on a rolling basis from free workspaces. Older advice online, written before that date, often says an upgrade brings everything back; for content past the one-year mark, that is no longer a safe assumption.

For a COO the practical rule follows directly. Treat the last day of the paid plan as the last safe day to capture full history, and assume that anything more than a year old will not be recoverable after the downgrade, even if you upgrade again later. Slack can change these limits, so read its current help pages on the day you decide and save a dated copy.

What changes on the day the plan drops#

On the day a workspace drops to the free plan, history access is only one of several changes. Export options narrow, retention follows the free plan's limits rather than your custom settings, and some integrations may stop, which can cut the links between Slack threads and Jira or GitHub records.

The table compares the paid starting point with the free plan, based on Slack's help center as of October 2026. Confirm each row against your own plan before acting.

A pre-downgrade export checklist#

A pre-downgrade export checklist protects the history you cannot rebuild once the plan changes. Work through it in order, because several steps depend on admin rights and export options that end with the paid plan.

The goal is a verified archive with a named owner, not a zip file sitting in someone's downloads folder.

• 1Confirm who holds owner or admin rights and can run exports before anything changes.
• 2Save dated copies of Slack's current free plan, retention and export help pages.
• 3Ask counsel whether any legal hold, audit or retention duty covers Slack content.
• 4On Business+ or Enterprise, apply for and run the export that includes private channels and direct messages, if counsel agrees they should be preserved.
• 5Run a public channel export and record the date range it covers.
• 6Download the files you need from key channels, because the export holds links to files rather than the files themselves.
• 7Open the export and check the oldest and newest messages in key channels against what Slack shows.
• 8Capture integration context: bot posts with Jira keys, GitHub links, workflow definitions and channel descriptions.
• 9Store the archive in company-controlled encrypted storage with an owner, an access list and a retention decision, and only then change billing.

What a downgrade puts at risk for a software company#

A downgrade puts at risk the oldest and often most useful part of a software company's Slack: the years of discussion behind its current product. Those threads usually date from before the last reorganization or migration, which is exactly the history the one-year deletion rule reaches first.

Jira and GitHub keep the outcome of that work, such as the issue, the fix and the merged pull request, but rarely the argument that led to it. Losing the Slack side does not break day-to-day work, so the cost stays invisible until someone needs to explain an old design choice, answer an audit question or assess the company's records for a data inventory.

Cheaper options than a full downgrade#

Cheaper options than a full downgrade exist when the real goal is a lower Slack bill rather than leaving Slack. Seat cleanup, a lower paid tier or a short overlap while the archive is verified can cut cost without putting older history at risk.

Check what each option gives up. Moving from Business+ to a lower paid tier keeps your history but removes the export of private channels and direct messages, so take that export first if you might need it.

• 1Deactivate accounts of former employees and contractors, after checking how your plan bills inactive members.
• 2Move to a lower paid tier if it keeps the history and export options you need.
• 3Combine duplicate workspaces left over from acquisitions before choosing a plan.
• 4Keep the paid plan only until the export is complete and verified, then downgrade.
• 5If you are leaving Slack entirely, archive first and treat the downgrade as the final step, not the first.

Illustrative: a scheduling software company cuts costs after a layoff#

Illustrative: a fictional appointment scheduling software company on Slack Business+ reduced headcount and asked finance to cut every subscription it could. The proposal was to drop Slack to the free plan at the next billing date, since the remaining team mostly used a few active channels.

The COO checked Slack's help pages first and saw what the free plan would mean: only 90 days of visible history, deletion of anything over a year old and no export of private channels. The company's private incident channel and its engineering-support escalation channel held six years of diagnosis threads linked to Jira issues.

The COO applied for the full export while still on Business+, ran it with counsel's agreement, downloaded the files attached in the incident channel and checked that each key channel reached back to its first message. The archive went to encrypted company storage with a named owner, and only then did finance downgrade the workspace.

How SourceX treats an exported Slack archive#

SourceX can still assess Slack history after a workspace downgrades, provided the company exported it first and holds the archive itself. An assessment starts from a description of the archive, such as the channel groups it covers, the years they span and the systems they link to, rather than from the messages themselves.

Provenance matters more for an archive than for a live workspace, so the SourceX Evidence Packet notes when and how the export was taken, by whom, and what it is known to omit. The remaining steps of the SourceX five-step transaction, Rights, Preparation, Approval and Delivery, then run as they would for any other record set, with the company approving each one.