# Build a usable Slack archive before downgrading

> Check export permissions, preserve attachments and have a colleague retrieve an old decision before reducing Slack access.

Updated 2026-10-21 · https://onelesstool.com/guides/slack-archive-before-downgrade

**Reduce Slack access only after an ordinary colleague can retrieve an important old decision, understand its context and open its supporting files from the proposed archive.** A downloaded ZIP is an input to that archive, not proof it works. Keep the necessary paid access while missing records, permissions or file dependencies remain unresolved.

This guide is for the person responsible for preserving records before a downgrade. Choosing the team's next chat service is a separate decision. The retrieval exercise below is a proposed user-run test; we have not exported a workspace or tested your history.

## Work backwards from a question people still ask

Choose a real question such as “Why did we reject the first supplier proposal?” Select a decision older than ninety days, preferably from a finished project, with a thread and an attachment. Record the correct answer while the original conversation is available. Include the final correction if the team changed its mind later.

Build a retrieval inventory before requesting exports. One row should describe a useful body of records, not merely a channel name.

| Inventory field | What to record |
|---|---|
| Business question | The decision or instruction somebody must recover |
| Source | Workspace, channel or conversation identifier, date range and message reference |
| Conversation category | Public, private, DM or external collaboration; archived or active |
| Context | Author, timestamps, parent message, replies and later correction |
| Supporting assets | Uploaded files, externally hosted documents, canvases or other required material |
| Destination and access | Archive location, intended readers, excluded readers and responsible owner |
| Retrieval result | Tester, date, missing material and pass/fail reason |

Separate confidential records from material everyone may read. Being able to export something does not mean the whole team should receive it. Have the record owner approve the intended audience and preservation scope.

## Establish what your account can export

Slack documents these standard export boundaries. [Slack's export options and roles](https://slack.com/help/articles/201658943-Export-your-workspace-data).

| Current plan | Documented route |
|---|---|
| Free or Pro | Workspace Owners and Admins can export public-channel messages and file links in JSON |
| Business+ | The same public-channel export; Workspace Owners can apply for broader exports including private channels and DMs for legal and regulatory compliance |
| Enterprise | Org Owners request self-service export tools through Slack Support; approved tools include broader conversation exports and custom scopes |

Approval is a dependency, not an automatic consequence of paying. Ask the responsible owner to confirm the enabled export type before promising private-message coverage. Do not change private channels to public to work around a missing export permission.

Slack also limits Free exports to file links from the last ninety days. Plan the file-preservation work before reducing access. [Free export restriction](https://slack.com/help/articles/201658943-Export-your-workspace-data).

Record the export's selected dates and actual contents against the inventory. An absent conversation might reflect the scope, dates or retention policy; mark it unresolved until someone establishes why. Keep the original package unchanged in restricted storage and do reading or conversion work on a copy.

## Preserve files separately from their references

Slack's JSON exports contain links back to workspace files, not the files themselves. Its reading guide also describes conversation folders organised by date and reference files that map users and channels to identifiers. [How Slack exports are structured](https://slack.com/help/articles/220556107-How-to-read-Slack-data-exports).

For each required attachment, record whether you have the actual file or only a link. An authorised owner should preserve a copy where needed, open it independently and connect it to the relevant decision in the archive index. Keep filenames, dates and source references so two similarly named proposals are distinguishable. A successful link click while signed in as the exporter is not a sufficient test.

For externally hosted documents, identify the service and account that control access. Decide whether the living document is enough or an approved dated copy is needed to explain the historical decision. Keep canvas and other content needs on the inventory instead of assuming the message export covers every asset.

For a small collection, a documented index and readable decision packets may suffice. A large archive may need a maintained reader or search service. Test either choice with real retrieval tasks and confirm its access controls before loading sensitive exports. A manually written decision summary should link to preserved evidence; label it as a summary, not a complete conversation export.

## Free Slack is not indefinite storage

Slack Free exposes the most recent ninety days of message and file history. Its downgrade guidance says workspace data older than a year is deleted. [Free-plan history limitations](https://slack.com/help/articles/27204752526611-Feature-limitations-on-the-free-version-of-Slack).

The retention controls also allow a ninety-day deletion setting, and retention deletions are permanent. Pinned or saved material remains subject to retention. Check the actual workspace and conversation rules rather than assuming every record has a year remaining. [Slack retention settings](https://slack.com/help/articles/203457187-Customize-data-retention-in-Slack).

Record the earliest relevant deletion deadline in the inventory. Re-upgrading later must not be your recovery plan for permanently deleted material. If preservation cannot finish before the access change, retain the current arrangement and revise the schedule.

## If the archive destination is Teams

Microsoft's importer requires archived Slack channels to be unarchived before export for migration. It excludes DMs, group chats and Slack Connect channels. It also depends on online access to the source workspace and Azure Blob Storage. [Microsoft's migration prerequisites and limitations](https://learn.microsoft.com/en-us/microsoftteams/slack-to-teams-migration-tool).

Ask the authorised migration owner to prepare the relevant archived channels and record their original state. Keep excluded categories on a separate preservation track. Do not conclude that everything was retained because an import job completed. Include an originally archived project in the retrieval sample and budget the migration dependencies separately.

## Make somebody else retrieve the answer

Give a non-admin colleague the business question and the normal archive entry point. Do not give them your login or coach them through JSON filenames. Agree a reasonable retrieval time in advance, based on how urgently this information is normally needed.

Pass only if the colleague can find the decision, identify who made it and when, read the relevant replies and open the correct supporting file. Check that they see the later correction and cannot access a deliberately excluded private record. Repeat with a second record type that matters to your team.

Stop the downgrade if a required answer is missing, an attachment depends on the exporter's Slack session, the reader exposes restricted material or the backup maintainer cannot operate it. Keeping Slack is reasonable when frequent historical work still relies on its native navigation and the archive adds unacceptable friction.

## Close the gap between export and downgrade

Name a cutoff for new decisions, capture changes made during the archive work and repeat the failed tests. Preserve the inventory, export dates, access instructions and unresolved exceptions together. Assign an owner to review access and test recovery from the backup periodically.

Keep the original workspace usable during the pilot. If the archive fails, return retrieval work to Slack while fixing it; do not delete original records to force completion. Rollback means a planned return to a working source, not an assurance that every export can be re-imported.

Compare the same billing period: **current Slack charge − remaining Slack charge − incremental archive and replacement costs**. Include added storage, search or access subscriptions once. Separate one-time preparation from ongoing archive maintenance, and use the actual renewal date for cash savings. Review the rest of the stack in the [subscription audit](/audit) only after the archive has earned its place as a usable replacement.