Converting Content to the New Cloud Editor
This section helps you visualize how your migrated Content Formatting Macros content may appear when converted to the new cloud editor.
Your Confluence admin has migrated your instance to Confluence Cloud. What does this mean for the existing content that you created with Content Formatting Macros for Confluence Server?
Depending on the macros you used to create your content, your content will be rendered in Confluence’s Legacy editor in three possible ways: with an Atlassian native support macro, with our new Content Formatting Macros Cloud macros, or with one of our legacy macros. These legacy macros preserve your content, but might not behave in exactly the same way as their counterparts on other platforms. We have limited, for example, the customization of these macros (macro parameters) and rather encourage those that want to continue to customize their macros, to do so on our new editor macros. Macros that cannot be migrated render with 'Unknown Macro'.
Atlassian’s conversion tool enables you to transfer this content, or any content created in the Legacy editor, to the new editor, but what happens to your Content Formatting Macros content and macro configuration?
The conversion tool lets you preview changes to your macro content before converting your page to the new editor, after which, you can continue to use all of our macros that are supported in Confluence Cloud. Following migration, your Confluence pages display a banner message confirming whether your page can be converted to the new editor, or if there are formatting issues that should be considered before converting. Once converted, the migrated Server macros are preserved in read-only format.
To help content creators visualize what happens to content when a space is migrated, we have created the following example which illustrates the different types of macro support that are possible. For a list of Content Formatting Macros that can be migrated, see Support for Migrated Content.
In Edit view, you may notice that your macro placeholders look different. That’s because some macros have native support in Confluence Cloud, some are handled by our legacy macros, created especially to preserve your migrated content, some use a single macro for both the legacy and new Cloud editors, while others are not supported in a migration. Refer to Atlassian’s Convert pages to the new editor for specific details on how native support handles each macro when converted to the new editor.
Which editor am I using?
If you are not sure which editor is being displayed when you edit a page in Confluence, the following images may help remind you of the differences. Our macros may behave differently in edit mode according to the editor you are using, but the rendered content is consistent. For more information on the differences between the editors, see Atlassian’s Confluence Cloud Editor Roadmap.
Macro placeholder in legacy editor
Macro placeholder in new editor
To learn more about using the Migration Assistant to migrate from Confluence Server or Data Center to Confluence Cloud, refer to the Atlassian Cloud documentation.