IT Admin Change Calendar Atlassian

Confluence Cloud legacy editor is fully deprecated from April 2026

Confluence Cloud legacy editor deprecation phases run January-April 2026. Legacy pages auto-convert and can no longer revert to legacy.

MediumDeprecationAwareness onlyIn effectVerified

Product

Confluence Cloud

Announced

30 June 2025

Effective from

21 January 2026

Completes

1 April 2026

Who is affected

Confluence Cloud sites with pages or templates created in the legacy editor, especially content migrated from Server or Data Center.

Admin roles to involve: Confluence admin, Space admin, Knowledge management owner

Why no action is required

No specific administrator action is required for most customers: Atlassian says eligible legacy pages are automatically converted to the cloud editor during the deprecation timeline. Confluence and space admins may still review legacy-content CSV exports and unsupported macro risk if they want extra transition assurance before the April 1, 2026 full deprecation.

What happens if this is ignored

Legacy content is converted automatically; unsupported portions may remain viewable but not editable, and teams lose the option to revert pages back to the legacy editor.

Why this is rated medium: severity comes from a fixed rubric — this entry is a deprecation that requires no administrator action. Time-to-deadline is shown separately and never changes the rating.

Official source

FAQ: Understanding legacy editor deprecation

Published by Atlassian · Source dated 30 June 2025 · Checked 24 August 2026

Last verified 24 August 2026