Confluence Cloud migrators - you can now bulk convert legacy editor pages to the new editor!

[#1]

Hey community!

My name is Steven Bao, and I’m a Product Manager on the Confluence Cloud team. We’ve been working on the capability to bulk convert legacy editor content to the new editor and are excited to announce that we are in process of rolling out!

If you are a recent migrator from server/DC, you may have noticed that your migrated content stayed in the legacy editor. Today, you are able to convert pages from the legacy editor to the new editor, but only on a single page basis. With this functionality you will be able to bulk convert eligible content (some content, such as nesting is not supported in the new editor) from the legacy editor to the new editor on a space or site basis.

This will allow you to more easily take advantage of the many new functionalities the new editor has as well as set you up for the exciting future additions planned!

How do I enable this?

Bulk Convert Eligible Legacy Pages in a Space

1. You must be a space admin to enable this at a space level. Navigate to:

   1. Space Settings → Manage Space → Convert Pages

   2. Toggle on “Convert Pages Automatically”

Bulk Convert Eligible Legacy Pages in a Site

1. You must be a site admin to enable this at a site level. Navigate to:

   1. Site Administration → Further Configuration

   2. Check “Convert Pages Automatically”

What do users see?

When this setting is enabled, all eligible pages in the space/site will display using the new render in view mode, as well as the new editor in edit mode. Users will receive a notification of this conversion the first time they land on a page that was bulk converted.

Reverting Changes

• Users will be able to revert the change from the dropdown menu in the top right hand corner if the page has not been published (in both view and edit). If the page has been published, they will need to revert from page history.

• This change is also able to be reverted at the space or site level, but will not revert pages that have been published since bulk conversion.

Eligibility

Eligibility mainly depends on if the page does not contain nested bodied macros, as they are incompatible with the new editor. There are also some minor changes during conversion to certain macros described here: https://support.atlassian.com/confluence-cloud/docs/convert-pages-to-the-new-editor/

At this time, we will also be excluding conversion of pages created in cloud using the legacy template or pages that were converted to the fabric editor but reverted as we do not want to convert pages that are desired to be in the legacy editor at this point.

Try it out

We’d love for you and your teams to try this functionality out and and let us know what you think in the comments below.

If you don't yet see this option today, you'll see it coming to your instance within the next few weeks. As a reminder, you must be a space admin to enable this on a space level, or a site admin to enable this on a site level.

For more information about migrating to cloud, visit the Atlassian Migration Program, and get started on creating a plan now!

[Steve Rhodes]

Too many missing features from the old editor not yet implemented on the new for this to be considered when importing data en masse. Atlassian has has years to restore the features that have been removed. These are just a handful of the important ones that need fixing.

https://jira.atlassian.com/browse/CONFCLOUD-67554 Resize image by pixel on new editor
https://jira.atlassian.com/browse/CONFCLOUD-67862 Bring back the option to add macros within a numbered or bulleted list
https://jira.atlassian.com/browse/CONFCLOUD-65749 Ability to add Images from web in the new editor
https://jira.atlassian.com/browse/CONFCLOUD-67648 Additional options for page layouts

[Mark Benson]

I'd second Steven's comment.

Post migration to cloud we've had many users break pages by not really understanding the implications and just converting to the modern editor without verifying first.

We're pretty heavy on formatting addons/plugins and from my experience most tend to not play nice when imported from server/dc especially when mixed/nested - eg. Tabs or similar with other elements embedded within them. Most of the time it breaks the pages catastrophically and you're left with big empty sections.

There's about a 0% chance I'd consider trying to do this in bulk, it'd probably break 50% of our content or more.

[Scott Seiter]

Converting from the legacy editor to the 'new' cloud editor is one case where new is NOT better. My advice to site admins, please DO NOT CONVERT pages to the new editor until the 'new' editor catches up to the 'legacy' editor.

To be fair, there may be great features in the new editor and I expect the Atlassian team will eventually get it fully functional, but until then, it seems hard to justify pushing a new editor that doesn't have  the fundamentals down yet.

============

If you need some examples, consider this post or consider that a seemingly fundamental task of indenting a bulleted or numbered list from the left margin doesn't seem to work in the 'new' cloud editor.

'New' Editor: Note that the bullets and numbers hug the left margin

'Legacy' Editor: Bullets and numbers sit nicely indented

The ironic thing is that it appears this comment board will allow the desired indenting ;)

asdfasdf

• sdf

asdfasdf

1. sdf

I cheer the Atlassian team on in making the new editor great, yet I'd say it's a bit early yet to push to the masses (even though it appears that's what's being done).

Best wishes all!

Scott