Behavior of Deprecated Macros Post-Migration from Confluence Data Center to Cloud via CCMA

Question

Hi Atlassian Community,

I'm currently migrating from Confluence Data Center to Confluence Cloud using the Confluence Cloud Migration Assistant (CCMA), and I've come across the following deprecated macros:

* panel

* noformat

* loreipsum

I referred to this Atlassian support document, which states these macros are not supported or are being removed in Confluence Cloud. While alternatives are suggested in the document, I’m unclear about the post-migration behavior of these macros.

My questions:

* How are these unsupported macros rendered in Confluence Cloud after migration? Are they displayed as broken content, static content, or something else?

* Is there any automatic conversion or replacement of these macros by the migration tool (CCMA) to their suggested alternatives?

* If not, what is the recommended process to handle these macros post-migration—should we manually replace each instance, or is there a tool/script to assist with this cleanup?

Appreciate any guidance or real-world experience from anyone who has encountered similar macro issues during migration.

Thanks in advance!

Trudy P Claspill · Accepted Answer

Hello @umashri

As per this documentation:

https://support.atlassian.com/migration/docs/what-migrates-with-the-confluence-cloud-migration-assistant/

...under the heading "What isn't migrated":

* Macros:

* User-created macros: Need to be recreated as Forge or Connect apps

* Legacy editor macros: Some macros only work in legacy editor, not in the new cloud editor

* Deprecated macros: Some macros have been removed from cloud and won't migrate

* Learn which macros are being removed:These macros have been removed from the cloud and, therefore, can’t be migrated from the server or Data Center.

The macros you mentioned are all supported in the Legacy Editor in Confluence Cloud. Pages currently are initially migrated to use the Legacy Editor, and the option to convert them to the new Confluence Cloud Editor is presented when the page is edited in Cloud.

You can learn more about the post-migration page conversion option here:

https://support.atlassian.com/confluence-cloud/docs/convert-pages-to-the-new-editor/

That does an automated conversion of macros where possible, and indicates if a page contains macros that can't automatically be converted. The above page includes information about a "Legacy Content Macro" that has been created to help preserve content of unsupported macros in the conversion process.

In 2026 the Legacy Editor is being deprecated and the New Editor will become the only editor available in Confluence Cloud. For more information about that and the automatic conversion of pages refer to this:

https://community.atlassian.com/forums/Confluence-articles/The-Legacy-Editor-is-being-deprecated-in-Confluence-Cloud-Here-s/ba-p/3046832

Adriian Semotiuk · Accepted Answer

Hi @umashri 
I am developer at Wombats Corp, and i find this question very interesting, so I tried it on my own.
I created page in DC with following macros

* panel
* noformat
* loremipsum

As @Trudy P Claspill said, after migrating to Cloud, all of those macros rendered successfully in both the Legacy Editor and after updating the page. However, in the case of loremipsum, I couldn't find it in the macro browser.
So while the macro still works, it can’t be added to new pages through the macro browser.

If you have any custom User Macros that you'd like to migrate to Confluence Cloud, please note that Connect is no longer the recommended solution.
Instead, you should use Forge or third-party apps—such as our product User Macro for Confluence Cloud. To assist with migrating User Macros from Data Center, we've developed a tool called User Macro Exporter