Exporting your data

You can request a full export of your workspace data at any time. Useful for backups, migrations to another tool, regulatory compliance, or peace of mind.

How to request

1. Open Settings → Danger zone. 2. Click Request data export. This opens a pre-filled email to hello@ochrehq.com with your workspace name. 3. Send the email.

We queue the export, run it, and email you a signed download link when it is ready.

The export is currently a concierge flow rather than a one-click in-app button. Both flows produce the same artifact; concierge lets us confirm scope and answer any questions before kicking off a long-running job.

Turnaround

For most workspaces, exports complete within one business day. Larger workspaces (millions of messages, thousands of customers) take longer; we will email you with a more specific estimate if it is going to take more than 48 hours.

The download link is valid for 7 days. After that you can request another export.

Who can request

Owner or admin. The export is delivered to the requester's account email.

What is included

The export is a single ZIP archive containing JSON files, one per entity type. Schemas are documented at the top of each file.

| File | Contents | |---|---| | conversations.json | Every conversation with status, timestamps, assignee, tags | | messages.json | Every customer-visible message and internal note | | customers.json | Customer records and custom fields | | articles.json | All KB articles, including drafts | | categories.json | KB categories and ordering | | routing_rules.json | Routing rule definitions | | team.json | Member list with roles (no passwords or tokens) | | attachments/ | File attachments under 50MB; larger files are referenced by URL |

JSON is line-delimited where appropriate so you can stream-process large files without loading them entirely into memory.

What is not included

• Stripe billing data: held by Stripe, not us. Download invoices and receipts from the stripe-portal directly. - BYOK API keys: kept in our secret store and never exported in plaintext. We export the key name and last-4 only. - OAuth tokens for connected integrations: not exported for security. You will need to reconnect integrations in any new tool.

Format details

Dates are ISO-8601 with timezone (e.g. 2026-05-06T14:32:01Z). UUIDs are used throughout for cross-references — a row in messages.json references its conversation by conversation_id. Enums are stable strings, not integers, so status: "open", not status: 2.

Common questions

Can I get the export as CSV instead of JSON? Not directly. The JSON is the source of truth. Convert with jq or a small script.

Are attachments lossless? Yes, full bytes are included for files under 50MB. Larger files are URLs valid for the 7-day window.

Is the export encrypted? The download link uses HTTPS and is unguessable, but the ZIP itself is not password-encrypted. Treat it as sensitive data.

Can I schedule recurring exports? Not yet. Email us if you need this.

What to do next

• Read danger-zone to see all irreversible actions in one place. - For deletion see workspace-deletion. - For Stripe records see invoices and stripe-portal.