---
title: "Switch to the new Tabs macro"
canonical: "https://support.appfire.com/space/CT/1562542237/Switch%20to%20the%20new%20Tabs%20macro"
format: markdown
---
> Macro (aura-html)

## Purpose

With the arrival of the [new editing experience](https://confluence.atlassian.com/confcloud/confluence-editing-improvements-945107733.html?__hstc=72543820.4e76311f874131a99198a462418b615c.1662100942946.1675918285968.1675921653570.374&__hssc=72543820.58.1675921653570&__hsfp=1594022185) in Confluence Cloud that does not support nested bodied macros ([CONFCLOUD-68323](https://jira.atlassian.com/browse/CONFCLOUD-68323?__hstc=72543820.4e76311f874131a99198a462418b615c.1662100942946.1675918285968.1675921653570.374&__hssc=72543820.58.1675921653570&__hsfp=1594022185)), Tab Group and Tab macros cannot work properly in the new editor.

To continue using tabs and enjoy future improvements, we recommend converting to the new Tabs macro available in the page editor. It offers an all-new macro tailored to work with the new editing experience in Confluence Cloud, while also providing backward compatibility with the legacy editor.

> ℹ️ If you recently migrated your pages from data center, all your migrated pages arrived in cloud with the legacy editor.

## Answer

You can keep using Tab and Tab Group macros if you don't plan to [convert your pages](https://support.atlassian.com/confluence-cloud/docs/convert-pages-to-the-new-editor/?__hstc=72543820.4e76311f874131a99198a462418b615c.1662100942946.1675918285968.1675921653570.374&__hssc=72543820.58.1675921653570&__hsfp=1594022185) to the new editor. 

> ℹ️ Tab and Tab Group macros are quite different than their data center counterpart. Take note of the list of the [Incompatible macros when nested within Composition Cloud's Tab and Tab Group macros](https://appfire.atlassian.net/wiki/spaces/CTFCC/pages/1561300405).

However, if you plan to or have converted to the new editor, consider switching to Tabs macros because Tab and Tab Group macros will not work properly in the new editor.

You can convert content from the existing Tab Group and Tab macros to the new Tabs macro automatically or manually.

## Moving content automatically

Things to know before doing the conversion:

- Some macros inside the tab may be lost. See here for a list of macros that [Tabs macro support](https://appfire.atlassian.net/wiki/spaces/CTFCC/pages/1561725840).
- The coversion process creates a new version of this page.
- If the content does not seem to render properly after the conversion, you can always restore the previous version of the page via [Page History](https://support.atlassian.com/confluence-cloud/docs/create-edit-and-publish-a-page/?__hstc=72543820.4e76311f874131a99198a462418b615c.1662100942946.1675918285968.1675921653570.374&__hssc=72543820.58.1675921653570&__hsfp=1594022185).
- To enjoy the full benefit of the Tabs macro, you can convert the page itself to the new editor. This is a separate process that is done after the conversion to Tabs macro.

### Steps to convert content automatically

1. Find a page that contains Tab and Tab Group macros. You can see the following *Legacy macro* warning on the page.
  
2. Click the warning to reveal more information and to access the converter tool.
  
3. Click **Switch to Tabs**.  
The conversion process may take a while to complete.

> ℹ️ After the Tab and Tab Group macros are converted to the Tabs macro, if you edit the page, you will see the JSON text format used by the new editor. **This is expected behavior** because you are still in the legacy editor. While we recommend you convert the page to the new editor (see steps below), there may be reasons to continue using the legacy editor. For example, when the tabs contain certain third-party macros that are not compatible with the new editor.

4. If you want to update your tabs, click the macro area and click **Edit** in the dialog.

### Steps to convert the page to the new editor (recommended)

As long as this page is in the legacy editor, it will always show the JSON text format. Follow these steps to convert the page to the new editor, and you will not see the JSON anymore.

1. Near the bottom of the page, there is an option to convert the page to the new editor. Click **Preview page**.
2. In the dialog, click **Preview your page first.**
3. Click either **Preview** or **Convert page**.
  
4. After the page is converted to the new editor and published, click **Edit** and verify that you can see the content of the [Tabs](https://appfire.atlassian.net/wiki/spaces/CTFCC/pages/1561725840) macro.

## Move content manually

1. Edit the page.
2. Copy the content from inside the Tab macro.
3. Create a new Tabs macro. Either select from the macro browser, or use the keyboard shortcut ( "`/"` for new editor or "`{"` for old editor).  
**New editor**:
  **Old editor**:
4. In the Tabs editor window, paste the content:
  Note that some formatting may be lost.
5. Repeat the copy-and-paste steps for all your tabs.
6. Save the macro and the page. Remove the old Tab Group and Tab macros if necessary.