Pumble and SlackVault
There's no migration here. Pumble is a hosted chat you'd move your team to, and SlackVault has no import from it. If your integrations and partners are in Slack, SlackVault copies your messages out and leaves the team where it is.
Where to start
Slack app setup, then Firebase setup, then the browser extension. The first sync is covered in Syncing & your archive.
Last checked November 7, 2026. Check Pumble for yourself. SlackVault is not affiliated with or endorsed by Slack.
Which one suits you
Choose Pumble if you would rather switch to a hosted chat whose free plan keeps unlimited history for unlimited users, with nothing to run yourself.
Choose SlackVault if your team's integrations, habits and partners are in Slack and the goal is to keep that history safe, not to move everyone to another app.
Prices
| Plan | Price | Terms as listed | Source |
|---|---|---|---|
| Free | $0 / month | unlimited users, unlimited chat history, 10 GB total file storage, free forever | Their page |
| Pro / Business / Enterprise | No listed price | Quote only: priced per seat; the amounts are shown in a region-based currency widget that did not render in the page we read | Their page |
Side by side
| What you need | SlackVault | Pumble |
|---|---|---|
| Saves public channel messages | Yes | Not stated on the pages we checked |
| Saves private channel messages | Yes | Not stated on the pages we checked |
| Saves direct messages and group DMs | Yes | Not stated on the pages we checked |
| 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 | Partly: 10 GB total on Free; 10, 20 or 100 GB per seat on paid plans 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 | Not stated on the pages we checked |
| Search across the saved history | Yes: The most recent page of messages, up to 50 per query | Partly: files can be searched later via the File browser Their page |
| Export to open file formats | Yes: JSON, CSV, HTML and Markdown | Not stated on the pages we checked |
| 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.