How to Export Tickets from LiveAgent

Exporting tickets from LiveAgent gives you a portable record of every customer conversation, which is essential when you're switching helpdesks, archiving for compliance, or analyzing support trends. This guide walks you through the two main methods — the built-in UI export and the API — so you can choose the one that fits your volume and technical comfort. You'll need admin access to LiveAgent and, for the API route, a basic understanding of REST calls and authentication tokens.

Prepare Your LiveAgent Account

Before you start, confirm you have an administrator role. Only admins can access the export functions in the configuration menu. If you're on a shared plan, ask the account owner to grant you the necessary permissions. Also decide on the date range and ticket filters you want — exporting everything at once can produce a massive file that's hard to open or import elsewhere.

Choose the Export Method

LiveAgent offers two paths: a manual CSV export from the interface, and a programmatic export via the REST API. The UI method works well for one-time exports under 10,000 tickets. The API method scales to hundreds of thousands of tickets and lets you automate recurring backups. Pick the UI if you're moving to a new helpdesk once; pick the API if you need regular extracts or want to script the migration.

Export via LiveAgent UI

1. Log in as an administrator and use the data export feature in the LiveAgent admin area (see LiveAgent's help documentation for the exact navigation).
2. Select Tickets as the data type.
3. Choose your filters — date range, departments, tags, or status — to narrow the set.
4. Pick CSV as the output format. CSV is universally readable and imports cleanly into most helpdesks.
5. Start the export and wait for the file to generate. Large exports may take several minutes; the page will show a download link when ready.
6. Download the file and verify it opens correctly in a spreadsheet tool. Check that column headers match your expectations: ticket ID, subject, requester email, status, created date, last updated, and the full conversation thread.

Why this matters: The UI export includes the conversation history in a single column, which some import tools parse poorly. If your target system expects separate rows per message, you'll need to transform the file afterward.

Export via LiveAgent API

1. Generate an API key from the LiveAgent admin area (refer to LiveAgent's API documentation for details). Copy the key immediately — you won't see it again.
2. Use the endpoint GET /tickets with query parameters for filtering: date_from, date_to, department, status, limit, and offset.
3. For large datasets, paginate using limit=1000 and increment offset until the response returns an empty array.
4. Each ticket object contains a messages array with the full thread. Decide whether to flatten messages into rows or keep the nested JSON structure.
5. Write the results to CSV or JSONL (one JSON object per line) for easier downstream processing.
6. Handle rate limits: LiveAgent returns 429 Too Many Requests if you exceed the threshold. Implement exponential backoff and respect the Retry-After header.

Why this matters: The API gives you granular control — you can export only open tickets, only tickets with a specific tag, or only the last message per ticket. It also avoids the UI's file-size ceiling.

Verify the Export

Open a sample of rows and confirm:

• Ticket IDs are unique and sequential.
• Timestamps use a consistent timezone (LiveAgent exports in UTC).
• Email addresses are intact — no truncation or encoding issues.
• Conversation threads are complete, including internal notes if you exported them.

If you spot missing data, re-run with broader filters or check whether the tickets were deleted or merged in LiveAgent.

Common Mistakes to Avoid

• Exporting without filters on a large account: the resulting file may exceed spreadsheet limits (1,048,576 rows in Excel) and crash your import tool.
• Assuming the CSV is import-ready: many helpdesks expect a specific column order or separate message rows. Plan a transformation step.
• Ignoring internal notes: they're excluded by default in the UI export. Enable the option if your team relies on them for context.
• Forgetting attachments: neither the UI nor the API export includes file attachments. You'll need a separate script to download them via the /attachments endpoint.
• Using an expired API key: keys don't rotate automatically, but a revoked key will break scheduled exports. Store it securely and monitor for 401 errors.

After the Export

If you're migrating to a new helpdesk, map your LiveAgent statuses (New, Answered, Resolved, Closed) to the target system's workflow. Import the CSV, run a test on 50 tickets, and verify that replies thread correctly before committing the full dataset.

For ongoing backups, schedule the API script weekly and store the output in cloud storage with versioning. That way you always have a clean restore point.

If you're evaluating a simpler, free alternative for email ticketing, try NeuraDesk free.