Moving from slack-archive to SlackVault
There's no import path here. slack-archive's JSON isn't in the shape SlackVault's importer reads, and nothing needs converting: its HTML files keep working as they are.
The steps
- Keep the folder slack-archive wrote. It's your record of anything Slack's API no longer returns, and it holds the files too.
- Set up SlackVault: Slack app setup, then Firebase setup, then the browser extension. The first sync is covered in Syncing & your archive.
- Run a first sync. It starts from what Slack's API returns today, so expect overlap with your HTML archive, not a join between the two.
Last checked November 7, 2026. Check slack-archive for yourself. SlackVault is not affiliated with or endorsed by Slack.
Which one suits you
Choose slack-archive if you want one free run that leaves you plain HTML files meant to open decades from now, with incremental re-runs when you choose to do them.
Choose SlackVault if you want the copy taken every 15 minutes without a manual run, and the result searchable from a web app rather than a folder of files.
Prices
| Plan | Price | Terms as listed | Source |
|---|---|---|---|
| Open source | $0 / one time | No cloud, free | Their page |
Side by side
| What you need | SlackVault | slack-archive |
|---|---|---|
| Saves public channel messages | Yes | Yes Their page |
| Saves private channel messages | Yes | Yes Their page |
| Saves direct messages and group DMs | Yes | Yes: DMs and multi-person DMs Their page |
| Saves thread replies | Yes: A thread that fails to save is skipped, not retried | Not stated on the pages we checked |
| Saves shared files | Yes: File details always; copies only at a public link on our storage, when switched on | Yes Their page |
| Runs on its own on a schedule | Yes: Every 15 minutes, while the browser runs | Not stated on the pages we checked |
| Copy lives in storage you control | Partly: Messages in your Firebase project; file copies are not in your storage | Yes Their page |
| Search across the saved history | Yes: The most recent page of messages, up to 50 per query | Yes: basic search Their page |
| Export to open file formats | Yes: JSON, CSV, HTML and Markdown | Yes: static HTML and JSON Their page |
| Works without workspace admin rights | Partly: No admin scopes, though a workspace can require approval for new apps | Not stated on the pages we checked |
| Puts records back into Slack | No: No way yet to send records back into Slack | Not stated on the pages we checked |
| Free plan with no time limit | Yes | Yes Their page |
What SlackVault does not do
- Messages, channels, members and file records go to your own Firebase project. Supabase is not supported yet.
- Files do not go to your Google Drive or your Firebase project. When file copying is switched on in our extension build, each file uploads to our file storage with its visibility set to public: the link is hard to guess, but anyone holding it can open the file without signing in. Where no storage key is set in the build, no copy is made, and your archive keeps the file’s details and Slack’s link, which works only while Slack serves that file.
- There is no way yet to send records back into Slack.
- The sync runs in a browser extension, every 15 minutes, only while that browser is running.
- SlackVault can copy only what Slack’s API still returns, so anything older than your plan’s window is out of reach unless an earlier sync already saved it.
- If saving one thread fails, the sync logs it and moves on without retrying those replies.
- Search checks the most recent page of messages, up to 50 per query, not the whole archive.
- The extension and the Android app have no store listing yet, and the source code is in a private repository.