Export Your Data

Converge Team

• Updated March 12, 2026

Learn how to export your customer data, conversation history, and contacts from Dixa before migrating to a new platform.

How to Export Your Data from Dixa

Dixa provides two primary export paths: a dedicated Exports API for bulk conversation and message data, and the Dixa API for per-customer data portability. There is no one-click "download everything" button — you'll use API endpoints to pull your data programmatically.

Export Conversations and Messages (Exports API)

Dixa's Exports API lives at exports.dixa.io/v1/ and offers two endpoints: /v1/conversation_export for conversations and /v1/message_export for messages. You can query by time range (Unix timestamp or yyyy-mm-dd format) or by a list of conversation IDs. Each query can span a maximum of 31 days — for larger date ranges, split into monthly batches. Rate limits are 3 requests per minute for messages and 10 per minute for conversations. Both endpoints return streamed JSON arrays. Generate an API token in Settings → Integrations → API token and authenticate with bearer <token>. The Exports API includes all fields available in Dixa's CSV export, plus structured JSON. Note that internal notes are not included in the message export — they appear under conversation_wrapup_notes in the conversations endpoint.

Export Customer Data (Dixa API)

For per-customer data portability (useful for GDPR requests), use the Dixa API at dev.dixa.io/v1/. First, find the customer by email: GET /v1/endusers?email=<address>. Then retrieve their conversations: GET /v1/endusers/<user_id>/conversations (paginated — follow meta.next until null). For each conversation, get messages with GET /v1/conversations/<csid>/messages and internal notes with GET /v1/conversations/<csid>/notes. File attachments and call recordings are linked within message attributes. The Dixa API has a rate limit of 10 requests per second with a daily quota of 864,000 requests.

Document Your Flows and Automations

Dixa's Flow Builder configurations, automations, queue structures, and macros (Ultimate plan and above) cannot be exported via API. Screenshot or manually document each flow's routing logic, IVR menus, business hours rules, and automation triggers. If you're using Dixa's knowledge base articles, copy or export them separately — there's no bulk knowledge export function. Save your email signatures, quick response templates, and tag structures as well.

Contact and Company Data

Dixa stores contacts with custom attributes, company associations, and conversation histories. Use the Dixa API's /v1/endusers endpoint to retrieve contact records. Contacts include names, email addresses, phone numbers, and any custom contact attributes you've configured. Company records can be accessed through the contacts they're associated with. Export these before canceling your subscription — API access requires an active account.

Tip: Both the Integrations API token and the Dixa API token work for the Exports API. Generate your token before starting the export process, and plan for batched requests given the rate limits. For large organizations with years of conversation history, budget several hours for the full export.