How to export Jira and Confluence before an Atlassian subscription lapses

Before cancelling Atlassian cloud, take a full site backup of Jira and Confluence with attachments, keep readable CSV, HTML or PDF exports of key projects and spaces, and confirm both open. After cancellation the site is deleted on Atlassian's schedule. Verified ticket and page histories can then be assessed for a possible SourceX data license.

What should you export before cancelling Jira and Confluence?

Export two things: a full site backup of Jira and of Confluence, with attachments, and readable copies (CSV for the Jira projects that matter, HTML or PDF for the Confluence spaces people actually used). The site backup is the export designed to keep issues, comments, change history, workflows and attachments together; the readable exports are what a person or a new tool can open without an Atlassian site. Verify both before anyone presses cancel.

For an MSP running a closing client's offboarding, this is a short, high-stakes job. After cancellation, Atlassian removes the site and its data on a schedule its documentation sets out by plan, so read the current page and put the deletion date in the wind-down plan.

What history Jira and Confluence hold

Product area	Records	How far back	Why AI buyers value it
Jira projects	Issues, sub-tasks, status changes, estimates, sprints, comments	The first project created	How engineering and operations work is planned, done and reviewed
Jira Service Management	Requests, agent replies, SLA timers, resolutions	Service desk launch	Request-to-resolution sequences with outcomes
Development links	Branches, commits and pull requests linked to issues	When the code integration was switched on	Ties a bug or requirement to the change that closed it
Confluence spaces	Specs, runbooks, postmortems, decision logs, meeting notes	Space creation	The reasoning behind technical and operational decisions
Page and issue history	Earlier versions, edits, timestamped transitions	Life of each page or issue	How plans changed, and who decided

Why ticket and page history can be licensable

AI developers are training agents to do multi-step technical work: triage a bug, write the fix, review it, update the runbook. Records of that work with outcomes attached rarely appear on the public web. Epoch AI researchers have estimated that language models could fully use the stock of public human-written text between 2026 and 2032 if current trends hold; it is a forecast with wide uncertainty, but it helps explain buyer interest in non-public records. A product company's Jira and Confluence history, with resolutions, linked code and postmortems, is exactly that kind of record.

Export options and what each one misses

Option	What you get	What to watch
Jira site backup	A restorable copy of issues, history, workflows, users and, if selected, attachments	Built to restore into an Atlassian site; large sites take time, so start early
Confluence site or space export	XML for restoring; HTML or PDF for reading	HTML and PDF drop some metadata and page history
Jira issue search exported to CSV	Readable rows for the fields you choose	Flattens history; large result sets need exporting in batches
REST API extraction by a script or backup vendor	Chosen fields and history in your own format	Engineering time and API rate limits
Marketplace backup apps	Scheduled backups to external storage	Their subscriptions end too; check exactly what they cover

Two gaps catch teams out. Many Marketplace apps, such as time tracking or test management tools, keep their data outside the site backup, so list every installed app and export its data separately. And Atlassian accounts are managed at the organization level, so keep an organization admin reachable until every export is verified.

Rights and privacy checks before a review

Who wrote it. Employees' work product generally belongs to the company, but contractor-written material counts as a work made for hire only in the categories listed in 17 U.S.C. 101 and only with a signed written agreement. Check the statements of work and assignment clauses for any outsourced developers.
Whose project it was. If the closing company built software for clients, the issues and specs may belong to those clients. Client work is a red flag unless the client agrees.
What sits inside tickets. Service desk requests carry customer names, emails and screenshots; engineering tickets can hold pasted credentials or API keys. The rules for scrubbing both are fixed with the company before any data work starts.

This is general information, not legal, tax or financial advice. Confirm with your own counsel before acting.

How an MSP spots a client with licensable Atlassian history

You often see these signals during license true-ups, access reviews or offboarding:

Jira has been used for several years with consistent workflows, not abandoned after a pilot
Issues link to repositories, so fixes trace back to code
Confluence holds postmortems, runbooks and decision records, not only a wiki homepage
The service desk records how requests were resolved, not just that they were closed
The company built its own product or ran its own operations rather than delivering client projects
It had 50+ full-time employees at peak (contractors excluded)
An owner, CEO, CFO or other authorized representative can approve a license

The MSP partner page covers the wider referral playbook, and who qualifies lists the full company baseline.

Common mistakes at cancellation

Mistake	Why it hurts	Fix
Cancelling before testing the backup	A corrupt or partial file is discovered too late	Restore or parse a sample before cancelling
Exporting CSV only	History, comments and links are flattened or lost	Keep a full site backup as well
Forgetting Marketplace app data	Time logs or test records vanish with the app	List apps and export their data separately
Keeping exports on the MSP's own storage indefinitely	The MSP becomes custodian of confidential records	Hand exports to company or estate storage with a custody log
Sending samples to SourceX as a teaser	Breaks confidentiality and program rules	The company completes an inventory; partners never share records

How much such history might be worth in a distressed sale is a separate question, taken up in the guide to data asset valuation in distressed deals.

What to say to the client

Next step

Preserve first, then introduce. Register as a partner to get a referral link for the client, or check fit beforehand with the company fit checker. If the client is heading into an ABC, the guide on choosing an ABC assignee lists the records questions to raise, and the same preservation steps apply to Microsoft 365 data after the subscription ends.

Step 1Share your linkSend your personal link to a company you know.
Step 2Company appliesThe company applies itself at /apply.
Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
Step 4You get your rewardYour share of SourceX fees becomes payable.

Common questions

Does a Jira cloud backup include attachments?

Only if you choose to include them when creating the backup. Including attachments makes the file much larger and slower to produce, but screenshots, logs and design files attached to issues are often where the useful detail sits. For a closing company, include them, then check that the number of attachments roughly matches what the site reports.

Can a site backup be opened without an Atlassian subscription?

A site backup is built to be restored into an Atlassian site, so it is awkward to read on its own. Without a site, you need a developer or a tool that can parse the files. That is why it pays to also keep readable CSV, HTML or PDF exports of the most important projects and spaces alongside the backup.

What changes if the client runs Jira Data Center instead of cloud?

The data lives on servers the company controls, in a database plus an attachments directory, so the risk is hardware being wiped or sold rather than a cloud deletion date. Back up the database and attachment folders together, record the application version, and keep the backup in company-controlled storage before the servers are decommissioned.

Is Jira data from a closing startup worth assessing?

It can be, if the company meets the baseline: 50+ full-time employees at peak (contractors excluded), several years of records and the rights to license them. Smaller teams usually fall short on size. Depth matters too: linked code, written resolutions and postmortems make a history more useful than a backlog of one-line tickets.

Who should hold the exports during a wind-down?

The company, or the fiduciary running the wind-down, in storage it controls and can account for. An MSP can run the export and hand it over with a short custody note, but should not become the long-term holder of a client's confidential records. Referral partners never receive, store or forward the data.

Should the client keep paying Atlassian until a license decision is made?

Only if the exports cannot be verified in time. Keeping a minimal subscription for a short period can cost less than losing history for good, but verified backups and readable exports in company storage let the subscription end on schedule while SourceX reviews the company's inventory of systems and years.

Free resources

Operational data inventory builder — List systems, record types, years held and owners.
AI readiness assessment — Ten questions, five dimensions, a score out of 100.
EBITDA calculator — Reported and adjusted EBITDA from net income.
All free tools · MCP resource center

By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09

Know a US company with valuable proprietary data?

Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.

Refer a company →

I own a business

Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.

Start an assessment