We have heard your need for Macro migration support and are excited to announce that have recently released a Confluence update that will allow saved Connect macro data to be migrated to Forge. This feature is now in Early Access and we would love to have you take part.
Previously, it was not possible to migrate saved macro modules from Connect to their Forge equivalents. For example, if a Connect-based Confluence macro is removed and upgraded to a Forge-based macro, all existing instances of the macro saved in pages will stop working.
With this change, a Connect app that has been re-written as a Forge app can now transfer saved macro data to the Forge macro extension. The Connect macro extension will be transformed to the Forge macro extension when edited. This allows the Forge successor to a Connect app to transition saved macro instances without disrupting existing customers who have installed the app.
Interested in joining the EAP?
Please reply to this topic with your app name or marketplace link if you are interested to sign up.
Once we have your app key we will reach out if we need to clarify some of the known limitations that your connect macro module is using. For example,
rich-text macro type and
macroId parameter are not supported in Forge macro.
If everything looks good, you will be invited to the dedicated Atlassian Developer Community space. This space is available for you to communicate with Atlassian to provide feedback and bug reports.