Atlassian is retiring the Legacy Editor in Confluence Cloud, with full deprecation scheduled for April 2026. This move is part of a broader effort to unify and modernize the editing experience, offering teams improved real-time collaboration, richer content creation, and access to AI-powered features.
What This Means for You
If you use Confluence, a wiki-based platform, the Tufts community can use to centralize and organize information, facilitating collaboration and knowledge sharing within teams, then the retirement of Legacy Editor could apply to you.
If your Confluence site contains pages created with the Legacy Editor, here’s what you need to know:
- Your existing content is safe. Legacy pages will remain viewable, and Atlassian is introducing tools to help transition content.
- Conversion options are available now at the page, space, or site level.
- Pages with complex content (e.g., nested macros) will use a Legacy Content Macro to preserve functionality during the transition.
Key Dates and Phases
- Phase 1 – January 2026 You will no longer be able to create new pages using the Legacy Editor. This includes copying existing legacy pages or using legacy templates.
- Phase 2 – January to March 2026 Any time you view or edit a legacy page, it will automatically convert to the new Cloud Editor.
- Phase 3 – April 2026 The Legacy Editor will be fully deprecated. All pages will use the Cloud Editor, and reverting to the Legacy Editor will no longer be possible.
What You Should Do Now