PSA Data Export guide
Export Atera data: tickets, contacts and device lists
Choose an Atera report for a reporting question, a device view for an inventory, or an entity API export for structured records. Record the selected filters and format before downloading.
On this page
Choose a report, Excel view or API export
Atera documents CSV operational reports, PDF/Excel analytical output and JSON API retrieval by entity. Ticket summaries and time sheets serve reporting needs; customers, contacts and tickets have separate API resources. See Atera Data Export FAQ.
Choose the output for each task
| Task | Official starting point | Format and scope |
|---|---|---|
| Ticket reporting | Timesheet, Ticketing Summary or Customer Tickets Overview | CSV/Excel reporting output; inspect the fields included |
| Ticket records | Tickets API | Paginated JSON; reconcile ticket data and related files separately |
| Customer list | Customers API or a customer-facing report | Entity records and report metrics answer different questions |
| Contacts | Contacts API | JSON records; convert a working copy if CSV or Excel is needed |
| Device inventory | Devices page or Auditor report | Excel view or CSV report; preserve customer and filter scope |
The Atera Data Export FAQ identifies customers, contacts and tickets as separate API resources. Export per entity and retain a manifest; a report is not an account-wide backup.
Export a filtered device list to Excel
On the Devices page, choose the required filters and columns, then use the download icon to export the view to Excel. Record whether the inventory covers one customer or a wider selection. Compare a sample device's customer assignment and status with the source. Keep device inventory separate from endpoint backup or agent migration.
Check all records against selected records
Save filters, export time and counts with every file. Reconcile batches against the intended customer, status and date range. A successful download proves that a file was produced; compare it with the source selection before describing it as complete. Retain original JSON when converting API results to CSV or Excel.
Does an Atera report export include the full ticket conversation?
A reporting row and a complete conversation have different acceptance checks. Review the selected report's fields, then compare comments and downloaded files against the source ticket. Use the entity API route and separate file handling where the reporting output does not provide the information required for your archive.
Prepare a usable archive
Choose a source method for each entity and reconcile record counts. Review comments, file downloads, technician IDs, time entries, custom fields and invoice details separately from summary metrics. Related official guidance: Atera Data Import FAQ.
Build the export inventory
| Record group | What makes it usable later |
|---|---|
| Tickets, comments, and attachment references | 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 |
| Contracts and rates | Customer and contract/plan IDs, effective dates, renewal terms, rates and linked services; preserve source status |
| Billing and invoices | 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.
Plan export batches, deleted records and files
Atera’s Data Export FAQ describes typical report limits of approximately 500–5,000 rows. Split reporting exports into reconciled batches or use paginated API retrieval. Deleted records are excluded; preserve history before deletion and consult the native recovery guide when a ticket has already disappeared. Download attachments individually. Document automation settings, thresholds and monitoring profiles separately because the FAQ excludes them from export; they are configuration work, separate from ticket history.
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.