New feature: Easily export list of legacy pages and templates with space admin tool

[#1]

We’re excited to announce a new feature for Confluence Cloud space admins: a dedicated tool to help you view legacy pages and templates in your space! This feature is rolling out now and expected to reach all customers by the end of the week. 

What’s new?

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:

• https://jira.atlassian.com/browse/CONFCLOUD-77396
• https://jira.atlassian.com/browse/CONFCLOUD-78527

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 with key details like eligibility for conversion, content owners, and direct links.

• Identify what needs attention: Spot pages or templates with unsupported content or conversion errors, so you can take action before the legacy editor is phased out.

How does it work?

1. Go to Space settings in your Confluence Cloud space.

2. Select General > Legacy content from the sidebar.

3. 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.

Eligibility Status	What it means
Supported	Can be converted to the new editor. If auto-convert is enabled, this will happen automatically.
Unsupported	Cannot be auto-converted. Manual conversion may be possible, but some 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 the status is unknown. Please review the page for any errors and try manual conversion.

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. 

[lk]

As an org admin, it would great to view all legacy content at once, not space by space

[Frank Kulla]

I could live with that - if it would work...

I tried it on our main confluence space. When i start the export i get an error message repeatedly, i guess because the csv file get's too big. So before this export i don't know which pages we must edit in advance to make the transition to the new editor smoothly, because there was no tool where we could see those pages. Now i still don't know which pages we must edit, because this export don't work... nothing changed...

Why isn't there an option where we could at least select the page status we are wanting to have in this export? That way we could at least limit the export to only those pages that need to be edited manually, namely "Unsupported" and "Error" state for example?

[Rick Westbrock]

I appreciate that this is being rolled out but in my tenant it shows we will get it in November which leaves less than two months to deal with tens of thousands of legacy pages. I would think that with the late delivery of this feature that Atlassian would push back the timeline for forced conversion of legacy pages by at least 2-3 months at a minimum.