Cloud editor auto-migration breaks page formatting on render

[Casper Leung]

Hi,

After the recent auto-migration of our pages from the legacy editor to the cloud editor, we're seeing broken formatting on many pages.

• The page looks correct in the new editor, but the rendered view breaks after saving/updating.
• Reverting to a legacy editor version fixes the page, but doesn't scale across the many affected pages.

This is blocking our team from effectively reading and commenting on affected pages.

Questions:

1. Is this a known bug with the auto-migration?
2. Is there a fix or timeline planned?
3. Any recommended workaround beyond manually reverting individual pages?

Thanks for any guidance!

[Tomislav Tobijas]

Hi @Casper Leung ,

As Arkadiusz said, the behavior you're seeing is a 'known' side effect of the migration and the differences between the editors.
Also, I've tried checking JAC for open bugs, but I couldn't find anything specifically related to what you're seeing 👀

Now, as this could also be site-specific, and based on the complexity and layout of some pages, the recommendation would be to reach out to official support team. Devs could review the backend of these pages where the problem occurs + there could be an actual system issue that could be fixed globally 🤔

Btw, if you haven't already, you can check the main differences between the new and legacy editors here: Differences using Confluence legacy editor and cloud editor 

Cheers,
Tobi

[Arkadiusz Wroblewski]

Hello @Casper Leung

Yep, I’ve seen this exact thing after the legacy - cloud editor auto-migration: the page looks fine while you’re editing, but once you hit publish/save the view/rendered version breaks. It’s usually some legacy layout/macro markup that doesn’t convert 100% cleanly and only shows its “real face” on render.

1) Known bug?

Not one single bug, but yes, this is a known kind of migration issue, especially with older layouts and certain macros.

2) Fix / timeline?

In my experience there’s rarely a clear public timeline. The best way to get traction is to open a support ticket with a couple of “perfect example” pages (links/page IDs), plus screenshots of edit vs view, and call out which macros/layouts are on those pages. That usually helps Atlassian tie it to an existing defect.

3) Workarounds (besides reverting page by page):

Try to spot the pattern (columns/layout sections, complex tables, include-page, panels, etc.) and rebuild just those blocks in the new editor that often fixes the render.

Sometimes switching the page width (wide/full width) helps.

If a page is completely cursed: create a fresh page in the new editor and copy content over in smaller chunks (annoying, but it avoids carrying broken legacy formatting).

And honestly… migrations are always a bit of an art. I’m doing migrations SOLO as one men Army ( JSM/Jira software and confluence) for my own company too, so I definitely feel your pain  best approach is finding the repeatable pattern and fixing it once, instead of chasing pages one by one.

[Casper Leung]

Hi @Tomislav Tobijas and @Arkadiusz Wroblewski 

Thanks to both of you for the quick replies and for confirming this is a known migration issue.

I am currently working with my internal team to get an official Atlassian support ticket opened.

@Arkadiusz Wroblewski, I will try your layout rebuild workarounds in the meantime so our team can keep reading the affected pages. Good luck with your migrations