Migration to Cloud

We have worked closely with Atlassian and their new cloud editor to help you move your valuable Confluence content to Confluence Cloud. Many of our server version macros are directly supported in a migration from Confluence Server to Cloud simply by using Atlassian’s migration assistant. We have also developed Cloud versions of some of our Server macros allowing you to preserve and modify your content and we have an ambitious roadmap to bring more of your favorite macros to Cloud. If you already use Content Formatting Macros for Server or Data Center and are moving to Cloud, please be aware that the Cloud versions of our macros do not support macro parameters such as ID, Class, and Custom Icons.

Is there a macro that you would like to see supported in Cloud? Do you have an idea for a new macro? We want to hear from you! Please forward your requests and ideas via our customer support portal or our app feature feedback page.

If you are a current Server customer moving to Cloud, the table below helps you identify what is supported and what you can expect when you migrate your spaces. Atlassian also supports a path from their legacy cloud editor to the new editor by way of page conversion. Content creators can find more information on how our migrated content is rendered in the new editor on the Converting Content to the New Cloud Editor page.

Which macros can be migrated

Not all of our server macros are supported in a migration to Confluence Cloud. The table below identifies which macros are supported and whether it is through native Confluence support or through our new Content Formatting macros. We have also added, where possible, legacy versions of our macros. These macros preserve your content, but might not behave in exactly the same way as their counterparts on other platforms. We have limited the customization of these macros (macro parameters) and rather encourage you to continue to customize your content using our new editor macros. Our legacy macros are always rendered in Confluence’s legacy editor. 

 Macro Compatibility Table

CFMC Server/DC Macro

Native Atlassian support in Confluence Cloud

CFMC Cloud macro



Legacy macro available for migrated content 


Background Color

BibTeX Display Table/Summary

BibTeX Referencing

Button Group

Button (Hyperlink)

Center Content


Colgroup Tag


CSS Style Sheet



Fancy Bullets


For new content only; cannot be migrated

Footnotes Table

For new content only; cannot be migrated


Horizontal Nav

HTML Comment

HTML Image



List Item(tick)(error)Legacy macro only; Atlassian's macro is known to add <p> tags to content


Message Box

Ordered List(tick)(error)Legacy macro only


Pre Tag

Privacy Mark

Privacy Policy

Progress Bar Container

Legacy macro only

Progress Bar (Hyperlink Step)

Registered Trademark

Restful Table


Round Rectangle

Search Box

Service Marks

Span Tag

Strike Text

Table Layouts

Tabs Container

Legacy macro only

Tabs (Page)

Legacy macro available for migrated content 


For new content only; cannot be migrated


Unordered List(tick)(error)Legacy macro only

Legacy macros are read-only. If they contain body content, you can amend the content or copy it to reuse elsewhere. You cannot add other macros to legacy macros.

Using macros with the legacy editor

Until your content is converted to the new editor, migrated pages display with Confluence's legacy editor. To add macros to a Confluence page using the legacy editor select Insert > Other Macros in the Confluence editor. Alternatively, use the keyboard shortcut by typing { and the beginning of the macro name to display a list of matching macro names. To learn more about standard macro use in Content Formatting Macros for Confluence Cloud, see Macros Overview.