Step 1: Prepare for the Scaffolding migration
Overview
This document explains how to plan your Scaffolding migration.
Confluence Cloud currently does not support nested macros (See CONFCLOUD-68323).
This means integration with other apps by way of nesting is limited.
This Atlassian documentation lists the Confluence macros that go through changes when converted to the new editor in Confluence Cloud.
Prerequisites
Review the Feature differences document before starting the migration.
Upgrade the Scaffolding app
Update the Scaffolding app to at least version 8.25.0 through the UPM inside the Confluence administration console.
If your pages contain Repeating Data macros, update the Scaffolding app to at least version 8.30.0 or 9.1.0.
Select Administration ( ) > Manage apps.
Search for Scaffolding.
Ensure the app is updated to the most recent version.
Find the non-migratable Scaffolding macros
Ensure that the site search indexes are current.
Choose one of the options below to assess data compatibility between the Scaffolding Data Center and the Cloud:
Option 1: Use the Macro Usage details page
The Macro Usage page can show you the number of Scaffolding macros on your site and the pages that contain them.
Go to Administration > Macro Usage.
Locate the macros under Scaffolding.
Record the number of Scaffolding macros on your site.
Identify how many Scaffolding macros cannot be migrated.
Click each macro link to show you the pages containing the corresponding macro.
Option 2: Use SQL queries
Use the sample SQL queries below to help you gather all pages and templates that contain unsupported Scaffolding macros.
Relevant page titles SQL
This SQL provides a list of impacted page authors and the relevant page titles that currently contain Scaffolding macros that are unavailable in cloud.
Relevant template SQL
This SQL provides a list of impacted page authors and the relevant template titles that currently contain Scaffolding macros that are unavailable in cloud.
Prepare the Scaffolding data for migration
Check the main templates and pages that your users are using and remove the structures that are incompatible with cloud. For information about the unavailable migration scenarios, refer to the Feature differences document.
Create a staging instance and perform a test migration on sample data
Test migration with a staging instance
Test data by creating a sample space
Schedule the migration window
To estimate the time you will need for the migration steps, we recommend reviewing all of the steps before executing.
Depending on the size of the data and the complexity of the existing template configuration, it might take a few hours to complete these steps.
Next Steps
Proceed to with Cloud Migration.
Questions?
Contact us via our support portal.