Overview
This document explains how to plan your Scaffolding migration.
Note |
---|
Confluence Cloud currently does not support nested macros (See CONFCLOUD-68323). |
This means integration with other apps by way of nesting will be is limited.
Info |
---|
This Atlassian documentation lists the Confluence macros that go through changes when converted to the new editor in Confluence Cloud. |
On this page:
|
---|
Prerequisites
Review the
/wiki/spaces/DEVSCAFC/pages/1534558568 document before starting the migration
.
Unsupported server scenarios upon migrations - Nesting Table Data
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.
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 2: Use
SQL
queries
Use the sample SQL queries below to help you gather all pages and templates that contain unsupported 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).
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.
Expand | ||
---|---|---|
| ||
|
|
|
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.
Expand | ||
---|---|---|
| ||
|
|
Prepare the Scaffolding data
in serverfor migration
Check the main templates and pages that
othersyour users are using and remove the structures that are incompatible with
Cloud. The following documentation can help you with this step:Due to CCMA Limitations: Global templates will not be migrated automatically and have to be manually migrated instead. (Bug report: MIG-190 - Consider making the Confluence Assistant migrating Global Templates)
Tip |
---|
As a workaround, you can copy all Global Templates manually into Space Templates before the migration, in order to migrate them to Cloud. You may copy the migrated templates back to Global templates after the successful migration. |
Detailed step-by-step instructions are available on this page - Global Template is not automatically migrated to Cloudcloud. For information about the unavailable migration scenarios, refer to the /wiki/spaces/DEVSCAFC/pages/1534558568 document.
Create a staging instance
,and perform a test migration on sample data
Tip |
---|
This is a recommended best practice step. |
Test migration with a staging instance
Expand | ||
---|---|---|
| ||
|
Test data by creating a sample space
Expand | ||
---|---|---|
| ||
|
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 might take a few hours to complete these steps.
Tip |
---|
We advise you It’s a best practice to schedule a maintenance window in your organization to perform the migration in your organization. |
Next Steps
Proceed to with
Cloud Migration/wiki/spaces/DEVSCAFC/pages/1534297749.
Questions?
Contact us via our support portal.