What happens to Slack history when you downgrade or cancel a paid plan?

Does downgrading Slack delete your message history?#

Downgrading Slack to the free plan does not erase message history on the day of the change, but it puts most of it out of reach and starts a deletion clock on the oldest part. Slack's help center says free workspaces can view and search messages and files from the last 90 days, and that older content is hidden.

Hidden is not the same as safe. The same Slack article says messages and files more than one year old on free workspaces are permanently deleted, and Slack states that from August 26, 2024 such content may be deleted on a rolling basis. In practice a downgrade turns months four to twelve into hidden history and anything older into history at risk of permanent loss. Slack revises these rules, so read its current article before changing billing.

The working rule is simple. History you have exported and verified is preserved; history that is merely hidden, or still sits only in the vendor's system, is not.

The three stages: paid, downgraded and deleted#

The three-row timeline below shows what changes at each stage of a Slack workspace's life, using the windows Slack publishes for the free plan. Confirm them against Slack's current help center before acting.

What else changes when the paid plan ends?#

Ending the paid plan changes more than message visibility. Features and controls tied to the plan may stop working or behave differently, and several of them matter during a wind-down.

• 1Export options: Workspace Owners and Admins on every plan can export public channel messages and file links in JSON, but exports of private channels and direct messages are offered only on Business+ and Enterprise, and owners must apply to Slack to use them.
• 2File links: Slack's export contains links to files rather than the files, and free workspaces can export file links only from the last 90 days.
• 3Retention settings: custom deletion periods set by admins are permanent once they run, so record what was configured before the plan changes.
• 4Admin controls: some security and sign-in settings depend on the paid plan.
• 5Integrations: limits on apps can break archiving tools, and the law firm Hunton reported that Slack's API terms were changed, effective May 29, 2025, to prohibit bulk exporting through the APIs and building long-term data stores, so rely on Slack's own export rather than an API-based copier.
• 6Shared channels and guests: connections with other organizations may change, which matters if customers or vendors worked in shared channels.
• 7Files: file access follows the same visible window, so attachments in older threads become unreachable too.

How a wind-down can downgrade Slack by accident#

A wind-down can downgrade Slack by accident when billing stops working before anyone has decided to change the plan. Finance teams close corporate cards, cancel bank accounts and switch off auto-renewals in bulk, and a subscription that cannot be charged may lapse to the free plan without a single owner choosing it.

The fix is to treat the Slack subscription as a dependency of the records plan, not just a line on the expense report. Decide in writing who may change the plan, and make sure that person is still on the closing team.

• 1Move billing to a card or account that will stay open until exports are verified.
• 2Name a billing contact whose email will be monitored through the wind-down, not a departing finance employee.
• 3Put the renewal date on the wind-down calendar and review it before cards or accounts close.
• 4Exclude Slack from any bulk cancellation of software subscriptions until the export is signed off.
• 5Check that the account paying for Slack is not owned by someone whose access is about to be deactivated.

Cancel, downgrade or delete: which order for a closing company?#

A closing company should export first, downgrade second and delete last, recording each step. The table summarizes when each option fits and the risk it carries.

Deletion should be approved by whoever controls the company's records, often the wind-down officer or the board, and logged with the date, the person who acted and a reference to the verified export.

Illustrative: a roofing contractor nearly loses its job threads#

Illustrative: a fictional roofing contractor is closing after the owner sells the trucks and equipment. Crews used a Slack channel for each job site, posting photos of decking, flashing details and change requests that never made it into the field service system.

To cut costs, the bookkeeper downgraded the workspace before anyone exported it. Five months later a building owner raised a warranty question about a job from the previous season, and the relevant thread sat beyond the free plan's 90-day window.

The owner upgraded again while the content still existed, ran a full export, downloaded the photos to encrypted storage and checked a sample of job channels against the live workspace. Only then was the workspace downgraded, and deletion was scheduled for after the warranty period recorded in the company's retention schedule.

Before you change billing: a short checklist#

This checklist puts every irreversible step after a verified export. It is written for one workspace; companies that ran several workspaces should repeat it for each.

• 1Make sure at least two people on the closing team hold owner-level access.
• 2Ask counsel whether a legal hold applies to any Slack content.
• 3Run the fullest export the current plan allows and save it to encrypted, company-controlled storage.
• 4Download files and canvases separately wherever the export holds only links.
• 5Rebuild a handful of threads from the export to confirm replies, authors and files are intact.
• 6Enter the archive in the company's retention schedule with a custodian and a review date.
• 7Only then downgrade, cancel or schedule deletion, and log who did it and when.

How SourceX looks at a Slack archive#

SourceX looks at a Slack archive as human-generated records of real work, which the SourceX Enterprise Data Value Framework counts toward value, together with a heavy privacy burden that reduces net value. Employee messages raise consent and notice questions that counsel assesses deal by deal, and direct messages are usually the first category excluded.

The fit check uses metadata only, such as channel types, years covered and the other systems involved. If a package proceeds, the SourceX Evidence Packet records how the archive was exported, what was removed during privacy preparation and who authorized release.