Legacy Editor vs Cloud Editor
When you are involved in a migration it is important to understand the difference between the Legacy Editor and the Cloud Editor.
Legacy Editor
When you migrate pages from a DC instance they are first created in pages that use the legacy editor. This is so that more of the features from DC can be preserved. When you are in view mode, it can be hard to tell the difference. At the top of all legacy pages, there is a label to tell users about the page.
The legacy editor is closer to the DC editor in terms of functionality. That means there are fewer options and you don’t get all the benefits of using Confluence Cloud.
An example of this is our Tabs macro. We have made a lot of improvements to our Cloud Tabs macro, this allows you to create all your tabs inside a single editor giving a quicker and easier experience. But this version of Tabs is not available in the Legacy Editor.
Nesting of macros is supported to a reasonable level, in the legacy editor. But nested content will not convert to the Cloud Editor.
For pages you don’t intend to update often, it may be no problem to leave them in the legacy editor. If you have pages that are heavily used and regularly updated it would be better to convert them to the Cloud Editor to make sure you get all the latest functionality of Confluence Cloud.
Cloud Editor
The Cloud Editor is the standard editor you get when you use Confluence Cloud. When you create a new page this is the editor you will be given. It has all the most up-to-date options and access to all recent macros and layouts.
Using the Cloud editor means that there are limitations on the nesting of macros. If you have migrated pages with many layers of nesting you may not be able to convert the page to the Cloud Editor without making significant changes.
Converting a page
You can convert a page from the Legacy Editor to the Cloud Editor. The bottom ribbon of Legacy Editor pages has a button that allows you to preview the page in the Cloud Editor.
You do not have to convert to the Cloud Editor after you preview the contents. If you do convert and are unhappy with the result you can use the page history to return to a version that used the legacy editor.
Check Atlassian’s documentation for more information about the conversion process.