Export Your Data

Converge Team

• Updated March 12, 2026

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

How to Export Your Data from Deskpro

Deskpro does not offer a one-click bulk data export. Ticket data is exported through the Stat Builder using SQL-like queries, with a limit of approximately 2,500 tickets per query. For larger datasets, you need to iterate with WHERE clauses or use the REST API.

Export Tickets via Stat Builder

Go to Reports > Stat Builder and run the query SELECT tickets.* FROM tickets. This exports ticket data (ID, subject, status, assignee, timestamps, custom fields) in CSV or PDF format. The output is capped at roughly 2,500 tickets per query. For larger volumes, add WHERE clauses like WHERE tickets.id >= '1' AND tickets.id <= '2500', then repeat for the next range. If you have many custom ticket fields (more than about 55), the wildcard query may fail — specify fields individually instead, e.g., SELECT tickets.id, tickets.subject.

Export Ticket Lists as CSV

Deskpro also allows you to download a ticket list as CSV from the ticket list view using the CSV icon. This exports the currently visible columns (Ticket ID, Subject, User, Department, Status, Agent, custom fields) for the tickets in your current filter or queue. This is useful for quick exports but doesn't include ticket message content or attachments.

Export Users and Organizations

User and organization data can also be exported through the Stat Builder with queries targeting the users and organizations tables. Alternatively, use the Deskpro REST API endpoints — /api/v2/people for users and /api/v2/organizations — to retrieve complete CRM data including custom fields that may be excluded from Stat Builder exports.

API Export for Large Datasets

If your ticket volume exceeds what the Stat Builder can handle, you'll need the Deskpro REST API (documented at deskpro.com/developers/api-docs/v2). Use the /api/v2/tickets endpoint with pagination to retrieve tickets including message content. This requires programming skills or a developer on your team. The API is available on all plans.

What You Cannot Export Natively

Trigger rules, escalation configurations, macro definitions, SLA policies, chatflow definitions, and Help Center templates are not included in any export method. Document these manually — screenshot your trigger conditions and actions, copy macro text content, and note SLA thresholds and escalation rules before canceling your account.

Tip: If you use Deskpro's 150+ built-in reports or custom dashboards, export or screenshot any reports you want to reference later — these are not included in ticket data exports and will be lost when your account is closed.