---
title: "Scaffolding migration: Resolving nested macros check failure"
canonical: "https://support.appfire.com/space/SUPPORT/3234398277/Scaffolding%20migration%3A%20Resolving%20nested%20macros%20check%20failure"
format: markdown
---
**Summary:**  
During the migration of **Scaffolding Forms & Templates** from Confluence Data Center to Cloud, the Confluence Cloud Migration Assistant (**CCMA**) may flag a "Nested macros check" failure. This article explains how to identify and resolve nested Scaffolding macros to ensure a successful migration.

**Environment:**

- **Product:** Scaffolding Forms & Templates for Confluence
- **Platform:** Data Center to Cloud Migration
- **Tool:** Confluence Cloud Migration Assistant (**CCMA**)

**Problem:**  
When running a migration plan, the Scaffolding app triggers a warning under the **Nested macros check** section. The migration assistant displays the following message:  
*"We detected that some of your pages have nested Scaffolding macros, which may prevent your data from migrating successfully."*

Affected pages are listed in a downloadable CSV report (e.g., `...scaffolding-nested-macros-checker.csv`).

**Cause:**  
This issue occurs because Scaffolding macros are placed inside other "bodied" macros. Body macros are those that act as containers, such as:

- Panels
- Expands
- Scaffolding macros that can trigger this check include:  
`Text Data`, `List Data`, `Number Data`, `Date Data`, `Table Data`, `Repeating Data`, `Attachment Data`, `Group Data`, `Live Template`, and their sub-macros (`List Option`, `Content Options`, `User Options`, `Attachment Options`, `Label Options`).
- Tables (if used as a container for the macro body)

The Scaffolding Cloud migration tool does not currently support the migration of Scaffolding macros when they are nested within the body of another macro.

**Solution/Workaround:**  
To resolve this check and proceed with your migration, you must move the Scaffolding macros out of the enclosing bodied macros.

1. **Identify Affected Pages:**
  - In the **CCMA** interface, go to the Scaffolding check results.
  - Click **Download report** to get the CSV file containing the list of pages that failed the nested macros check.
  - Open the CSV and locate the specific page titles or IDs.
2. **Edit Affected Pages:**
  - Navigate to the affected page in your Confluence Data Center instance.
  - Enter **Edit** mode.
  - Locate any Scaffolding macros (e.g., `Table Data`, `List Data`, `Text Data`) that are currently sitting inside a Panel, Expand, or another macro's body.
3. **Restructure the Content:**
  - Cut the Scaffolding macro from its current nested position.
  - Paste the macro directly onto the page body, ensuring it is no longer wrapped by another macro.
  - **Note: The Scaffolding migration tool only migrates Scaffolding macros that are at the root level of the page structure (i.e., not wrapped inside another macro's body). If your page layout requires content grouping, place the Scaffolding macro outside the container macro (e.g., Panel, Expand) and arrange the surrounding content independently, rather than nesting the Scaffolding macro inside the container.**
4. **Verify and Refresh:**
  - **Publish** the updated page.
  - Return to the Confluence Cloud Migration Assistant.
  - Click the **Refresh** button on the Scaffolding checks screen.
  - The **Nested macros check** should now show a green checkmark once all listed pages are fixed.

**What happens if you skip this check?**

If you proceed with the migration without resolving nested Scaffolding macros:

- **Scaffolding data on affected pages will not migrate.** The nested macros will be skipped by the migration tool, resulting in missing form data in your Cloud instance.
- **The migration may stall.** Nested macros are a known cause of migrations stalling between 90–97% progress, requiring manual investigation and re-runs.
- **Post-migration remediation is harder.** Once migrated, the affected pages will show empty or broken Scaffolding macros in Cloud. You would need to go back to Data Center, restructure the macros, and re-run the migration for those spaces.

**Recommendation:** Always resolve all nested macros flagged in the CSV report before proceeding with the migration.

**Additional Resources:**

- [Migrate Scaffolding Data Center to Scaffolding Cloud Checklist](https://appfire.atlassian.net/wiki/spaces/SCAFC/pages/1356071105)
- [Scaffolding Migration Guide](https://appfire.atlassian.net/wiki/spaces/SCAFC)