Converting this page as-is may result in data loss

[Keith Furnell]

Increasing bugs in the old (MCE) editor are causing us to revisit converting our pages, many of which are afflicted with "Some page elements aren't supported in the new editor". My question is about identifying these elements.

Attempting to preview conversion of such a page yields the following message:

Is the Learn more link meant to go to https://confluence.atlassian.com/confkb/understanding-legacy-editor-element-conversion-in-confluence-cloud-1388151356.html? Instead it's just a link to edit a draft of the same page 😒

https://community.atlassian.com/forums/Confluence-articles/Convert-your-old-pages-to-the-new-editor/ba-p/1292275 implies that unsupported elements will be highlighted in yellow, but this doesn't appear in the preview for us?

What's the best approach for modifying such legacy editors pages to avoid data loss?

[Keith Furnell]

A relevant suggestion has been made here - https://jira.atlassian.com/browse/CONFCLOUD-81426

[Marc - Devoteam]

Hi @Keith Furnell 

using this KB article you can see which macros on pages using the OLD editor are deprecated and should be replaced.

learn-which-macros-are-being-removed 

Also check the KB article understanding-legacy-editor-element-conversion-in-confluence-cloud , this will explain what info can't be converted and what happens with the information

Main documentation on converting can be found here; convert-pages-to-the-new-editor 

[Keith Furnell]

Thanks for these additional references Marc. They do seem to assume you know what macros are used on the page being converted. Often that knowledge is spread between a large set of contributors and/or has been lost with a departed colleague!

I'm wondering if Confluence is able to indicate the specific macros that it's unable to convert for a given page (as implied by the View unsupported content section of Convert-your-old-pages-to-the-new-editor)?

[Marc - Devoteam]

Hi @Keith Furnell 

This was only in the early stages.

The new editor has been fully operation since 2021.

You could reach out to Atlassian Support and see if they can still enable this for you instance.

[Keith Furnell]

Will give this a try and report back if that's an option.