Macros break in the new editor
Keep macros and layout intact when pages move to the new editor.
Migrating to the new editor shouldn’t break pages that worked fine. Here is how to keep them intact.
The symptom
A page built in the legacy editor loses formatting and macros when opened in the new editor, forcing a manual rebuild.
Why Confluence behaves this way
Some legacy macros and layout constructs have no exact equivalent in the new editor and are dropped or degraded during conversion.
The manual workaround — and why it falls short
Teams keep large libraries on the legacy editor for as long as possible, or rebuild broken pages one by one after each conversion.
How Patcher fixes it
Patcher keeps supported macros and layout intact across the editor change, so your existing pages survive the move.
Turn it on
- Install Patcher for Confluence from the Atlassian Marketplace.
- Open Patcher › Patches from your Confluence admin.
- Find Macro-safe editor migration in the list and switch it on.
- Scope it to the spaces you choose, then save — the fix is live immediately.