PSA Data Export guide
How to back up NinjaOne data
A practical NinjaOne backup workflow covering PSA tickets and comments, credentials, native exports, recurring snapshots, and important limits.
On this page
Choose a NinjaOne backup method
| Method | Use it for | Check before relying on it |
|---|---|---|
| Native report/export | A current spreadsheet or report | Whether it includes notes, files, custom fields, and related records |
| Official API workflow | Structured capture you control | Authentication, pagination, licensing, rate limits, and file downloads |
| BackupPSA | Dated search, comparison, and snapshot download | Supported collections and successful capture results |
NinjaOne reporting can answer operational questions, while API coverage varies by enabled PSA feature and tenant licensing.
What to preserve from NinjaOne
The business record groups to assess are PSA tickets and comments, ticket contacts and forms, agreement context, and PSA invoices where enabled. Keep source identifiers and relationships so a ticket or financial record still resolves to a readable customer, person, agreement, and date. This page is limited to NinjaOne PSA, ticketing, and business records—not endpoint or RMM backup.
Set up recurring backups
- Follow the NinjaOne credential guide.
- Use a dedicated identity with the smallest workable read permissions.
- Select supported record groups and run a manual capture.
- Review counts and collection failures; sample old and complex records.
- Use eligible daily scheduling on Full Access or repeat manual captures within plan limits.
Confirm the tenant exposes the PSA ticketing and billing resources shown in current Public API schemas; endpoint-management resources are outside this guide.
Plan access to retained history
Keep dated captures, source identifiers and related records together so your team can retrieve useful history after a platform change. Review the native export guide before finalizing the archive.
Preserve history before switching platforms
Run and validate a final capture before source access ends, then follow the PSA migration checklist. Use the destination vendor’s documented importer for the transfer.
Review records after deletion
A previously captured record remains useful if it was backed up before it disappeared. Only compare successful results for the same record group, and do not treat absence as proof of deletion when permissions or an API failure could explain it.
Official source and limits
Review NinjaOne official API documentation alongside the live tenant. API documentation does not prove every module is licensed or visible to the chosen credential. Validate the selected records against the official interface and your account permissions.
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.