PSA Data Export guide
Ticket history: preserve the conversation around the work
Keep ticket fields, replies, private notes, requesters, time, and file context understandable after the live record changes.
On this page
What makes ticket history readable
Preserve the ticket's stable ID, subject, status, priority, customer/requester, assignee, dates, custom fields, replies, internal notes, and time entries where the platform exposes them. Keep each related object's source ID so the archive can reconstruct the conversation without guessing.
Why a list export can fall short
List and report exports usually optimize for rows and metrics. Conversations can require a per-ticket endpoint; attachment metadata can point to separate file downloads; archived tickets may use a different endpoint. Those are vendor-specific facts, not safe cross-platform assumptions.
A practical validation sample
Check an old closed ticket, a ticket with many replies, a private note, custom fields, a merged or linked ticket, and at least one attachment. Compare visible dates and people with the source. Record any resource the credential cannot read.
Keep historical conversations usable
Retain source IDs, capture dates and the relationships needed to read the conversation. Review public and private visibility in the archive and use the destination-specific import guide when preparing a transfer.
Related workflows
Use Deleted Records for records absent from a later snapshot and PSA Migration before canceling a source subscription.
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.