Exporting your data
Updated 18 May 2026
Your data is yours. Two formats, no quota, no friction. The strongest reason to run an export isn't because you're leaving — it's because you might want to. Knowing the door's unlocked is what makes the room feel safe.
CSV — tasks and projects
Settings → Workspace → Export → CSV. We assemble a CSV per project:
tasks.csv— every task with its core fields (title, description, assignee, due date, status, priority, project)comments.csv— every comment, with task ID and authorprojects.csv— project metadatausers.csv— workspace members
The export runs in the background and emails you a download link when ready. Big workspaces take a minute or two.
JSON — full structured backup
Settings → Workspace → Export → JSON. Same data, JSON instead of CSV. Includes things CSV can't easily represent — task attachments (as URLs), reactions, workflow step state. Better for piping into another system.
What's included
- Tasks (all fields)
- Comments and activity
- Projects, workflows, members
- File attachments (as signed download URLs, valid for 7 days)
- User profiles for workspace members
What's not included
- Other workspaces (we only export the one you own)
- Audit log (request separately if you need it)
- Billing records (Stripe is the source of truth there)
- Cached search indexes, push tokens, internal metadata
Frequency
You can run an export as often as you like — there's no quota and no fee. Many enterprise customers schedule a monthly export as a backup.
Privacy and GDPR — what we store, what we don't.