Migrating Macros
The following information applies to macros that are not nested. Confluence Cloud does not support nesting. Pages with large numbers of nested macros may not survive a migration unchanged, especially if 3rd party macros are combined with our macros. If this applies to you please contact us for support.
When you migrate a page from DC to Cloud the contents of that page including any macros are also moved. On the published version of the page, the appearance of the macros may change, and some may not be displayed at all. On the edit page, all of the content will be preserved, but the macro will be converted into one of three types.
Migrated Macro Types
Select the macro names to expand for more information.
Cloud
This macro has been converted into a Cloud macro. This could be one of our macros or an Atlassian macro. These macros will work if you convert the page to the Cloud editor.
Unsupported
These macros will not work on the published version of the page in either the Legacy or Cloud editor. The content can be accessed on the edit page.
Legacy
There is no migration path for this macro. You can see and edit the content of the DC version of the macro, but this macro will not be editable if you convert the page to the Cloud editor. Some work as normal in the legacy editor some do not.