export

Export your Snippbot data as JSON. Useful for backups, migration, GDPR data-portability requests, or feeding your own tooling.

All three subcommands can either print the JSON to stdout or write to --output.

Overview

snippbot export conversations        # Conversations + messages
snippbot export projects             # Projects + phases + tasks
snippbot export all                  # Everything, as a directory of JSON files

---

snippbot export conversations

Dump every conversation and its messages from snippbot.db.

snippbot export conversations                   # To stdout
snippbot export conversations -o conv.json      # To a file

Output shape:

{
  "conversations": [
    { "id": "c1", "title": "Project kickoff", ... }
  ],
  "messages": [
    { "id": "m1", "conversation_id": "c1", "content": "…" }
  ]
}

---

snippbot export projects

Dump every project, phase, and task from projects.db.

snippbot export projects                   # To stdout
snippbot export projects -o projects.json

Output shape: { "projects": [...], "phases": [...], "tasks": [...] }.

---

snippbot export all

Write a bundle directory with one JSON file per data domain plus a metadata file.

snippbot export all                          # Creates ./snippbot-export/
snippbot export all -o ~/backups/2026-04-16

Bundle contents:

File	Description
conversations.json	Conversations + messages
projects.json	Projects + phases + tasks
meta.json	Export timestamp + per-database schema versions

Note

export all is a snapshot, not a live link — re-run it to refresh. The bundle is safe to commit to your own version control; it contains no secrets (secrets live in a separate encrypted store; see secrets).

---

Related

• secrets export — encrypted backup of the secret store (separate file)
• reset —restore — restore full installation from a timestamped backup (different format)