Composition Tabs for Confluence Feature Differences

Composition Tabs for Confluence Feature Differences

Use this page to compare Composition Tabs for Confluence Data Center and Cloud before planning your migration.

Migration path

Composition Tabs macros migrate from Data Center to Cloud in three stages.

License migration is required for app data migration. Before you migrate:

  • Confirm that your Data Center app is version 5.14.1 or later.

  • Complete a test migration to understand the migration steps and required reconfiguration.

  • Migrate your Confluence Data Center content with the Confluence Cloud Migration Assistant before migrating app data.

  • Review Atlassian migration resources for additional planning guidance.

  • Follow Migrate Composition Tabs from Confluence Data Center to Cloud for the app migration procedure.

 

Cards and tabs macro differences

Data Center's Deck of Cards and Card macros convert automatically to Cloud's Tab Group and Tab macros. See Migration path above for how the Legacy and New editor stages work. Deck of Cards and Card macros require additional pre-migration steps; see Migrate the Deck and Card macros to Cloud.

The New editor doesn't support nested body macros; see Atlassian's new editing experience and CONFCLOUD-68323. See Incompatible macros when nested within Composition Cloud's Tab and Tab Group macros before converting nested content.

Data Center macro

converts to

Cloud macro

Data Center macro

converts to

Cloud macro

Deck of Cards

Tab Group

Card

Tab

Showcase macro differences

The Showcase macro migrates automatically. Some parameter names change in Cloud, but the migration converts the Data Center parameter names automatically.

Data Center parameter

converts to

Cloud parameter

Data Center parameter

converts to

Cloud parameter

Title

Title

Description

Description

Image URL

Image or Emoji

Button Text

Button Text

Button Link

Button

Not available

Badge (new in Cloud)

Macros without Cloud equivalents

These Data Center macros don't have Cloud equivalents, though support for some is planned in future Cloud releases. Their data is retained during migration, but the macros won't produce output in Cloud. You may see a blank space where a macro was originally placed:

Related pages