Updated 2026-10-10 · by Hieu Tran, written with AI agents and checked against the sources below
Jira Cloud's built-in backup exports the whole site. Exporting just one project, to hand to a client, archive before deletion or move to another site, has been one of Atlassian's most-voted requests since 2013 (JRACLOUD-34307, over 1,000 votes as of today). Here are the options and what each loses.
No self-serve tool yet. If you need one project or space exported now, tell us through early access: we'll do it for you while we build the app.
Your options
Issue search → export CSV: filter by project and export. Quick, but you get fields, not history: attachments, full changelogs and configuration are missing, and big projects need several exports.
Site backup (Backup manager): complete, but for the whole site; you'd restore it somewhere and delete everything else.
Cloud-to-cloud migration tools in Atlassian administration can move projects between Cloud sites, with their own limits on what moves.
Marketplace apps: backup and restore apps (Rewind, Revyz, GitProtect) and copy apps (Deep Clone) cover parts of this; check what each includes before buying.
REST API: issues, comments, changelogs and attachments are all readable by API; a script can export one project fully, but needs care with rate limits and attachments.
What to check in any export
Issue count matches the project's count in Jira.
Comments, attachments and history are included, not just current fields.
Users map correctly (exports often show account IDs, not names).
You can actually re-import it: test on a sandbox before you delete anything.
Confluence spaces
Confluence has a similar long-standing request (CONFCLOUD-3191). Space export to PDF, HTML or XML exists per space, but check what it includes before relying on it as an archive.
No self-serve tool yet. If you need one project or space exported now, tell us through early access: we'll do it for you while we build the app.