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 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:
|
---|
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.
Info |
---|
Or access the macro usage information via the shortcut <base-url>/admin/pluginusage.action . |
look under Scaffolding.
Record:
the number of Scaffolding macros on your site.
identify how many cannot be migrated.
Info |
---|
In this example, the ones marked will not be migrated to the Cloud. |
Select the macro links to show you all pages containing those macros.
Expand | ||
---|---|---|
| ||
|
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.
Expand | ||
---|---|---|
| ||
|
Prepare the Scaffolding data in server
Info |
---|
Know your Scaffolding structure and data in server to anticipate incompatibilities in Cloud after migration. As the Scaffolding server is more versatile than Scaffolding Cloud, it is important that admins understand what's inside their scaffolding structure, and anticipate what is not migratable. |
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:
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 Cloud.
Create a staging instance, and perform a test migration on sample data
Tip |
---|
This is a recommended best practice step. |
Test migration with staging instance
Expand | ||
---|---|---|
| ||
|
Test data by creating 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 take a few hours to complete these steps.
Tip |
---|
We advise you to schedule a maintenance window in your organization to perform the migration. |
Next Steps
Proceed to with Cloud Migration.
Questions?
Contact us via our support portal.