Prepare for a switch
Keep useful Jira Service Management history available while teams learn a replacement system.
IT service management · Vendor guide hub
Jira Service Management export, import and migration guides
Explore native tools for moving Jira Service Management records, preparing a usable archive and recovering deleted information.
Cloud and Data Center guidance must remain separate; neither should be inferred from the other.
Choose a native Jira Service Management workflow
Work through an outage
Look up a previously captured ticket, customer, or billing record while the source is unavailable.
Review an absent record
Open the last captured version of a record after it no longer appears in a later successful backup.
Records to assess
Jira Service Management business-record context
- Requests and issue fields
- Comments and worklogs
- Organizations and participants
- Attachment metadata and files
Cloud and Data Center have different endpoints and authentication. Exports must preserve issue keys, custom fields, comments, worklogs, and attachment files separately.
Backup preparation
- Create Atlassian OAuth/API token or Data Center credentials using least privilege.
- Add the tenant, region, or subdomain details described in the credential guide.
- Validate the connection and choose supported record groups.
- Run a manual backup, then review collection results before relying on the snapshot.
Plan the full data lifecycle
Choose a native export method, check the destination importer, and validate a sample before cutover. Preserve readable source history for later client questions.
Invitation only
Keep Jira Service Management history within reach
BackupPSA is invitation only. Join the waitlist and we’ll contact you about your invitation.