Wind-downs and transitions
How to export a Slack workspace before you shut down the company
By SourceX Editorial · Updated
Short answer
To export a Slack workspace before shutting down, run the export while the paid plan and owner accounts are still active, confirm which conversations your plan's export covers, get any approval needed for private channels and direct messages, and download important files separately. Cancelling or downgrading first can limit what history remains visible and exportable.
Key takeaways
- Export before you cancel or downgrade, while owner accounts and the paid plan are still active.
- Export scope depends on the plan and export type; private channels and direct messages often need extra steps.
- Exports may reference files by link, so download the files you need before the workspace closes.
- Verify the export channel by channel against the live workspace before anything is deleted.
- Exporting direct messages raises privacy questions that counsel should settle first.
What a Slack export includes, by export type#
A Slack export's contents depend on the workspace plan and the export types Slack makes available to it, so the first job is to confirm what yours includes. Slack's help center describes the current options by plan; check it before planning around any assumption.
Plans and features change. Treat the table as a list of questions to answer for your own workspace, not as a statement of what your plan includes today.
| Export type | Who usually runs it | What it typically covers | What to confirm first |
|---|---|---|---|
| Standard workspace export | Workspace owners and admins | Messages in public channels, with links to files | Date range options and whether file contents are included |
| Export of all conversations | Owners on eligible plans, sometimes after an approval step with Slack | Public and private channels and direct messages | Plan eligibility, the approval process and the legal basis for including private content |
| Discovery and compliance exports | Org owners on enterprise plans, often through approved tools | Message and file archives for legal and compliance use | Whether a tool is already set up and what it has retained |
| Third-party backup or archiving apps | Admins, through an installed app | Varies with the tool and the permissions granted | Which scopes the app holds and where it stores copies |
Before you start: access, plan status and scope#
Starting a Slack export safely means confirming owner access, keeping the plan active and agreeing the scope with counsel before anyone clicks export. Each item below prevents a specific failure, such as losing the only owner account or exporting less history than you expected.
Assign one person to run the export and a second to check it. In a small wind-down team that is often the last engineer plus the founder, and writing down who did what becomes part of the custody record a buyer or a court may later ask to see.
- Confirm the primary owner account works and add a second owner from the wind-down team.
- Keep the paid plan active until exports are verified; cancelling or downgrading can reduce what history is visible or exportable.
- Check for a legal hold; if one applies, counsel decides how Slack data is preserved.
- Decide with counsel whether private channels and direct messages are in scope, and record why.
- Review retention settings and pause any rule that deletes older messages or files.
- Arrange encrypted, company-controlled storage to receive the export.
Running the export#
Running the export happens from the workspace's administration settings, in the section for importing and exporting data. Menu names change between versions, so follow Slack's current help article for your plan rather than an old screenshot.
Large or long-lived workspaces take time to export. Start early in the wind-down, not at the last minute before the renewal date.
- Open the import and export area of the workspace settings as an owner.
- Choose the export type and the date range, usually the entire history.
- Start the export; Slack typically notifies the owner when the archive is ready.
- Download the archive promptly to encrypted storage, since download links may expire.
- Repeat for every workspace the company ran; on an enterprise organization, confirm whether the export covers the whole organization or one workspace at a time.
What an export may leave out#
A Slack export may leave out content that teams assume is included, so list the gaps before the workspace closes. The one that matters most is often files: exports often contain links to files hosted by Slack rather than the files themselves, and those links can stop working once the workspace is deleted.
Also check canvases, lists, huddle notes and recordings, clips, workflow definitions, app and bot configurations, user profile fields and Slack Connect channels shared with other organizations. Some of these export separately, some only through APIs and some not at all. Capture what you need by other means, such as downloading canvases or documenting workflows, while access remains.
How to verify the export#
Verifying a Slack export means comparing the archive with the live workspace channel by channel before anything is deleted. Exports are usually folders of structured message files organized by channel and date, with separate files listing users and channels, which makes them straightforward to check with a short script or a spreadsheet.
- Compare the channel list in the archive with the workspace's channel directory, including archived channels.
- Check the earliest and latest dates for the busiest channels.
- Open several long threads and confirm that replies and edits came through.
- Confirm the user list maps message authors to names for internal reference.
- Test a sample of file links and download the files that matter.
After the export: custody, privacy and the licensing question#
After the export, the archive needs a custodian, an access log and a retention decision, because it holds years of company and personal communications. Store it encrypted, restrict access to the wind-down team and record every access.
Keep the original export unaltered and do any review or redaction on a working copy, so the original can later show where the records came from. Record the export date, the export type, who ran it and a checksum of the archive file. Whether any channels could be licensed, and whether former employees need notice, are separate decisions for counsel and the board.
Illustrative: an IT lead closes a logistics software company's workspace#
Illustrative: a fictional logistics software company with more than fifty staff is shutting down, and its remaining IT lead must close Slack before the renewal date. Finance had planned to cancel the plan early to save money.
The IT lead keeps the plan active, adds the CEO as a second owner and confirms with counsel that public channels and selected private engineering channels are in scope, while direct messages are not. The plan supports the needed export after an approval step, which the owner completes, and a standard export runs first as a backup.
Verification shows that file links will break after deletion, so the team downloads design documents and postmortems referenced in the incident channel and exports canvases one by one. Only after the CEO signs the custody record is the plan cancelled and workspace deletion requested.
How SourceX fits after the export#
SourceX fits after the export, at the assessment stage. A metadata fit check covering channel names, date ranges and linked systems tells the company whether any part of the archive is worth preparing, and no messages are shared during that assessment. Any package that proceeds follows the SourceX five-step transaction and is documented in a SourceX Evidence Packet, with the company keeping ownership.
Frequently asked questions
What happens to Slack data after we cancel?
It depends on the plan and Slack's terms at the time. Cancelling a paid plan may move the workspace to a free plan with less visible history, and deleting the workspace removes it. Check Slack's current documentation and export everything you need first.
Can we export direct messages without telling employees?
That is a legal question as much as a technical one. Whether notice or approval is needed depends on employee policies, privacy notices and which laws may apply. Settle it with counsel before the export, and record the decision and its basis.
Can a regular member export the workspace?
Generally no. Workspace-wide exports are limited to owners and, for some export types, admins. Members can usually save individual messages or files they can see, which is no substitute for a full export, so keep an active owner on the wind-down team.
Should Slack Connect channels be exported?
Your side of a shared channel may appear in your export, but the content includes another company's messages, which may be covered by its own confidentiality terms. Keep them for records purposes if needed, and treat them as excluded from any license unless counsel clears them.
How long should the company keep the Slack export?
Set the period by record type in a retention schedule reviewed by counsel. Some messages support tax, employment or contract records and must be kept; others carry personal information that should not be held longer than needed. A legal hold, if one applies, overrides the schedule until it is lifted.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.