Step 1: Plan your 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 will be limited.
This Atlassian documentation lists the Confluence macros that go through changes when converted to the new editor in Confluence Cloud.Â
Â
Â
Prerequisites
Review the following documents 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.
Click the global admin icon.
Click Manage apps.
Search for Scaffolding.
Ensure the app is updated to the most recent version.
Â
Â
Â
Find all the Scaffolding macros
Ensure that the site search indexes are current.
Choose one of the 2 options below to assess data compatibility between the Scaffolding Server and the Cloud:
Option 1: Use the Macro Usage details page
The Macro Usage page will give you the number of Scaffolding macros on your site and the pages that contain them.
Navigate to Administration > Macro Usage.
look under Scaffolding.
Record:
the number of Scaffolding macros on your site.
identify how many cannot be migrated.
Select the macro links to show you all pages containing those macros.
Â
Â
Option 2: Use the SQL query below
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 will provide a list of impacted page authors and the relevant page titles that currently contain Scaffolding macros that are unavailable in the Cloud.
Â
Relevant template SQL
This SQL will provide a list of impacted page authors and the relevant template titles that currently contain Scaffolding macros that are unavailable in the Cloud.
Prepare the Scaffolding data in server
Check the main templates that others are using and remove the structures that are incompatible with Cloud. The following documentation can help you with this step:
Detailed step-by-step instructions are available on this page -Â Global Template is not automatically migrated to Cloud.
Create a staging instance, and perform a test migration on sample data
Test migration with staging instance
Test data by creating 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 may take a few hours to complete these steps.
Next Steps
Proceed to with Cloud Migration.
Questions?
Contact us via our support portal.
Â
Â
Â