--- title: "Troubleshooting Composition Tabs Migration Issues (DC to Cloud)" canonical: "https://support.appfire.com/space/SUPPORT/3413409906/Troubleshooting%20Composition%20Tabs%20Migration%20Issues%20(DC%20to%20Cloud)" format: markdown --- This article addresses several known rendering issues and limitations encountered when migrating **Composition Tabs** from Confluence Data Center to Confluence Cloud. It covers scenarios involving legacy macro placeholders, nested macro incompatibilities, and the "Switch to Tabs" converter tool. ## Summary The article covers four distinct use cases/scenarios related to the migration of Composition Tabs: 1. Tabs appearing as "Legacy macro" placeholders. 2. Content disappearing when `Tab Group` is nested inside `Layout` and `Panel` macros. 3. The "Switch to Tabs" converter tool not appearing on certain pages. 4. Rendering issues when using the `Include Page` macro with tabbed content. ## Use Case 1: Tabs appearing as "Legacy macro" ### Problem After migration, Composition Tabs (Tab Group/Tab macros) appear as "Legacy macro" placeholders and do not render correctly. The tab bar may appear cut off or non-functional. ### Cause Since Composition Tabs Cloud v6.0.0, the app runs as a Forge app. Forge macros do not render in Confluence's legacy editor. Migrated pages initially use the legacy editor, causing the macros to display as placeholders. ### Solution 1. **Manual Conversion:** Edit the affected page. Confluence will prompt you to convert the page to the new Cloud editor. Once converted, the Forge-based tabs will render correctly. 2. **Bulk Conversion:** Use the **"Switch to Tabs"** converter tool provided by the app to transition to the new Cloud-native Tabs macro. - **Reference:** [Switch to the new Tabs macro](https://appfire.atlassian.net/wiki/spaces/CTFCSM/pages/1562542237) ## Use Case 2: Content disappearing in nested Layout/Panel macros ### Problem Entire sections of content become invisible on the page. While the content exists in the page storage format, it does not render visually. ### Cause The `Panel` macro is incompatible when nested within `Tab` or `Tab Group` macros in Confluence Cloud. Specifically, when `Tab Group` macros are nested inside `Layout` and `Panel` macros, the rendering engine fails to display the content. > **Note**: No data is lost; content remains in the page storage format even if not visible. ### Solution 1. To confirm the data is safe, navigate to **More options (⋯)** > **View Storage Format**. 2. In the *Edit* mode, manually remove the `Layout` or `Panel` wrapping around the `Tab Group`. 3. Once the nesting is simplified, the content renders, and you can use the converter tool. - **Reference:** [Incompatible macros when nested within Composition Cloud's Tab and Tab Group macros](https://appfire.atlassian.net/wiki/spaces/CTFCC/pages/1561300405) ## Use Case 3: "Switch to Tabs" converter tool not appearing ### Problem The **Switch to Tabs** conversion tool does not appear on specific pages that contain legacy Composition macros. ### Cause This is a known limitation in the converter detection logic. The tool may fail to identify macros that are deeply nested within other structures, such as `Layout` and `Panel` macros. ### Solution 1. Manually simplify the page structure by removing the outer `Layout` or `Panel` macros. 2. Once the `Tab Group` is no longer deeply nested, the converter tool becomes available. > [!WARNING] > When using the converter on pages with nested macros, **do not click Update** in the editor after conversion. Instead, simply close the editor. Clicking **Update** in certain nested scenarios can lead to tab content loss. - **Reference:** [Switch to the new Tabs macro](https://appfire.atlassian.net/wiki/spaces/CTFCSM/pages/1562542237) ## Use Case 4: Include Page macro complexity ### Problem Pages using the native Confluence `Include Page` macro show broken layouts or missing sections when the included page contains Composition Tabs. ### Cause The `Include Page` macro is incompatible when nested within `Tab` or `Tab Group` macros. If the included page contains broken or legacy `Tab Group` macros, it can cause a rendering overflow that hides subsequent sections on the referencing (parent) page. ### Solution 1. Identify the source page being included. 2. Fix the rendering issues on the source page first by following the solutions in Use Case 1 or Use Case 2. 3. Once the source page renders correctly, the referencing page displays the included content properly. - **Reference:** [Incompatible macros when nested within Composition Cloud's Tab and Tab Group macros](https://appfire.atlassian.net/wiki/spaces/CTFCC/pages/1561300405) ## Related Documentation - [Incompatible macros when nested within Composition Cloud's Tab and Tab Group macros](https://appfire.atlassian.net/wiki/spaces/CTFCC/pages/1561300405) - [Switch to the new Tabs macro](https://appfire.atlassian.net/wiki/spaces/CTFCSM/pages/1562542237) - [Tabs](https://appfire.atlassian.net/wiki/spaces/CTFCC/pages/1561725840) - [Migrate Composition Tabs from Confluence Data Center to Cloud](https://appfire.atlassian.net/wiki/spaces/CTFCSM/pages/1561725231) - [Composition Tabs for Confluence feature differences](https://appfire.atlassian.net/wiki/spaces/CTFCSM/pages/1561201095) - [FAQ on the migration from Composition Data Center](https://appfire.atlassian.net/wiki/spaces/CTFCSM/pages/1561595043)