PSA Data Export guide
Export Freshservice data
Freshservice’s knowledge-base guide describes an Account Admin XML export through Account > Other Details > Export now, including solution articles. Supplement your inventory with tickets, conversations, requesters, workspaces and linked ITSM records.
On this page
Choose the native export
Freshservice’s knowledge-base guide describes an Account Admin XML export through Account > Other Details > Export now, including solution articles. Supplement your inventory with tickets, conversations, requesters, workspaces and linked ITSM records. See Getting Started with Knowledge Base 2.0.
Export ticket fields and complete conversations
Under Tickets, apply filters, clear selected rows if Export is hidden, choose CSV or Excel, and select the required fields for each run. Freshservice documents 10,000 tickets per export, 200 records in Analytics PDF exports and five scheduled exports per module. Split larger runs into reconciled ranges.
Standard ticket fields and interaction columns are distinct from full conversation history. Use account-wide XML or the API for notes and timestamps. Service Request item fields require their own Analytics/API treatment. See Exporting tickets.
Prepare a usable archive
For a partner migration, check the destination attachment retrieval method and workspace dependencies before choosing source extracts. Compare a full conversation and its downloaded files with the export sample. Related official guidance: How to migrate into Freshservice via Bulk APIs? [For Freshservice Data Migration Partners].
Build the export inventory
| Record group | What makes it usable later |
|---|---|
| Tickets and service requests | Source ticket ID, client/requester, status, dates and custom fields; join notes and files by parent ID |
| Conversations and notes | Source object ID, parent references, original dates, field definitions and a representative record checked against the source |
| Requesters and workspaces | Source person/company IDs, names, email and parent organization/site; preserve inactive and duplicate-name mappings |
| Problems, changes, and linked assets | Source object ID, parent references, original dates, field definitions and a representative record checked against the source |
Validate formats and attachments
Open CSV or spreadsheet output with dates and identifiers intact. Validate JSON pagination and error handling. Download and verify file contents as well as metadata while authenticated or time-limited URLs remain accessible.
Prepare for migration
Count records by type and year, sample the oldest and most complex items, save field dictionaries, and document missing modules. Use the PSA migration checklist before cancellation.
Keep the source history useful
Store the original export, field definitions, file manifest and validation results together. Follow the source archive planning use case and keep the archive readable after cutover.
Plan your independent PSA archive
Keep source history available after your move. Join the waitlist for invitation-only BackupPSA access, or contact us about your platform.