PSA Data Export guide
Export Syncro data
Syncro provides Ticket Export and Ticket Time Entry reporting alongside its other ticket reports. Use the report that matches the required business question and inspect the exported columns.
On this page
Choose the native export
Syncro provides Ticket Export and Ticket Time Entry reporting alongside its other ticket reports. Use the report that matches the required business question and inspect the exported columns. See Ticket Reports.
Separate ticket fields from communications
The current Ticket Reports guide distinguishes Ticket Export, which omits comment and note bodies, from Ticket Communications, which covers public notes, private notes and email. Communications runs cover a maximum 60-day window; the guide directs longer bulk comment-history requests to Syncro Support. Export time entries separately and reconcile ticket IDs across files. This current guidance takes precedence over the vendor-marked legacy Export All Data article.
Prepare a usable archive
The legacy Export All Data guide separates customers, tickets, invoices and inventory and directs contacts/comment requests to support. Syncro marks that legacy article unverified: confirm its current procedure with support before scheduling a final export. Related official guidance: Export All Data.
Build the export inventory
| Record group | What makes it usable later |
|---|---|
| Tickets and ticket comments | Source ticket ID, client/requester, status, dates and custom fields; join notes and files by parent ID |
| Customers and contacts | Source person/company IDs, names, email and parent organization/site; preserve inactive and duplicate-name mappings |
| Estimates and appointments | Estimate/customer IDs, quoted lines and validity; appointment time zone, participants and related ticket |
| Invoices and payments | Document and customer IDs, line items, currency, tax, totals, balances and payment allocations; reconcile financial meaning |
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.
Retain an organization export
Syncro’s Organization import/export guide describes CSV exports, including custom_fields values. Keep those identifiers with the ticket and communication files so staff can resolve the original client relationship.
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.