Moving from SysCloud Backup for Slack to SlackVault
SysCloud's exports are CSV and JSON in its own layout, which SlackVault's importer doesn't read. So this is a fresh start with your old exports kept beside it.
The steps
- Export what you want to keep from SysCloud, and store those files somewhere safe.
- 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 copies what Slack's API returns for your plan today, which may be less than SysCloud holds. Keep that in mind before ending the contract.
Last checked November 7, 2026. Check SysCloud Backup for Slack for yourself. SlackVault is not affiliated with or endorsed by Slack.
Which one suits you
Choose SysCloud if you have at least 100 seats and want unlimited retention, point-in-time snapshots and restore into Slack handled by a vendor.
Choose SlackVault if you are a small team well under 100 people and want the archive for free in your own Firebase project rather than a per-license contract.
Prices
| Plan | Price | Terms as listed | Source |
|---|---|---|---|
| Slack backup | $36 / year | per license, yearly plan ($48 list, 25% discount with yearly); minimum 100 licenses to move from trial to paid | Their page |
Side by side
| What you need | SlackVault | SysCloud Backup for Slack |
|---|---|---|
| Saves public channel messages | Yes | Yes Their page |
| Saves private channel messages | Yes | Not stated on the pages we checked |
| Saves direct messages and group DMs | Yes | Yes: export of direct messages in JSON Their page |
| Saves thread replies | Yes: A thread that fails to save is skipped, not retried | Yes Their page |
| Saves shared files | Yes: File details always; copies only at a public link on our storage, when switched on | Yes: files in their original format 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 | Not stated on the pages we checked |
| 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: CSV 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 | Yes 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.