---
title: "Migrate the Deck and Card macros to cloud"
canonical: "https://support.appfire.com/space/CT/1562247621/Migrate%20the%20Deck%20and%20Card%20macros%20to%20cloud"
format: markdown
---
> ℹ️ This is a **pre-requisite** step for *Confluence Server & Data Cente*r users who are planning to migrate to *Confluence Cloud* and have pages that use the ** **[Deck of Cards](https://appfire.atlassian.net/wiki/spaces/CTFCSM/pages/1562607623)** **and [ Card ](https://appfire.atlassian.net/wiki/spaces/CTFCSM/pages/1562509352)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 ](https://jira.atlassian.com/browse/CONFCLOUD-70962)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.

<span style="color: #000000">Once this process is completed, administrators can then run the</span> [Confluence Cloud Migration Assistant](https://marketplace.atlassian.com/apps/1219672/confluence-cloud-migration-assistant?hosting=server&tab=overview) <span style="color: #000000">to migrate all their content to Confluence cloud.</span>

## What happens during this process?

All content that contains <span style="color: #000000"> </span>**<span style="color: #000000">Deck</span>**<span style="color: #000000"> and </span>**<span style="color: #000000">Card</span>**<span style="color: #000000"> macros,</span> including pages and comments, will be updated to the new macro names, **Tab Group** and **Tab**.

| **Before** | **After** |
| --- | --- |
| ![image](media://e0e5953f-5329-4966-af79-f4410d83a1c1) | ![image](media://6368483b-c25a-4274-b38b-2e78df8956c6) |

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.

> ℹ️ 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](https://confluence.atlassian.com/upm/updating-apps-273875710.html) to the newest version (5.14 or above)

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

1. <span style="color: #000000">Go to Confluence Administration Console. Search for the </span>**<span style="color: #000000">Macro Usage</span>**<span style="color: #000000"> menu.</span>
2. <span style="color: #000000">Search for </span>**<span style="color: #000000">Composition</span>**<span style="color: #000000">. You will see the number of contents that contain </span>**<span style="color: #000000">Deck</span>**<span style="color: #000000"> and </span>**<span style="color: #000000">Card</span>**<span style="color: #000000"> macros. This will be the number of contents that require the macro name change. </span>  
> Macro (inline-media-image)

<span style="color: #000000"> </span>

## Step 2 - Run the pre-migration tool

1. Go to Confluence Admin console.
2. Under Composition Configuration, select **Composition Cloud Pre-migration Tool**.  
> Macro (inline-media-image)
3. On the pre-migration page, the following information can be seen:  
> Macro (inline-media-image)
  - **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. you can do so by tracking the Confluence log file named "atlassian-confluence.log". More details on these steps are available [on this KB page](https://appfire.atlassian.net/wiki/spaces/CTFCSM/pages/1562280505).

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".  
> Macro (inline-media-image)
7. <span style="color: #000000">The number of pages that contain </span>**<span style="color: #000000">Deck</span>**<span style="color: #000000"> and </span>**<span style="color: #000000">Card</span>**<span style="color: #000000"> macros in the </span>**<span style="color: #000000">Macro Usage</span>**<span style="color: #000000"> menu will be updated</span>

## Step 3 - Proceed with Cloud migration

Your content is now ready for migration with the [Confluence Cloud Migration Assistant](https://support.atlassian.com/migration/docs/confluence-cloud-migration-assistant/) (CCMA). Follow the instructions that come with the migration tool to bring all your Confluence data to the Cloud.  
> Macro (inline-media-image)



## Step 4 - After migration

<span style="color: #000000">After the migration with CCMA, you should see migrated content on Cloud pages that uses the </span><span style="color: #000000">[Tab Group](https://appfire.atlassian.net/wiki/pages/createpage.action?spaceKey=ctfcsm&title=Tab%20Group&linkCreation=true&fromPageId=1562247621)</span><span style="color: #000000"> and</span><span style="color: #000000">[ Tab](https://appfire.atlassian.net/wiki/pages/createpage.action?spaceKey=ctfcsm&title=Tab&linkCreation=true&fromPageId=1562247621)</span>**<span style="color: #000000">[ ](https://appfire.atlassian.net/wiki/pages/createpage.action?spaceKey=CTFCC&title=Tab)</span>**<span style="color: #000000">macros. </span>

### Need more information?

Get in touch with us via [our support team](https://appfire.atlassian.net/servicedesk/customer/portal/11).