Understanding what to expect

For long-time users of Confluence DC the experience of using Confluence Cloud can feel unfamiliar. Confluence Cloud offers a lot more features as part of the standard experience but at the same time limits how macros can be used. It's important to be aware of these limits as they impact what is possible to do as part of your migration.

Nesting macros inside each other is extremely limited in Confluence Cloud. The changes to the platform mean that it is no longer possible to combine layers upon layers of macros to build highly custom functionality. Actions that were simple in Confluence DC are no longer an option.

eg Tabs inside Tabs

Because Confluence Cloud works so differently it is no longer possible to apply CSS to all the macros on a page. When you first migrate your content your existing stylesheet settings will be respected as far as possible, but some macros that are combined with the CSS Style Sheet macro may not successfully convert, even if they would convert on their own.

When working on new pages in the Cloud Editor individual style settings need to be applied to each macro, or section of content. Many options are available as standard from the Confluence editor. Inside Moasic macros, there are user-friendly color and style options.

Confluence Cloud has more built-in options for organizing and styling content. This means that many core Mosaic DC macros are no longer required. eg. the iframe macro is now part of Confluence natively. This means that our macro list for Confluence Cloud is much reduced. However, the experience of using our Cloud macros is significantly improved allowing users with lower levels of technical knowledge to easily create well-styled and easy-to-consume content.