FAQ: Understanding legacy editor deprecation

How can I share feedback or concerns?

You can share feedback in the following ways:

• Select in the header (next to your profile photo), select “Give Feedback,” and choose “Editor” from the menu.

• Vote or comment on feature suggestions in jira.atlassian.com.

• Participate in the deprecation community group.

Legacy features not available in cloud editor

Why are some features from the cloud editor not available in the legacy editor, and when will missing features be added?

Atlassian is actively working to address the most critical gaps between the legacy and cloud editor so that, by the time of deprecation, nearly all pages can be converted seamlessly with minimal manual effort.

Some features from the legacy editor have intentionally not been replicated in the cloud editor due to technical limitations and our focus on building a modern, scalable editing experience for the cloud.

If there are specific features that are important to your workflows, please search for them under Confluence Cloud suggestions on jira.atlassian.com. Voting and commenting on suggestions helps us prioritize improvements that matter most to you.

How do I know how many pages in a space or site are using the legacy editor or have unsupported content?

Admins can use a script to export a CSV-formated list containing the coversion eligibility of all legacy editor pages. Follow these detailed instructions to use this tool to list the status of all legacy content on your Confluence site.

The tool marks each page with one of these statuses:

• SUPPORTED: Almost no changes after conversion.

• SUPPORTED_WITH_MIGRATION: This page can be converted to the new editing experience; however, you may notice slight changes.

• PARTIALLY_SUPPORTED: Converting this page as-is may result in data loss.

• UNSUPPORTED: Rare case. This would happen if a conversion error occurred.

• UNKNOWN: The eligibility status is dynamically generated whenever a page is published. However, some pages may not have an eligibility status set, particularly if they were migrated or before the editor v2 was added to pages.

We have a large dependency on third-party macros in our content. Will these macros continue to function normally after the legacy editor is deprecated?

Many third-party macros on legacy pages, including those with nested macros, will be converted automatically to the cloud editor using our Legacy Content Macro. However, because the third-party ecosystem is so broad, there may be some edge cases that are not fully addressed by the solution.

If you encounter issues with a specific third-party macro, reach out directly to the app developer and also provide feedback to Atlassian.

If we detect that some pages still have feature parity gaps in the cloud editor, can we keep these pages in the legacy editor?

You can continue using the legacy editor for your pages until Phase 3 of the deprecation. In Phase 2, all eligible pages will be automatically converted, but you’ll still have the option to manually revert them if needed. You can do so by restoring the most recent version of the page before conversion, via the page’s version history. Once Phase 3 begins, all pages will transition to the cloud editor, and reverting will no longer be possible.

Please provide feedback about any critical issues or concerns with the cloud editor so we can better support you and focus on the capabilities that matter most.

Is there any way to control who can convert a page from legacy to the cloud editor?

Anyone with permission to edit a page can convert it from the legacy editor to the new cloud editor. At this time, there isn’t a way to restrict this action to specific users.

My organization has a lot of legacy pages and I’m worried about the timeline of the deprecation. Do I need to take any action to prepare for the legacy editor deprecation?

You are not required to take specific action for this deprecation. These solutions are designed to enable a smooth, automatic conversion. They are focused on ensuring the transition to the cloud editor is as straightforward and smooth as possible.

Eligible legacy pages will be automatically converted to the cloud editor according to the deprecation timeline. Your content will remain viewable and editable after the deprecation, even without manual intervention.

While no action is required for most customers, if you have especially complex legacy pages, it’s helpful to convert eligible pages early and share feedback—your input helps Atlassian refine the solutions and support you better.

Can you disable the “Get the latest editing experience” prompt that encourages users to Update page to get the latest editor experience?

This prompt only appears on pages eligible for conversion to cloud, where no "unsupported" content will be displayed after conversion. These pages are fully compatible with the cloud editor, allowing users to view and edit them seamlessly.

This prompt encourages users to switch to the cloud editor because the legacy editor is unsupported, and soon to be deprecated. While you can still edit existing pages in the legacy editor, converting to the cloud editor gives the best experience and support.

Currently, this prompt can't be disabled, but you can vote and comment on the related suggestion to provide feedback to us and receive status updates. We’d also appreciate understanding your reasons for wanting to disable the prompt, as this helps us better support you and address your concerns.

How do I know if a page is eligible before converting?

Eligible pages are those that can be converted to the cloud editor without displaying any unsupported content after conversion. These pages are fully compatible with the cloud editor, allowing users to view and edit them seamlessly. The introduction of the legacy content macro has made a lot more pages eligible and we’re actively expanding support for additional use cases over the next quarter.

Identifying Eligible Pages:

• “Get the latest editing experience” prompt: When you edit an eligible page, you’ll see a prompt to update your page.

• Checkmark Indicator: While editing in the legacy editor, a checkmark in the bottom left corner indicates eligibility.

Ineligible pages: If a legacy editor page has content that can’t be converted, you won’t see the prompt to convert to the cloud editor. If you try to convert it anyway, you will see a warning that you could lose content.

For additional details, please visit our page on converting pages to the cloud editor.

What happens to my templates that use the legacy editor?

We’re committed to ensuring a smooth transition for customers using legacy editor templates. By Phase 1 of the deprecation, templates using the legacy editor will be convertible to the cloud editor.

Our team is actively working on this capability as a priority for the upcoming quarter, so you can continue to use your templates seamlessly in the cloud editing experience.

My organization has a lot of legacy pages and I’m worried about the timeline of the deprecation. How can I get a head start on converting our pages to the cloud editor?

Site and space admins can enable autoconversion settings at any time to help streamline the transition for their teams. Autoconversion applies to eligible pages—those that can be converted to the cloud editor without unsupported content. Once converted, these pages can be seamlessly viewed and edited in the cloud editor.

Pages containing unsupported content will remain in the legacy editor until support becomes available, at which point they’ll become eligible for conversion. If auto-conversion is already enabled, no further action is needed as we expand support for additional use cases.

To learn more about converting pages, visit the procedure for converting pages.