Migrating Deck & Card macros to Cloud

This is a pre-requisite step for Confluence Server & Data Center users who are planning to migrate to Confluence Cloud and have pages that use the Deck of Cards and Card macros from Composition Tabs.

These pre-migration steps in this article are crucial for avoiding clashes with similarly-named macros on Confluence Cloud. On Cloud, there are currently Confluence-native macros which are also called Deck and Card (these are not ServiceRocket macros). More details are available in this bug report.

As part of the migration process, a ServiceRocket pre-migration tool is available which can rename all Deck and Card macros to Tab Group and Tab macros. On Confluence server, Tab Group and Tab macros behave exactly the same way as Deck and Card macros previously do, but with a different name.

Once this process is completed, administrators can then run the Confluence Cloud Migration Assistant to migrate all their content to Confluence cloud.

What happens during this process?

All content that contains  Deck and Card macros, including pages and comments, will be updated to the new macro names, Tab Group and Tab.

Before After


After the macros are renamed, your content will be displayed as it was previously. You can still view, edit and use your updated tabbed content as before on this site.

(info) If new Deck and Card macros are created on your server after the rename process, you will need to run the pre-migration tool again before migrating to Confluence Cloud. For example, If you have completed this process for migration test purposes, but your users continue to add new content with Deck and Card macros, you will need to run the tool again before doing the production migration.

Before you start

Make sure you have updated your Composition plugin to the newest version (5.14 or above) 

Step 1 - Check how many content pages need the macro name update

  1. Go to Confluence Administration Console. Search for the Macro Usage menu.

  2. Search for Composition. You will see the number of contents that contain Deck and Card macros. This will be the number of contents that require the macro name change. 

Step 2 - Run the pre-migration tool

  1. Go to Confluence Admin console.

  2. Under Composition Configuration, select Composition Cloud Pre-migration Tool.



  3. On the pre-migration page, the following information can be seen:



    • Number of contents to update - A count of all content pages that still use the Deck and Card naming convention.
    • After a first run of this process , the page will be updated with the following info
      • Previous run - The date and time of the last run. 
      • Number of contents updated - Accumulated total number of content pages with renamed macros (refer to the screenshot in step 5)

  4. Click Run update. The button will be greyed out, and there will be a spinner to indicate that the macro rename process is in progress.

    Optional: The pre-migration tool runs as a background job so you can perform other tasks in the server. If you need a more detailed status update. y ou can do so by tracking the Confluence log file, atlassian-confluence.logMore details on these steps are available on this KB page

  5. The button is disabled when the process is completed. The page is updated with details such as Previous run  and Number of contents updated.

  6. All pages that have been updated will have a new entry under Page History with the comment "Composition Migrator: Move Deck & Card macros to Tab & Tab Group Macros".



  7. The number of pages that contain Deck and Card macros in the Macro Usage menu will be updated

Step 3 - Proceed with Cloud migration


Your content is now ready for migration with the Confluence Cloud Migration Assistant (CCMA). Follow the instructions that come with the migration tool to bring all your Confluence data to the Cloud.

Step 4 - After migration


After the migration with CCMA, you should see migrated content on Cloud pages that uses the Tab Group and Tab macros. 

Need more information?

Get in touch with us via our support channels.