PSA Data Export guide
PSA Data Export
Choose native PSA exports, preserve conversations and files, and validate usable records before migration or cancellation.
On this page
Choose an export that answers the next question
A useful PSA export preserves both the records and enough context to understand them later. Start by deciding whether the destination is a spreadsheet, a searchable archive, a new PSA or another instance of the same product. Each destination needs a different level of detail.
For a reporting task, a ticket list may be sufficient. For a migration, take the destination importer’s required fields back to the source before exporting. For service history, preserve conversations, people, dates and files together.
Compare the native export routes
| Route | Useful for | Inspect before relying on it |
|---|---|---|
| Report or list CSV/Excel | Analysis, inventories, field mapping | Filters, selected columns, date ranges, row limits and time zones |
| Administrative account export | A broad source archive | Included modules, file packaging, access role and download expiry |
| Export in import-template format | A supported native round trip | Stable IDs, matching rules and update behavior |
| Documented API extraction | Related objects and repeatable collection | Permissions, pagination, rate limits and separate child resources |
| Vendor database or migration service | Instance retirement or consolidation | Hosting eligibility, delivery format, service scope and access afterward |
Autotask documents an import-template export route for several entities. Freshdesk provides an administrator XML export; Zendesk offers several account-export formats. NinjaOne Ticketing distinguishes a board CSV from an individual ticket export containing comments. See the vendor guides below for the official references and exact scope.
Build a record inventory before downloading
| Record family | Preserve | Completeness check |
|---|---|---|
| Tickets and conversations | Native IDs, subjects, public replies, internal notes, authors, timestamps | Compare a long thread and its visibility with the source |
| Organizations and people | Customer/company, site, contact, agent and assignment IDs | Resolve every selected ticket to the right customer and requester |
| Fields and classification | Custom-field definitions, statuses, priorities and tags | Save both stored values and their readable labels |
| Files | File bytes, filename, size, parent record and download result | Open sampled files and compare them with the source |
| Service and finance | Time, contracts, invoices, products and payment links where applicable | Reconcile hours and financial totals with module reports |
| Knowledge | Articles, categories, embedded media and access settings | Open an article with images and verify audience access |
Keep helpdesk, PSA, RMM and documentation modules distinct. Zoho Billing needs a financial inventory; Freshdesk needs a support-history inventory. A vendor’s endpoint-management agent belongs to a separate migration workstream.
Validate the first sample
Export one customer with several contacts, an old closed ticket, a recent ticket, an internal note, a custom field and a file. Include a time entry or invoice when those records matter. Compare record counts by type and year, and record missing or transformed fields in an exception log.
Keep the original export untouched. Make working copies for encoding changes and field mapping. Store an export manifest containing the source account, method, selected filters, extraction time, files, record counts and unresolved errors. Record whether archived or deleted items were included by that specific method.
Preserve regional formats and access details
Record the source region, account time zone and currency before exporting. Keep identifiers as text so a spreadsheet does not remove leading zeros or alter long numbers. Test day/month order, daylight-saving transitions, international phone numbers and non-ASCII client names in your sample. Store original timestamps alongside any normalized values.
Use the vendor guide for the actual product edition and tenant region. A US billing template or Cloud import procedure should be applied only where its field and format rules match the destination. Retain a manifest that tells the next administrator which regional rules were used.
Prepare the final export and long-term access
Choose a final-change window with the service team. Take the final authorized export while source access remains active, reconcile it against the pilot, and verify that a colleague can locate an old record and open its files from the retained copy.
Continue with PSA Data Import for destination requirements, PSA Migration for cutover planning, or Deleted Record History for native recovery and earlier captures. The migration use case explains why readable history belongs in the handover plan.
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.