PSA Data Export guide
Export Jira Service Management data
Jira Cloud Backup manager exports work items and fields, users, comments and configuration, with media selected separately. Keep the database XML and media folders together as an identifiable backup set.
On this page
Choose the native export
Jira Cloud Backup manager exports work items and fields, users, comments and configuration, with media selected separately. Keep the database XML and media folders together as an identifiable backup set. See Export data from Jira Cloud.
Prepare a usable archive
Plan separate handling for Assets, automation rules, Marketplace app data and Opsgenie-backed features. The guide specifies a 48-hour interval for backups including media and a 30-day backup-age restore limit. Data Center procedures need their own version-specific review. Related official guidance: How to import comments with author and date using the CSV importer in Jira Cloud.
Build the export inventory
| Record group | What makes it usable later |
|---|---|
| Requests and issue fields | Source ticket ID, client/requester, status, dates and custom fields; join notes and files by parent ID |
| Comments and worklogs | Parent ticket ID, ordered content, author, original timestamp and public/private visibility; reconcile child counts |
| Organizations and participants | Source person/company IDs, names, email and parent organization/site; preserve inactive and duplicate-name mappings |
| Attachment metadata and files | Parent ticket/comment ID, original filename, content type and verified downloaded bytes; retain access expiry |
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 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.