Map Connect macro keys to a Forge macro using the migratedFrom property

What's changing Apps adopting Forge from Connect can now use the migratedFrom property in a Forge macro module to map one or more existing Connect macro keys to a single target Forge macro. This allows you to consolidate multiple legacy macros into a new Forge implementation.

Key details of this feature:

• Resolution: Existing Confluence content that uses any of the listed Connect macro keys will automatically resolve to the target Forge macro.
• Scope: The listed keys must belong to the Connect app declared in the app.connect.key field of your manifest.
• Responsibility: The target Forge macro is responsible for handling the configuration and parameters stored by the previous Connect macros. Note that migratedFrom does not transform parameter schemas.
• Exclusivity: A legacy macro key can be claimed by only one Forge macro on a given tenant.
• Current limitation: Forge-to-Forge macro consolidation is not currently supported; this property only supports mapping Connect macro keys to Forge macros.

What you need to do To consolidate your Connect macros, update your manifest.yml file to include the migratedFrom property under the target macro module:

modules:
  confluence:macro:
    - key: consolidated-macro
      migratedFrom:
        - old-connect-macro-a
        - old-connect-macro-b

For more information on migrating macros and handling legacy data, refer to the Adopting Forge from Connect: Migrate macros documentation.

More details

By mapping legacy Connect macro keys to a Forge macro, migratedFrom helps existing Confluence content continue to resolve correctly during the app-user migration to Forge. For background, see CONFCLOUD-84508.