---
title: "Step 1.2: Prepare your Scaffolding data for migration"
canonical: "https://support.appfire.com/space/SCAFC/1827144199/Step%201.2%3A%20Prepare%20your%20Scaffolding%20data%20for%20migration"
format: markdown
---
> Macro (aura-html)

# Prerequisites

- Verify that the site search indexes are current.
- Understand which Scaffolding macros are not migratable. See [Macros not migratable to cloud](https://appfire.atlassian.net/wiki/spaces/SCAFC/pages/1827012708/Macro+differences+between+Scaffolding+Data+Center+and+Scaffolding+Cloud#%3Across_mark%3A-Macros-not-migratable-to-cloud) .
- Understand the supported vs unsupported migration scenarios for each migratable Scaffolding macro. See [Macros migratable to cloud](https://appfire.atlassian.net/wiki/spaces/SCAFC/pages/1827012708/Macro+differences+between+Scaffolding+Data+Center+and+Scaffolding+Cloud#%3Acheck_mark%3A-Macros-migratable-to-cloud).

# Find your Scaffolding macros

Choose one of the options below to assess data compatibility between Scaffolding Data Center and Cloud.

## Option 2: Use SQL queries

Use the sample SQL queries below to help you gather all pages and templates that contain non-migratable Scaffolding macros.

> ℹ️ This example uses PostgreSQL query syntax. You must adjust usage according to your database syntax. Also, to avoid performance issues, limit the outcome to a smaller scope if needed (using limit can help).

# Clean up your content from non-migratable Scaffolding macros

> ✅ Perform this step first on the staging instance if you’ve created one.

1. Go to the pages that contain [non-migratable Scaffolding macros](https://appfire.atlassian.net/wiki/spaces/SCAFC/pages/1827012708/Macro+differences+between+Scaffolding+Data+Center+and+Scaffolding+Cloud#%3Across_mark%3A-Macros-not-migratable-to-cloud).
2. Rework the content to remove the non-migratable Scaffold macros and preserve the data in these macros.

# Unnest the migratable Scaffolding macros

> ✅ Perform this step first on the staging instance if you’ve created one.

1. Go to the pages that contain [migratable Scaffold macros](https://appfire.atlassian.net/wiki/spaces/SCAFC/pages/1827012708/Macro+differences+between+Scaffolding+Data+Center+and+Scaffolding+Cloud#%3Acheck_mark%3A-Macros-migratable-to-cloud).
2. Check the macros structure.
3. Rework the macros structure if necessary to ensure a supported migration scenario for each macro.

# Rework the live templates that are based on Scaffolding templates

> ✅ Perform this step first on the staging instance if you’ve created one.

If you want to migrate pages that are based on a Scaffolding template:

1. Transfer the content of the Scaffolding template to a Confluence page.
2. Edit each Live Template macro:
  1. Change the **Type **parameter from *blueprint *to **page.**
  2. Configure the **Page **parameter with the name of the newly created page.

# Remove any restrictions from the pages with Scaffolding macros

For information on how to remove restrictions from a page and how to view all restricted pages in a space, see the Atlassian [documentation](https://confluence.atlassian.com/doc/page-restrictions-139414.html).

# Remove hidden content

Make sure that there is no hidden content with the `"display:none"` inline styling inside templates and pages.

For example, remove any whitespace that is wrapped by the hide inline style: `<div style=”display:none”><br/></div>`.