On 1 December 2026, XML Site Export and XML Space Export in Confluence Cloud reach End of Life. Nothing switches off that day, which is exactly why this one is easy to miss. The export button will still work. What goes away is everything behind it.
This is a Cloud change. Data Center is only involved in one edge case, covered below.
What actually changes on 1 December
From Atlassian’s knowledge base article and the June announcement:
- The feature keeps working. “The features will continue to work.”
- Support ends. Atlassian will no longer fix bugs, accept support tickets, or provide SLAs for XML export. You use it “at your own risk”.
- XML Import is not affected. “XML Import is not in scope for this change.”
- CSV Site Export and CSV Space Export are the supported path, described as “fully supported and unaffected” and available on all plans (Free, Standard, Premium, Enterprise).
The practical meaning: if an XML export fails or produces a broken file on 2 December, there is no ticket to raise. If that export was your backup, you find out at restore time.
Where XML exports hide
In most sites nobody decided to depend on XML export. It accumulated. The places to check:
- Scheduled or scripted backups. Any script, scheduled job or runbook that requests an XML site or space export.
- Offboarding and archive procedures. “Export the space to XML before deleting it” is a common line in old runbooks.
- Compliance and audit evidence. Periodic exports kept as a record.
- Space moves between sites. Export from one site, import to another.
- Internal documentation. Admin guides that tell space admins to choose XML.
The switch
- Space export: Space Settings > Export. The file format list shows PDF and CSV first. XML now sits under Advanced Options next to HTML, with a warning on it: “Support for XML export ends December 1, 2026. You can continue to use this format. After December 1, Atlassian will no longer provide bug fixes or technical support for XML exports. We recommend switching to CSV export.”
- Site backup: Confluence Settings > Backup Manager, select CSV as the export format.
So the product already steers space admins away from XML. Anyone following an old runbook that says “choose XML” will now have to open Advanced Options to find it. This is the screen as it looks today:
Atlassian’s own migration tips are short and worth following in order:
- Identify scripts, scheduled jobs and runbooks that use XML export and switch them to CSV.
- Update internal documentation to reference CSV.
- Validate the first CSV export: extract it and spot-check pages against the live content, confirming it holds “the expected spaces, pages, and attachments”.
- “Keep one final XML export as a transitional backup until you’ve fully validated your CSV workflow.”
One permission detail from the same page: an export only contains content visible to the person running it, while site admins get everything. The export screen makes the same point: the default content choice is “All content you have permission to view”. A backup run by a non-admin account can be silently incomplete in either format.
The one exception: Cloud to Data Center
If you have a reason to restore Cloud content into Data Center, CSV does not help. The Data Center site restore “only accepts XML format” and “CSV cannot be imported into DC”. Atlassian’s instruction for that case is to contact Support to discuss options, and the time to do that is before 1 December, while tickets on the subject are still accepted.
What to test before you rely on it
- Whiteboards, databases and slides are left out. The export screen says so directly: “These content types aren’t supported for space exports yet. They will be excluded from your file.” If a space leans on whiteboards or databases, a space export in any format is not a full copy of it.
- Restore. Atlassian’s pages cover exporting to CSV. They do not walk through restoring a single space from a CSV space export. An export you have never restored is not a backup yet.
- Contents beyond pages and attachments. The knowledge base article tells you to confirm spaces, pages and attachments. It does not list comments, restrictions or page history. Check the ones your organisation cares about in the extracted file.
Checklist before 1 December
- List every script, job and runbook that produces an XML export
- Switch each to CSV and run it once
- Extract one CSV export and spot-check pages and attachments against live content
- Confirm the exporting account can see everything it is meant to back up
- List the spaces that rely on whiteboards, databases or slides, since space exports exclude them
- Test a restore of one space on a sandbox or test site
- Take one final XML export and keep it until the CSV workflow is validated
- If Cloud to Data Center is on your roadmap, open the Support conversation now
- Update internal admin documentation
If you have already moved your backups to CSV, what did the first restore test show?
Verified against Atlassian’s knowledge base article (last updated 6 August 2026), the Community announcement, and the Space Settings > Export screen on a Cloud site, on 19 November 2026.