Learn more about how our Cloud macros can preserve content created with Content Formatting Macros for Confluence Server or Data Center. If you are working with spaces or pages migrated from Confluence Server or Data Center, you will be working with Confluence’s Legacy editor. 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 Content Formatting Macros for Confluence Server 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 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

To support our customers that are migrating from Server or Data Center to Cloud, we have, where possible, added 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, 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. Our legacy macros are always rendered in Confluence’s legacy editor. The table below outlines the Server version macros, their corresponding macros rendered following a migration to Confluence Cloud, and their editor availability.

 Macro Compatibility Table

CFMC Server/DC Macro

Native Atlassian support in Confluence Cloud

CFMC Cloud macro

Notes

Alert


Align


Background Color


BibTeX Display Table


BibTeX Referencing


Button Group


Button Hyperlink


Center Content


Clickable


Colgroup Tag


Copyright


Dialog


Div


Fancy Bullets


Footnote

New editor only; cannot be migrated

Footnotes Display

New editor only; cannot be migrated

Highlight


Horizontal Nav


HTML Image


Iframe


LaTeX


Lozenge


Message Box


Paragraph


Pre Tag


Privacy Mark


Privacy Policy


Progress Bar Container


Progress Bar Hyperlink Step


Registered Trademark


Restful Table


Rollover


Round Rectangle


Search Box


Service Marks


Span Tag


Strike Text


Style Sheet


Table Layouts


Tabs Container


Tabs Page


Tooltip

New editor only; cannot be migrated

Trademarks


Working with migrated content

In the following example, content containing the Tabs Container and Tabs Page macros was migrated from Confluence Server to Cloud.

An example of a rendered Tabs page and Tabs Container macro.

An example of placeholders for the Tabs Page and Tabs Container macro.

To see how your macro content was rendered when migrated, follow the steps below.

  1. Navigate to a page that was migrated. Your page content is displayed.

  2. Click the Edit icon. The page is displayed in Edit mode with Confluence’s legacy editor.

  3. Macro placeholders are displayed. If legacy macros were used to preserve the content, legacy is included in the macro name, for example Tabs Page Legacy.

    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.

  4. To remove the macro from the page, click the macro placeholder, then click Remove.

Using macros with the legacy editor

When editing migrated pages, the legacy editor is displayed. 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.

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.

Legacy editor

The tools available in the Legacy Editor.

Macro placeholder in legacy editor

A Button Hyperlink macro placeholder in Legacy Editor.

New editor

The tools available in the New Editor.

Macro placeholder in new editor

An example Button Hyperlink 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.