PSA Data Export guide
How to back up Jira Service Management data
A practical Jira Service Management backup workflow covering requests and issue fields, credentials, native exports, recurring snapshots, and important limits.
On this page
Choose a Jira Service Management 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 |
Cloud and Data Center have different endpoints and authentication. Exports must preserve issue keys, custom fields, comments, worklogs, and attachment files separately.
What to preserve from Jira Service Management
The business record groups to assess are requests and issue fields, comments and worklogs, organizations and participants, and attachment metadata and files. Keep source identifiers and relationships so a ticket or financial record still resolves to a readable customer, person, agreement, and date. Cloud and Data Center guidance must remain separate; neither should be inferred from the other.
Set up recurring backups
- Follow the Jira Service Management 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.
Choose Cloud or Data Center instructions first. Cloud JSM request APIs and Data Center Jira REST endpoints are related but not interchangeable.
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 Jira Service Management 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.