Page Comparison

Server/DC

Cloud

Migration Path is available

Needed

• Understand the feature differences (see below)

•  between the application for Confluence Server and Confluence Cloud.

• Allocate time for a test migration to understand the steps required to migrate data and complete re-configuration.

• This guide assumes you have successfully migrated

• your Confluence Server data into Confluence Cloud, per Atlassian's instructions (CCMA).  More Atlassian resources are available here.

Versioning/License

Version Support

Minimum migratable Version : 5.14.1

Migrate to Composition Tabs Cloud using the steps at Migration Path.

License

Available through Atlassian Marketplace.

Available through Atlassian Marketplace only. Monthly subscriptions are the default option, however, discounted annual subscriptions are available upon request to our Atlassian Sales team.

Confluence Differences

Integration with other macros

Composition Tabs allows

• Integration with other macros.

• Support of nested macros, which means Composition Tabs macros can easily be nested and integrated with other Confluence native macros or any third-party macros.

Composition Tabs macros in the cloud have the following limitations:

• Does not support nested macros, which means Composition Tabs macros cannot be placed in a nested container (such as inside an expand macro, etc.)

• Due to the above, integration with other macros may be difficult.

Macro Differences Overview

Macros availability

Server

macros

Cloud

macros 

• Only some macros in  are available in Cloud.

• Look out for icons

• highlighting how the data will be migrated.

  •  

• • – Available 

  •  – Unavailable

  •  – Partially available

• Migration for the following Composition

• Tabs macros is possible.

  • Migration for Showcase

• •  macros works out of the box.

  • Deck of Cards & Card can be migrated after performing the

• • mandatory pre-migration steps.

    • These will be converted to Tab Group & Tab (Legacy Editor) macros first

    • Then you can choose to convert to Tabs (New Editor) at a later point

  • Other Composition macros not available in Cloud can still be migrated without data loss, however, the below conditions apply:

    • You may see a blank space where the macros were originally positioned in the documents

    • While these macros do not have any output and the values are ignored in Cloud, all data will be retained. Some of the macros will be coming to Cloud in future releases.

• Find details of each migratable macro below and the differences in terms of behavior once migrated to cloud.

• Card 

• Deck of Cards 

• Cloak 

• Composition Setup 

• Float 

• Page Banner 

• Show Card 

• Showcase 

• Toggle Cloak 

• Showcase

• Tabs

• Tab Group

• Tab

• Pages to Tabs

Macro Differences Breakdown

Supported Server Macro

Cloud Macro (Or closest equivalent ) 

Key Differences

Server

Cloud

• Card

• Deck of Cards

• Tab

• Tab Group

• Tabs

Deck of Cards and Cards

• In Server, Tabbed content is available by calling the Cards macro nested inside the Deck of Cards

• The content of each tab will be added inside each Card macro

Image Added

 Notes about Cloud migration

• Deck of

• Cards &

•  Card can be migrated after performing the

• mandatory pre-migration steps

  • These will be converted to Tab

• • Group &

• •  Tab (Legacy Editor) macros first

  • Then you can choose to convert

• • to Tabs (New Editor) at a later point

  • Refer to Legacy editor vs New editor to understand the background behind each of these versions of Confluence editors.

Tabs, Tab Group, and Tab

• Confluence Cloud has two different editors (see Legacy editor vs New editor for more information)

• Composition Tabs have a different set of macros for each type of editor:

  • Macros available for Legacy Editor: Tab and Tab Group

    • Tab & Tab Group macros can be added to the legacy editor by calling the Tab macros nested inside Tab Group

• • • 
      Image Modified
      

    • The content of each tab will be added inside each Tabs macro

      Expand
      title Take note of the incompatible macros when nested within Composition Cloud's Tab and Tab Group macros..
      Include Page CTFCC:Incompatible macros when nested within Composition Cloud's Tab and Tab Group macros CTFCC:Incompatible macros when nested within Composition Cloud's Tab and Tab Group macros

  • Macros available for New Editor: Tabs

    • Tabs macro can be added to New Editor by calling the Tabs macro, which will call a Tabs editor. Content is added inside this editor

• • • Image Added

  • New editing experience in Confluence Cloud does not support Nested Bodied macros (CONFCLOUD-68323)

  • Tab Group and Tab macros that utilize nested macros mechanism will not work properly in New Editor.

Showcase 

Showcase

Parameters available:

• Title

• Description

• Image URL

• Button Text

• Button Link

Parameters available:

• Title

• Description

• Image

• Emoji

• Button Text

• Button

• Badge

 Notes about Cloud migration

A number of parameters have different names in the Cloud version, but they work the same way as the Server version parameters, Server parameter names will be automatically converted to Cloud parameter names during migration.