Q: Can I use a JSON file as a backup for Jira?


You could but you shouldn’t.

You might think having a JSON export is like creating a backup of your Jira account. It’s understandable why you might think that since even Jira encourages using a JSON export as a backup. However, it’s not a solution to your problem and here’s why:

1. JSON is hard to use

The JSON (JavaScript Object Notation) is a highly technical format meant for machines to interpret and use. As a result, it isn’t as easy to read as an Excel or CSV file. Take a look at what information about a Jira project will look like in JSON format:


For a Jira user looking to quickly recover from a mistake, parsing through JSON notation can be quite cumbersome. 

2. You have to remember to regularly export new JSON files

If you make the mistake of relying on JSON files as your backup, you will have to remember to update those files on a consistent basis. In some cases, even a week-old export might be too outdated to be used to recover after a problem. This is especially true for Jira users who make important changes to their boards daily. 

3. JSON files do not transfer images

Images cannot be imported into JSON format. As a result, if you lose all of your attachments, you’re going to have to manually add them back, which would take hours or days of work.

You should think twice before deciding that JSON exports are a sufficient backup solution. Use Rewind to backup Jira and ensure that your information is fully protected and easily recoverable.