Export Your Data

Export tickets via Stat Builder

Open Reports > Stat Builder and run SELECT tickets.* FROM tickets. The result downloads as CSV or PDF with ticket ID, subject, status, assignee, timestamps, and custom fields. The query is capped at roughly 2,500 tickets per run. For higher volumes, add ID ranges — WHERE tickets.id >= '1' AND tickets.id <= '2500', then repeat. If you have more than ~55 custom ticket fields, the wildcard query can fail; list fields explicitly (SELECT tickets.id, tickets.subject, tickets.status) instead.

Export a ticket list as CSV

From any ticket list view, click the CSV icon to download the visible columns (Ticket ID, Subject, User, Department, Status, Agent, custom fields) for the current filter or queue. Quick to use, but the output contains only ticket properties — no message bodies, no attachments, no internal notes. Treat it as an index, not a backup.

Export users and organizations

The Stat Builder runs the same kind of query against the users and organizations tables. For a complete dump including custom CRM fields, use the REST API endpoints /api/v2/people and /api/v2/organizations with pagination. The API output is the most reliable source for CRM data because it includes fields the Stat Builder sometimes drops.

Export full ticket conversations and attachments via API

For message bodies and attachments, you need the REST API. Hit /api/v2/tickets for the ticket list, then /api/v2/tickets/{id}/messages for the full thread and /api/v2/blobs/{id} to download each attachment as a binary blob. Deskpro stores attachments as separate blob objects keyed by ID — they are referenced from messages but not bundled into ticket payloads. The API is available on all plans; it does require a developer to write the loop and store the files.

Export Help Center articles

Knowledge base content (articles, guides, news posts, downloads) is not included in any ticket export. Pull articles from the publish admin manually or via the API endpoints under /api/v2/publish. If your Help Center is multilingual, you'll need to fetch each language version separately. Save HTML or Markdown copies before canceling — there is no public bulk article export button.

What has no export at all

Triggers, escalations, macros, snippets, SLA policies, chatflow definitions, ticket form templates, Help Center themes, and custom Stat Builder reports are configuration, not data. None of these are included in any export. Before canceling, screenshot each trigger's conditions and actions, copy macro and snippet text into a document, and record SLA thresholds. Treat this as a one-time inventory exercise; if you skip it you will rebuild from memory.

Can I export all tickets from Deskpro?

Yes, but not in a single click. The Stat Builder returns roughly 2,500 tickets per query, so a full export requires iterating with ID-range WHERE clauses or paginating the /api/v2/tickets REST endpoint. Stat Builder CSVs cover ticket properties; message bodies and attachments require the API.

Does the Deskpro export include attachments?

No. Stat Builder CSVs and ticket-list CSVs include ticket properties only — no message bodies and no attachments. To export attachments you have to call the REST API: fetch the messages for each ticket, then download each referenced blob from /api/v2/blobs/{id} as a binary file. Plan for a scripted job.

How long does a Deskpro export take?

A single Stat Builder query runs in seconds for up to about 2,500 tickets. A full archive of a busy account — iterating ID ranges, calling the API for messages, and downloading every attachment blob — can take a developer hours to a couple of days, depending on ticket volume and attachment size.

Can I migrate from Deskpro to Converge directly?

No direct ticket migration. Converge does not import Deskpro tickets; instead, you connect your messaging channels (WhatsApp, Telegram, Messenger, Instagram, Discord, Zalo, Gmail, email, widget) to Converge and run new conversations there. Keep your Deskpro export as a historical archive in your own storage. Most teams complete the channel switchover in 1–3 business days on Converge's $49/month flat rate for up to 15 agents.

Can I export Deskpro Help Center articles?

Not as a single archive. Pull articles individually from the publish admin or through the /api/v2/publish API endpoints. If you publish in multiple languages, each language version is a separate fetch. Save the HTML or Markdown into your own repository before you cancel — Deskpro does not offer a one-button knowledge base export.

Will my custom fields and tags export?

Custom ticket and user fields export through the Stat Builder and the REST API. Labels and tags export as fields on the ticket record. Field definitions (the names, types, and conditional rules you configured under Admin > Ticket Structure) do not export — only the values applied to tickets. Document the definitions manually if you plan to recreate the same data model elsewhere.