PSA Data Export guide
Export NinjaOne data
NinjaOne Ticketing exports board rows to CSV using the selected filters and columns. An individual ticket export includes fields and public/private comments; the documented option also covers tickets on the deleted board.
On this page
Choose the native export
NinjaOne Ticketing exports board rows to CSV using the selected filters and columns. An individual ticket export includes fields and public/private comments; the documented option also covers tickets on the deleted board. See NinjaOne Ticketing: A Guide to Exporting Tickets.
Prepare a usable archive
Record the export user’s time zone. Treat ticketing, PSA billing and NinjaOne Documentation as separate scopes; verify their respective exports and file coverage when building your inventory. Related official guidance: NinjaOne Ticketing: Delete and Restore Tickets.
Build the export inventory
| Record group | What makes it usable later |
|---|---|
| Psa tickets and comments | Source ticket ID, client/requester, status, dates and custom fields; join notes and files by parent ID |
| Ticket contacts and forms | Source person/company IDs, names, email and parent organization/site; preserve inactive and duplicate-name mappings |
| Agreement context | Customer and contract/plan IDs, effective dates, renewal terms, rates and linked services; preserve source status |
| Psa invoices where enabled | 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.
Choose board columns before exporting
NinjaOne’s Filter and Configure Boards guide says the selected columns determine exported output; tags appear in the CSV’s final column. Save the board filters, columns and export user’s time zone alongside the file. Use individual-ticket exports when you need comment history, and review deleted-ticket recovery while the native recovery window is open. Keep PSA billing and Documentation exports as distinct inventory tasks.
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.