Possible challenges
Due to the flexibility that Confluence DC offers users, it is not always possible to smoothly migrate all content to Cloud. We are continuing to work on the migration process but some types of content or layouts present more challenges.
Many layers of nested content
Due to the limitations of Confluence Cloud, it is not possible to place many macros inside each other. If your instance has many macros inside other macros the migrated results will not look the same as the original. The results will depend on which macros are placed inside others and how many layers of macros are combined.
It may be necessary to separate macros or consider options to rebuild the functionality using Cloud macros instead.
Nested third-party macros
If the content you are migrating combines macros from other developers inside our macros then we can not predict how these will appear after the migration. If you are having issues with this you may need to separate the third-party macros from your Mosaic macros.
Extensive use of the CSS Style Sheet Macro
When you migrate content to Confluence Cloud a best effort is made by Atlassian to preserve your existing CSS. However, more complicated applications often fail and can have unpredictable results.
Macros that have the CSS Style Sheet applied to them can also become unsupported in the Cloud Editor.