Legacy editor content in the cloud editor
The legacy content macro lets you keep incompatible legacy content on a cloud editor page. It supports a few of the macros and nested content configurations that aren’t available in the cloud editor.
What was the legacy editor?
The legacy editor was the original editing environment in Confluence Cloud, largely mirroring the Confluence server experience. Our cloud editor is now the default in Confluence Cloud and across Atlassian.
The legacy editor was fully deprecated in April 2026. All Confluence content is now viewed and edited in the cloud editor, and pages can’t be reverted to the legacy editor.
Legacy content in the cloud editor
Some pages contain content that originated in the legacy editor, including content migrated from Confluence Server or Data Center. This content is viewed and edited in the cloud editor.
During conversion to the cloud editor, most content converts seamlessly. Legacy editor elements that aren’t directly supported in the cloud editor are preserved inside one or more legacy content macros.
In this example, a legacy page was converted to the cloud editor.
During the conversion, this nested content was placed inside the legacy content macro. This allows the content to be edited and reconfigured without losing any data.
The reason this content wasn’t supported was the use of nested macros. (In this case, the Column macro is inside the Section macro and the Section macro is inside the Panel macro.)
This text (and only the text, not the entire element) can be copied from the legacy content macro to a table or layout outside the macro, delivering the intended visual design but taking advantage of the features of the cloud editor.
Working with the legacy content macro
Editing with the legacy content macro is similar but not identical to working in the legacy editor. Some macros may not work as expected because Confluence only provides support for the cloud editor.
Additional limitations:
Unsupported content – such as nested macros or entire legacy macros – can’t be copied and pasted outside the legacy content macro. You can only copy the text.
Rovo AI features like summarize will ignore all the text inside certain blocks inside the legacy content macro.
Smart links will render as plain URL inside the legacy content macro.
Anyone reading your page will not be able to add an inline comment to content inside the legacy content macro.
You also will not be able to add your own legacy content macro into the cloud editor – it is only used by Confluence’s automatic page conversion process.
Collaborative editing: Because your new page is a cloud editor page, more than one person can edit it at the same time. However, using collaborative editing with the legacy content macro could cause unpredictable results, including loss of data. Make sure only one person is editing before you publish.
Was this helpful?