PSA Data Export guide
Export Freshdesk data
Freshdesk offers individual ticket printing to PDF and an Account Admin XML account export through Admin > Account > Account Details. The documented account export includes tickets and solution articles.
On this page
Choose the native export
Freshdesk offers individual ticket printing to PDF and an Account Admin XML account export through Admin > Account > Account Details. The documented account export includes tickets and solution articles. See How can I export tickets including the content of the ticket?.
Export contacts and companies as CSV
Open Contacts > Export, select required fields including custom fields, and retrieve the file through Admin > Account exports. Repeat from Companies. Keep the export details with the file. Contact tag filtering in the interface does not restrict this export to those tagged contacts. See Importing and Exporting customer data. These CSVs complement ticket XML/PDF exports; use the Freshdesk import guide when planning a customer-data round trip.
Prepare a usable archive
For a Zoho Desk move, retain the original export filenames and keep Freshdesk API access active for file retrieval. Test a ticket with public replies, private notes and inline images against the source. Related official guidance: Migrating From Freshdesk to Zoho Desk.
Build the export inventory
| Record group | What makes it usable later |
|---|---|
| Tickets and custom fields | Source ticket ID, client/requester, status, dates and custom fields; join notes and files by parent ID |
| Public replies and private notes | Parent ticket ID, ordered content, author, original timestamp and public/private visibility; reconcile child counts |
| Contacts and companies | Source person/company IDs, names, email and parent organization/site; preserve inactive and duplicate-name mappings |
| Attachment metadata and downloadable files | Parent ticket/comment ID, original filename, content type and verified downloaded bytes; retain access expiry |
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.