Docs / Hosting OwnBase

Taking your data out

export writes a workspace in Slack's export format: users.json, channels.json, and a folder of one JSON file per day for each channel. Tools that read Slack's exports read it, and import-slack reads it back, which is how to move a workspace's history into a new one without its accounts, apps and settings. For a full copy of a workspace to restore, use backup or Download a copy.

ownbase-server export --data ./data --to ./acme-export.zip
ownbase-server export --data ./data --to ./acme-everything.zip --everything

Without --everything it holds public channels only. --everything adds private channels (groups.json), direct messages (dms.json) and group messages (mpims.json); it is only on the command line, since whoever can run commands on the server can read the database anyway. Unlike Slack's export, the zip holds the files themselves, under files/, and each message names its own in export_path.

It holds what a profile shows, and never a password, sign-in, token or app secret. Deleted messages are left out. Polls keep their question, and a forward with no words of its own is left out. The export can run while the server is running: it reads one consistent moment of the workspace. It needs disk beside the zip for the day files while it writes, and room for the zip.

This page is made from docs/DEPLOYMENT.md.