3rd party macros misinterpreted as Confluence native macros after migration to cloud

Issue Summary

3rd party macros were misinterpreted as Confluence native macros after migration to cloud.

Steps to Reproduce

The ServiceRocket team is looking into the Cloud migration path for a specific macro, Tabs, for one of our apps, Composition Tabs for Confluence. This app exists both in Server and Cloud. Its primary function is to provide a tabbed view of Confluence content. In Server, the macros are called Deck and Card macros.
 
We understand that in Cloud, Atlassian owns macros with the same name but different display outcome. Maybe as a means to provide a placeholder for inexistent corresponding macros in Cloud.

Deck macro:

 
Card macro:
 

 
This results in migrating customers unknowingly converting to Atlassian macros, due to the name share. This could be a challenge for us as we would love to retain our migrating server customers using the Deck and Card macros or at least give them an option to choose.

Expected Results

ServiceRocket macros should be migrated to cloud as the same corresponding ServiceRocket macros in server.

Actual Results

ServiceRocket Deck macro and Card macro were migrated to cloud as Confluence native macros due to duplicate naming/ID.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available