Export guide · Checked against Jira documentation 2026-11-17
How to export all your data from Jira
In Jira Cloud, go to Settings > System > Backup manager and select Create backup for cloud. The download unzips to entities.xml and activeobjects.xml plus optional attachment, avatar and logo folders. For spreadsheets, export work items from search as CSV, up to 10,000 per export. Automation flows and third-party app data are not included in the backup.
Who can export from Jira
This guide covers Jira Cloud. The site backup is created in Backup manager, which sits under Settings > System in the Import and export section. Atlassian's backup page does not name the role required, so confirm that your account can open the System settings before planning around it.
Organization admins can prevent people from exporting data in particular app instances or for certain classification levels. If the export options are missing or blocked, check with your organization admin whether such a policy applies.
The CSV export of work items runs from the search page or a space's list view. The pages checked do not state a required permission. The file is built from the work items your search returns.
How to export, step by step
Route 1 of 4
Backup manager (the full site backup)
A user with access to Settings > System, where no organization policy blocks export.
- 01Select Settings, then System.
- 02In the Import and export section, select Backup manager.
- 03Under Backup for cloud, tick the option to include files if you want work item attachments, user avatars and space logos in the export.
- 04Select Create backup for cloud.
- 05After the backup is complete, select Download backup file.
You can back up at any time, but if you include attachments, avatars or logos you must allow 48 hours between backups. Atlassian recommends staying within 25 GB of total data and 50 to 100 GB of attachments.
Route 2 of 4
CSV export from search
A user who can search the work items.
- 01From any page in Jira, select Filters > Search work items.
- 02Enter a search query that returns the work items you want.
- 03Select the More actions menu, shown as three dots.
- 04Choose Export.
- 05Select Export CSV - all fields.
- 06Open the download link in the in-product notification when processing finishes.
The export runs in the background, so you do not need to stay on the page. Atlassian supports up to 10,000 work items per export, and exports with many fields are slower.
Route 3 of 4
CSV export from a space
A user who can view the space.
- 01Navigate to your space.
- 02Select List, and optionally edit the filter query to return a specific list of work items.
- 03Select the More actions menu, shown as three dots.
- 04Choose Export.
- 05Select Export CSV - all fields.
Route 4 of 4
Splitting a large CSV export with JQL
Anyone exporting more than 10,000 work items to CSV.
- 01Enter your original JQL in Filters > View all work items and note the total count.
- 02Split the results into batches of fewer than 10,000, using fields such as space, created date ranges, work type or status.
- 03Run each batch and confirm its count is under 10,000.
- 04Export each batch with the standard CSV export.
- 05Merge the files and confirm the combined total matches the original count.
Atlassian recommends created dates as the most predictable way to split. An older workaround that appended a pager/start value to the export URL is marked as deprecated as of March 2026.
What comes out
The backup downloads as one file that you unzip. At the top level are two XML files, activeobjects.xml and entities.xml, which together hold the database data. Next to them is a data folder with attachments, avatars and custom-template-icons subfolders, and a logos folder. The media folders are present only if you chose to include files.
The backup holds work items and their field content, including system and custom fields, board and sprint data, users and user group settings, comments, space configuration such as workflows, schemes, screens and work types, and Advanced Roadmaps data. Because it is a database dump in XML, it is built for restoring into Jira, not for opening in a spreadsheet.
The CSV export is one row per work item, encoded as UTF-8. With Export CSV - all fields, each comment is placed in its own Comment column, in chronological order. Older versions of Microsoft Excel may read the file as ANSI and show garbled characters, so open it in a text editor or a spreadsheet program that handles UTF-8.
| In the export | What it contains |
|---|---|
| entities.xml | Database data for the site. Atlassian states that database data is stored in both XML files. |
| activeobjects.xml | The second file of database data. |
| data/attachments | Work item attachments, when files are included. |
| data/avatars | User avatars, when files are included. |
| data/custom-template-icons | Icons for custom space templates, when files are included. |
| logos | Space logos, when files are included. |
| CSV export | One row per work item with every field as a column and one Comment column per comment. |
Before you rely on it
Limits and gotchas.
- The backup does not include automation flows, third-party apps and app data, Jira Service Management features powered by Opsgenie such as alerts and on-call schedules, Assets for Jira Service Management, app access settings, or the views configurations, insights and vote fields of Jira Product Discovery.
- Automation flows can be exported and imported manually as a separate step.
- A backup that includes attachments, avatars or logos can be created only once every 48 hours.
- Since January 22, 2026, Backup manager restores only from backups that are 30 days old or less. An older backup file is an archive, not a restore point.
- The CSV export is supported up to 10,000 work items. Larger sets have to be split with JQL and merged by hand.
- Jira Cloud does not natively support downloading attachment files in bulk from search. Attachments come out through the site backup.
Handle with care
Personal data inside a Jira export.
- Users and user group settings, which the backup includes.
- User avatars, when files are included.
- Reporter, assignee and other people fields stored on each work item.
- Comments, which carry what named staff and customers wrote.
- Attachments, which can be screenshots, logs or documents containing anything users uploaded.
- Custom fields, which often hold customer names, emails or account numbers.
An export is a copy outside the access controls of Jira. Store it encrypted, limit who can open it and delete working copies when you are done. The personal data scrubber removes common identifiers in your browser before a file is shared.
What the export can be worth
Outrich Data is a direct buyer of de-identified company data for AI training, from companies with 50 or more employees. We never connect to your Jira account: your team runs the export above and removes what is out of scope. Not every export qualifies, and a rights review comes before any offer.
Questions
Exporting from Jira: common questions.
How do I back up an entire Jira Cloud site?
What is the limit on exporting Jira work items to CSV?
Does a Jira CSV export include comments and attachments?
What is missing from a Jira Cloud backup?
Sources
Steps were checked against Jira documentation on 2026-11-17. Vendors change menus, plans and limits, so confirm against the linked pages. Jira is a trademark of its owner. Outrich Data is not affiliated with Jira.
Find out if your data qualifies.
Eleven questions, about five minutes, no call required. You get an answer on screen and a written follow-up.