Export List of Legacy Pages and their Eligibility Status
Platform Notice: Cloud Only - This article only applies to Atlassian apps on the cloud platform.
Summary
11/11/25 - New Update!
Space admins can now quickly view and export a CSV list of all legacy pages and templates in their space. This makes it easier to plan for the upcoming deprecation of the legacy editor. This addresses two feature suggestions:
For more details, please see the announcement here: New feature: Easily export list of legacy pages and templates
Note: While this tool allows per-space reporting, Confluence currently does not provide a built-in site-wide legacy content reporting tool.
Solution
What can you do with the new tool?
See all legacy content at a glance: Instantly view which pages and templates are still using the legacy editor.
Export detailed reports:Download a CSV for each space with key details like eligibility for conversion, content owners, and direct links. If you manage a large number of spaces, plan a systematic approach by prioritizing high-usage spaces and critical pages for review ahead of the auto-conversion window.
Identify what needs attention: Spot pages or templates with unsupported content or conversion errors or legacy macros that might not function correctly in the new editor, so you can take action before the legacy editor is phased out. Please note that there is currently no functionality to perform a full Confluence instance-wide test for compatibility. Users will need to review pages space by space or work with their admins for broader testing strategies.
How does it work?
Go to Space settings in your Confluence Cloud space.
Select General > Legacy content from the sidebar.
Choose to view pages or templates, and export the CSV report.
What information is included?
For each legacy page or template, you’ll see information such as:
Space name
Space key
Template / Page title
Owner
Eligibility status
Last modified date
Direct link to the content
Understanding eligibility status
Note: If auto-convert is enabled, users will view these pages in the new editor, but they’re still stored as legacy until edited and published. These auto-converted pages will still appear in this report. The legacy editor will be phased out starting January 2026. Learn more about the legacy editor deprecation. For answers to the most common questions and more details about the deprecation plan, visit our Deprecation Details & FAQ page.
If auto-convert is enabled, you can treat every page with the "supported" status as auto-converted. There is no need to manually re-publish every page.
Eligibility Status | What it means |
|---|---|
Supported | Can be converted to the new editor. If auto-convert is enabled, this will happen automatically. |
Unsupported | Can be converted to the new editor, but some sections of content on the page might not be editable. Unsupported sections will be visible when viewing the page, but not editable; the rest of the page will remain fully editable and viewable. |
Error | An error occurred when determining the eligibility status or there is a technical issue on the page. In the legacy editor, you’ll see a "This page can't be converted" message and no convert button. Please try re-formatting the page and saving it; if the issue persists, please contact Support. |
We are continuing to address unsupported use cases to ensure that, by the time deprecation begins in January, nearly all content will be eligible for conversion. For the small number of pages that remain unsupported, please note that these pages will still be viewable even after the legacy editor is deprecated. While these improvements are underway, users encountering 'not convertible' pages should follow the manual recreation steps outlined above. After the auto-conversion period ends, we recommend running random checks on critical pages to ensure the content aligns with expectations.
Was this helpful?