[Migrators] Starting July 30: New cloud sites will automatically convert eligible legacy pages

[#1]

For Migrators: To follow up on our announcement in the Atlassian Migration Program Community, starting US July 30 / AU July 31, all newly created Confluence Cloud sites will have automatic conversion enabled to convert eligible legacy pages to the cloud editor.

• If your Confluence Cloud site is created on or after this date, any eligible legacy pages will be automatically converted to the new editor upon viewing the page. Pages containing unsupported content will remain in the legacy editor until we add support for those pages—at which point, they will also be automatically converted to the cloud editor.

• This change will apply to both production and sandbox sites.

• You can still revert pages to the legacy version in the More actions (…) menu by selecting Revert to legacy editor. This option will be available until the legacy editor is deprecated.

• This will not impact migrations where content is moved to an existing cloud site that was created before US July 30 / AU July 31. In those cases, the auto-convert setting will not be enabled by default.

FYI: 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 many more pages eligible for conversion, and we’re continuing to expand its capabilities. As more content types become supported, those pages will also be automatically converted.

This update only applies to new Confluence Cloud sites created from US July 30 / AU July 31 onwards. If your production or sandbox site was created before these dates, this change will not affect your site’s settings. However, all sites—regardless of creation date—will still be included in the broader legacy editor deprecation milestones announced for 2026:

• Phase 1 (January 2026): New pages cannot be created in the legacy editor, including copying legacy pages or creating new pages from legacy editor templates.

• Phase 2 (January 2026 - March 2026): Viewing or editing a legacy page will automatically convert it to the cloud editor.

• Phase 3 (April 2026): legacy editor is fully deprecated; all content is viewed and edited in the cloud editor and pages cannot be reverted back to legacy editor.

For more information, learn more about converting legacy pages and check out the FAQ page for additional details about the deprecation.

[chihara]

https://jira.atlassian.com/browse/CONFCLOUD-82319