How to Export Your Data from Gorgias

Open the dropdown menu at the top left of the Gorgias helpdesk, choose Inbox, select a view from the sidebar, tick the checkboxes on the tickets you want (the header checkbox selects the current page, then you can extend the selection to the whole view), open the three dots icon and choose Export tickets. Gorgias emails a download link that stays active for 14 days, after which you regenerate the export. The feature is available on all Helpdesk plans, but only the account owner, admins and leads can run it. One export covers a maximum of 1 million tickets and a larger view is cut off at that limit rather than split into several files, so filter by date range if you are close to it. Budget roughly 1 hour per 100,000 tickets, up to about 10 hours for a full million (docs.gorgias.com, checked 9 August 2026).

It depends entirely on which export you run, and this is the fact that decides most Gorgias migration plans. The CSV export from an Inbox view does not include message text — it carries the number of agent and customer messages, but not the messages themselves. The Analytics drill-down export does: open Analytics, click a metric value to open the ticket list behind it, hit Export, and choose Export with message content rather than Export metadata only. The catch is reach. A metadata-only drill-down export goes back 2.5 years, while an export with message content is limited to the most recent 30 days of the selected period or 100,000 tickets, whichever comes first. Only public messages are included; internal notes, ticket events, Facebook wall posts and Instagram media messages are excluded (docs.gorgias.com, checked 9 August 2026).

Not through any self-serve route with the message text attached. The 30-day cap on the Analytics drill-down's message-content export is the binding limit, and the Inbox view CSV has no message bodies at all regardless of how far back it reaches. Two routes remain. The REST API returns full history through /api/tickets and /api/messages with cursor-based pagination, subject to rate limits. Or you email [email protected] with your Gorgias subdomain, the data types and the time frame you need, and request a custom export — which can include message IDs and message body text, customer notes, macros, Help Center article content, billable-ticket and revenue statistics, and the page a chat ticket started from. Both need lead time, so open them before the last week of your billing cycle rather than after.

Yes. The Gorgias REST API sits at https://{your-domain}.gorgias.com with endpoints including /api/tickets, /api/customers and /api/messages. Pagination is cursor-based (offset paging is deprecated): pass cursor, limit and order_by, then follow meta.next_cursor. The default limit is 30. Rate limits work as a leaky bucket — 80 requests per 20 seconds for OAuth2 apps and 40 per 20 seconds for API-key integrations, with Enterprise accounts getting the same counts over a 10-second window. Exceeding it returns HTTP 429 with Retry-after and X-Gorgias-Account-Api-Call-Limit headers. At 40 requests per 20 seconds and the default page size, an API-key integration moves about 3,600 tickets a minute at best, so half a million tickets is a job of well over two hours. Note that gorgias.com/pricing separately publishes a plan-level API rate limit of 2 requests per second (4 on Enterprise) — size bulk exports against the slower figure (developers.gorgias.com, checked 9 August 2026).

Your Chat widget configuration — appearance, office hours, targeting rules and custom text — has no documented export route, so record it by hand before cancelling. Two other items are common false alarms. Macros come out through a custom export from Gorgias support and through GET /api/macros. Rules come out through GET /api/rules, which returns each rule's name, priority, trigger events and its full logic as JavaScript in the code field — you can archive the definitions, you just cannot import them into a different helpdesk, so budget rebuild time rather than capture time. The gaps that catch people out sit inside the exports rather than outside them: internal notes, ticket events, Facebook wall posts, Instagram media messages and Instagram ad media messages are all excluded from message-content exports (docs.gorgias.com and developers.gorgias.com, checked 9 August 2026).

Your subscription ends at the end of the billing cycle in which the cancellation request was received, and you keep access until that date — so that period, not the day you decide to leave, is your export window. Cancel from Settings > Account > Billing & usage, click Manage on the Helpdesk card, then Cancel auto-renewal. Shopify merchants should note that uninstalling the Gorgias app from Shopify does not cancel the subscription; billing continues until you cancel in Gorgias itself. Billing questions go to [email protected]. Work backwards from the renewal date: request the custom export first because it sits in someone else's queue, start any API pull second because it runs longest, and leave the CSV and drill-down exports until last since both are self-serve and quick to repeat (docs.gorgias.com, checked 9 August 2026).