How to Export Data from Groove

How do you export data from Groove?

Account Owners and Admins export data from Groove at SettingsCompanyMoreExports, then click Request Export in the top-right corner. Groove returns a GZIP-compressed JSON archive of your conversations — there is no CSV option. We re-checked this click path against Groove's own export documentation on 27 August 2026 and it is unchanged (help.groovehq.com).

Exports run on request, never on a schedule. Groove processes them in a FIFO queue that is shared across all Groove customers, so your wait depends on your own conversation volume and on how many other accounts happen to be exporting at the same time. Small accounts finish in minutes; Groove's documentation warns that large exports can take up to 72 hours.

You can only have one export request outstanding, and this is the part that costs people a day. Groove is explicit that additional requests submitted while one is queued are simply not processed — they do not stack up behind the first one. Submit a second request assuming it queued and you are waiting on nothing. The Exports page shows live status and updates when your request reaches the front of the queue and begins processing.

What does the Groove export file actually contain?

The Groove export is a GZIP archive of JSON matching Groove's v1 Tickets API "full" conversations format: ticket metadata, every message in each thread, and customer contact details. Groove states plainly that a .CSV export is not available.

The v1 ticket shape is public, so you can see exactly what you are getting before requesting anything. Per Groove's REST API documentation, each ticket carries number, state, created_at/updated_at, tags, assigned_group, priority, resolution_time, message_count, and links to its assignee, customer, state, and messages. Customer records carry email, name, phone number, company name, title, and location.

The practical problem is the format, not the coverage. Little you are likely to need is missing from a conversation, but nothing arrives in a shape a spreadsheet or a helpdesk importer will read either. Budget time to flatten the nested JSON — one row per message, one row per ticket, or whatever your destination expects. If your plan was to open the export in Excel and eyeball it, that is not a step, it is a small scripting job, and it is worth assigning to someone before the file lands.

What does the Groove conversation export leave out?

The conversation export covers conversations only — Knowledge Base articles, Instant Replies, and Rules are not in the archive. Two of those three can still be exported, but by emailing Groove support rather than using the Exports page, and Groove sends them as CSV.

Can you export Groove conversations through the API instead?

Yes, but only through the deprecated v1 REST API. Groove's GraphQL v2 API carries a warning that the Inbox and Knowledge Base APIs are still being built and points developers back to REST — so the modern-sounding option cannot read your conversations today (checked 27 August 2026).

This catches people out because every REST documentation page opens with a banner saying the REST API is no longer in active development and to use GraphQL instead. Both statements are true at once: REST is deprecated, and GraphQL is the one of the two that cannot yet reach your inbox. Following the banner's advice at face value sends you down a path that dead-ends.

That leaves GET https://api.groovehq.com/v1/tickets as the working programmatic pull, authenticated with an admin access token from the API section of account settings and paginated at a maximum of 50 records per page. It returns the same ticket shape the bulk export uses, so the API buys you incremental or filtered extraction — by assignee, customer, state, or folder — rather than richer data. If you want everything once, the Exports page is less work.

What happens to your Groove data after you cancel?

It is deleted. Groove's cancellation documentation states that once the account is closed your data is removed and returning means starting a fresh account. Export before you cancel — there is no recovering it afterwards.

There is a window, and it is generous enough if you use it. Cancelling leaves the account open through the end of your current billing period, and you keep access to conversations, Knowledge Base articles, and invoices until it closes — unless you specifically ask for immediate closure, which Groove also offers. Do not lean on that window: the export queue can take up to 72 hours, and you cannot request an export from an account that has already shut.

Groove also offers a data retention plan on request, holding your data past cancellation until you need it again. It is not automatic and it is not on any settings screen — you have to raise it in your cancellation email. Cancellation is not self-serve either: you email [email protected] rather than clicking a button, so add a support reply-time buffer to your timeline.

What should you watch out for when exporting from Groove?

Three things bite people exporting from Groove: download links that expire almost immediately, the single-request queue colliding with the 72-hour ceiling, and a JSON-only file landing on a team that expected a spreadsheet.

Where the archive lands: most platforms cannot import Groove's v1 Tickets JSON, so the realistic plan is a searchable local archive plus a clean inbox on the new tool. That is how a move to Converge works — $49/month flat rate for up to 15 agents, new conversations from day one, with the Groove export kept as historical reference. See the Groove email migration guide for redirecting your forwarding rules once the export is safely downloaded.