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. 

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

[Brian Taylor]

When will this be rolled out to all sites.  As of this morning I have not seen this feature in either our sandbox or production environments. 

[Trixie Johnson]

Agree with the comments above. If you have a space you've been using for quite awhile (& probably does have legacy content), the export fails, likely due to the size. It would be great if you could trigger this process to kick off at a page and include all child pages below it, that way we could export in groups and avoid this failure. As it is now, this tool is unusable....but was a great idea.

[Elle Ky]

Hi @Frank Kulla @Trixie Johnson

We apologize for the inconvenience. We are aware of an issue with the export erroring out for large spaces and are actively working on a fix. Please "watch" and follow along on CONFCLOUD-83179 to receive updates on the rollout of this fix. Thank you for your patience and understanding.

[Elle Ky]

Hi @Brian Taylor 

This is rolled out to all customers as of last week Friday November 14. Please let me know if you're still having trouble with accessing the space admin tool in your sandbox or production environment.

[Elle Ky]

Hi @Rick Westbrock 

Thank you for your feedback and for your patience as we roll out the new space admin tool.

Before this tool was released, we provided a self-serve script and support to help customers retrieve this information, as noted in our original announcement and FAQ page on July 1, 2025. Our support team was also available to assist if you needed help before the tool became available.

(Please note: Since the rollout of this new admin tool, that script has now been retired.)

I understand this isn’t the outcome you were hoping for, but at this time, the deprecation timeline for legacy pages remains unchanged. Thank you again for sharing your feedback.

[lk]

@Elle Ky I encountered issues with the tool as well : the file failed to download in one space, and in another, the CSV showed many "error" statuses. After rerunning the tool with the Admin Key, it worked better—no error statuses appeared, and the file downloaded successfully. It seems the issues were caused due to restricted pages.

My question: will the auto-convert tool convert restricted pages as well?

[lk]

@Elle Ky 
I encountered issues with the tool as well : the file failed to download in one space, and in another, the CSV showed many "error" statuses. After rerunning the tool with the Admin Key, it worked better—no error statuses appeared, and the file downloaded successfully. It seems the issues were caused due to restricted pages.

My question: will the auto-convert tool convert restricted pages as well?

[Ariel Prado]

Hi @Elle Ky 

Today at 8:30 at morning Madrid time zone, i downloaded the Legacy Content CSV file, without the Admin Key. I got 533 pages with 173 pages in Error. Some errors was due restriction, and others about some missing macros. 

Later today, i did 3 downloads more, with 1hs of difference between the first one and the others. Now i got 533 pages without error, all supported.

I don't know if Atlassian release something about Legacy, but i am trying to understand this behavior, and also trying to understand the 3 different statuses. So please can you clarify about this? Did Atlassian change something about this?

[lk]

@ariel prado @Elle Ky 
I had similar situation - 

I downloaded the Legacy Content CSV files twice for one space using the Admin Key and received different results. The first download showed two unsupported pages and many errors. The second showed all pages as supported. I am unsure which is correct...

[Elle Ky]

Hi @Ariel Prado @lk

We are actively working on and rolling out some fixes for a timeout issue that was previously reported (see details here: CONFCLOUD-83179).

The above issue was causing two main problems:

• Reports for spaces with a large number of legacy pages could not be generated
• For some reports that were generated, a large number of ERROR statuses appeared

We’re also currently investigating the specific scenario that both of you reported. At this stage, we suspect it may be related to a caching issue, but are further investigating to confirm. Please be assured that we’re prioritizing these fixes to ensure you can use the tool more reliably.

I’ll keep you updated with any new information as it becomes available. I apologize for the inconvenience and appreciate your patience as we work to resolve this.

[Elle Ky]

Hi @lk @Ariel Prado @Trixie Johnson @Frank Kulla 

We’ve deployed a fix for several issues affecting the legacy content export, and we’ve confirmed that the export is now working as expected. To summarize, here are some of the problems reported:

• Reports for spaces with a large number of legacy pages could not be generated
• For some reports that were generated, a large number of ERROR statuses appeared
• For some reports that were generated, there were inconsistent results across different attempts

Note: While you may see the occasional page with ERROR in a report, this should be uncommon. 

We understand how important this tool is for planning the legacy editor transition, and we appreciate everyone who reported the problem and shared details here.

If you’re still seeing any errors or unexpected behavior, please reply here or log a support ticket so we can investigate with your specific site details. We’re monitoring this closely and will continue to refine the experience.

Once again, I apologize for the inconvenience this has caused. Thank you again for your patience and feedback.

[Alexander Ruetzler]

Hello,
We are still experiencing the same error when exporting the report.
I have already created a support request (CES-123866), and the support team has confirmed the bug. However, the fix does not seem to work in our environment, or we might be facing a different issue in our system that is preventing the export from working in many spaces.
Best regards,
Alex

[Stefan Vollmer]

Hello,

We can't export the list due to errors caused by large spaces. How can we resolve this issue?

With only a few weeks to go until the legacy editor is deprecated, it is crucial that we identify the problematic pages.

Given the many unsolved problems we are facing with the new editor, this is unacceptable and unfair to all Confluence customers who have moved from the data center to the cloud. You always say that you address the issues that arise during migration. But ultimately, the most important ones won't be solved!

This is really annoying, and I don't know how we can regain our users' trust in Confluence.

Regards,

Stefan