Blog ·
Back up Jira Cloud: automatic backups and the restore test
To back up Jira Cloud you have two tools from Atlassian. Any site admin can take a manual backup from the Backup manager under Settings, System, and download the file. Sites on a Premium or Enterprise plan can buy the Atlassian Backup and Restore add-on, which runs backups automatically on a daily or weekly schedule and keeps them for 30 days. Neither one is a full safety net by itself, and the part most teams skip is the one that matters in a bad week: checking that a backup restores. This guide covers both tools, what they leave out, and a small routine that keeps the whole thing honest.
Statements about Jira's built-in features are as of October 2026, from Atlassian's own documentation.
The two ways to back up Jira Cloud #
| Backup manager | Atlassian Backup and Restore | |
|---|---|---|
| Where | Jira Settings, System, Backup manager | admin.atlassian.com, Data management |
| Who can run it | A Jira admin | Someone who is both organization admin and app admin |
| Plan | Any Jira Cloud plan | Paid add-on, Premium or Enterprise only |
| Schedule | Manual, one at a time | One-time, daily or weekly |
| Where the backup lives | A file you download | Atlassian-owned storage, no download |
| How long it is kept | As long as you keep the file | 30 days, then it expires |
| Marketplace app data | Not included | Not included |
The short version: the backup manager gives you a file you own, and Backup and Restore gives you a schedule you do not have to remember. Many teams with the add-on still take a manual backup now and then, because the add-on's backups cannot be downloaded.
Back up Jira by hand with the backup manager #
The manual backup is the one every Jira Cloud site has. Atlassian's steps:
- Select Settings, then System.
- In the Import and export section, select Backup manager.
- Under Backup for cloud, select Create backup for cloud, and choose whether to include attachments, avatars and logos.
- Wait for the backup to finish, then download the file and store it somewhere you control.
There is a limit on how often you can do this. Atlassian's export page says it plainly:
You can backup your Jira data at any time. However, if you include attachments, avatars, and/or logos, you'll need to allow 48 hours between backups.
If you try too soon, Jira shows "Backup frequency is limited" with a countdown. The timer starts when the previous backup completes, and only Atlassian Support can reset it. So a plan that relies on "we'll take one right before the big change" can fail on the day you need it, because someone took one yesterday.
The backup manager also does not run on its own. It is a button, and a button only gets pressed when somebody remembers.
Automatic Jira backups with Atlassian Backup and Restore #
If you need a Jira automatic backup, Atlassian's own answer is the Backup and Restore add-on. Atlassian describes it this way:
You can run backups whenever you need them, or schedule them daily or weekly. The backups are stored in Atlassian-owned storage.
To set a schedule:
- Go to admin.atlassian.com and pick your organization.
- Select Data management, then Backup and restore.
- Select Create new policy, name it, and choose the app.
- Select Set schedule, pick Daily or Weekly, and choose the date.
A few things to know before you rely on it:
- You choose the date, Atlassian chooses the time. Backups and restores are queued, so you cannot pick an hour.
- Backups expire after 30 days. A problem you notice six weeks later cannot be restored from this tool.
- Permissions matter after setup. If the person who created the policy loses organization admin or app admin rights, scheduled backups stop running until someone with both rights updates the policy.
- Everything is included. You cannot back up a single project; all projects go in, with a choice about attachments.
- You cannot download the backup. It stays in Atlassian's storage.
- Sandboxes only take one-time backups. Daily and weekly schedules are for production sites.
Atlassian states a recovery point of 24 hours and a recovery time of 12 hours for Jira sites up to 300 GB and 7 million attachments. That is the promise for the restore itself; the decision to restore is still yours to make.
What neither tool backs up #
Both tools skip Marketplace app data. If your team stores test cases, checklists, time logs or schedules in an app, that data lives with the app vendor, and you need the vendor's own export or backup option. Make a list of the apps you depend on and note, for each one, how you would get its data back.
Automation rules are another gap in the manual backup. Atlassian notes that automation flows are not exported with the backup manager, and you can export and import them separately from the automation settings. If your site runs on a few dozen rules, export them after each round of changes. The Jira automation examples guide shows the kind of rules worth keeping.
Third-party backup apps on the Atlassian Marketplace fill some of these gaps, with features such as longer retention and storage you choose. They are a fair choice when your compliance team asks for copies held outside Atlassian. Compare their own pages for what they include and what they cost.
A backup you never restore is a guess #
A backup proves nothing until it has been restored once. The common failures are quiet: the scheduled policy stopped after an admin left, attachments were left out, or the file you downloaded is the one from last spring.
A restore test does not have to be dramatic. With Backup and Restore, any backup can be restored into an empty sandbox, which never touches production. With a manual backup file, restore it into a test site. Then check a short list:
- Open three projects at random. Do the issues, comments and history look right?
- Open an issue that should have attachments. Are they there?
- Check that users and groups came across, and that permissions look the way production does.
- Note how long the restore took, and write it on the ticket.
Do it on a schedule. Quarterly is a sensible starting point for most teams, and right after any big migration or cleanup.
Make the backup routine run itself #
Every step above is a recurring chore: take the manual backup, check the scheduled policy is still active, export the automation rules, check the Marketplace exports, run the restore test. Chores like these are forgotten in exactly the month something goes wrong. The fix is to give each one a ticket that arrives on its own.
| Task | Suggested cadence | Who |
|---|---|---|
| Check the Backup and Restore policy ran | Weekly | Jira admin |
| Manual backup, file stored off-site | Monthly | Jira admin |
| Export automation rules | Monthly, or after changes | Automation owner |
| Check Marketplace app exports | Quarterly | Jira admin |
| Restore test into a sandbox | Quarterly | Jira admin |
You can create these tickets with a Jira Automation scheduled rule. Scheduled rules count against your automation limits, and Atlassian disables a scheduled rule after 10 consecutive failures, so a quarterly rule that breaks can go quiet for a long time. The Jira recurring tasks guide compares the options.
Recurring Work Items for Jira is our app, and a routine like this is what it was built for:
- Turn the app on for the admin or ops project and choose who may schedule.
- Create one rule per task above, weekly, monthly or quarterly.
- Title each with tokens so the ticket names its period, for example
Backup restore test {{now.monthName}} {{now.year}}. - Put the checklist from this guide in the description, and set the assignee and a due date as an offset from the run.
It uses no Jira Automation quota, because the scheduling is the app's own. Each created or failed run is written to the rule's history with its reason. A rule only creates tickets in the project it lives in. It is free for up to 10 users.
The app creates the reminder tickets. The backups themselves are still taken by Atlassian's tools or your backup app.
When the manual way is enough #
If you run a small site with a handful of projects and one admin who takes a monthly backup without fail, the backup manager and a calendar reminder are enough. Download the file, keep two copies in different places, and try a restore into a test site once a year. Scheduled backups and a ticket routine earn their place when more than one person shares the job, when the site holds work you could not recreate, or when someone will one day ask you to prove the backups ran.
For the rest of an admin team's routine, see Jira for IT operations and Jira hygiene.
Frequently asked questions #
Does Jira Cloud back up automatically? Only with the paid add-on. A backup you can restore when you need it requires either the manual backup manager or the Backup and Restore add-on on a Premium or Enterprise plan.
How often can I take a manual Jira backup? With attachments, avatars or logos included, Atlassian asks for 48 hours between backups.
How long are scheduled backups kept? Atlassian Backup and Restore keeps each backup for 30 days, then it expires.
Can I back up a single Jira project? Not with Atlassian's tools. Both include every project.