Moving from Backupery for Slack to SlackVault
Your Backupery HTML exports stay readable on their own, so there's nothing to convert for reading. What changes is where new messages go: into your Firebase project, from a browser extension.
The steps
- 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, then keep your last Backupery export as your record of anything older than Slack's API still returns.
- Backupery's pages say its JSON export is compatible with Slack's import tools. If your export keeps Slack's layout, with
users.json,channels.jsonand a folder per channel, try the merge below. We haven't tested it on a Backupery file, so check the counts on the Import page before relying on it.
SlackVault's Import page reads one JSON file, not a ZIP, so a Slack export needs merging first. Unzip it and run this
inside the folder that holds users.json and channels.json, with jq installed:
jq -n --slurpfile users users.json --slurpfile channels channels.json \
--slurpfile msgs <(for c in $(jq -r '.[] | "\(.id):\(.name)"' channels.json); do
jq -s --arg id "${c%%:*}" '{($id): add}' "${c#*:}"/*.json
done) \
'{users: $users[0], channels: $channels[0], messages: ($msgs | add)}' > slackvault-import.json
Then upload slackvault-import.json on the Import page of the web app, as described in
Search & export. Merge mode adds new records and updates
existing ones. Private channels and DMs need their own export files, which this command doesn't cover.
Last checked November 7, 2026. Check Backupery for Slack for yourself. SlackVault is not affiliated with or endorsed by Slack.
Which one suits you
Choose Backupery for Slack if you want a paid, mature desktop or cloud exporter with scheduled runs, selective exports per user and HTML output you can open offline.
Choose SlackVault if you would rather pay nothing and keep the live archive in a Firebase project you own, with search and export built into a web app instead of files on one machine.
Prices
| Plan | Price | Terms as listed | Source |
|---|---|---|---|
| Standard and Pro licenses | No listed price | Quote only: the pricing pages state that taxes may be added, but the price table itself did not render in the page we read | Their page |
Side by side
| What you need | SlackVault | Backupery for Slack |
|---|---|---|
| Saves public channel messages | Yes | Yes Their page |
| Saves private channel messages | Yes | Yes Their page |
| Saves direct messages and group DMs | Yes | Yes Their page |
| Saves thread replies | Yes: A thread that fails to save is skipped, not retried | Yes: release notes cover thread presentation and pinned items from threads Their page |
| 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 | Yes Their page |
| Copy lives in storage you control | Partly: Messages in your Firebase project; file copies are not in your storage | Partly: desktop version writes to your disk; the cloud version's main storage is Backblaze B2 Their page |
| Search across the saved history | Yes: The most recent page of messages, up to 50 per query | Not stated on the pages we checked |
| Export to open file formats | Yes: JSON, CSV, HTML and Markdown | Yes: self-contained HTML and Slack-compatible JSON Their page |
| Works without workspace admin rights | Partly: No admin scopes, though a workspace can require approval for new apps | Yes: Synthetic mode in the desktop version Their page |
| Puts records back into Slack | No: No way yet to send records back into Slack | Partly: JSON export is compatible with Slack's import tools; re-import is done with Slack's tool Their page |
| Free plan with no time limit | Yes | Not stated on the pages we checked |
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.