Known issues when migrating to Scaffolding cloud
This document will contain all known Confluence structures/data that are not migratable to Cloud, along with possible solutions and workarounds.
Errors/Issues - Individual pages
|Missing users inside the Scaffolding user picker field|
This issue arises if you are migrating to cloud partially, and the users inside the picker field are not a part of your space, and hence not migrated to Cloud along with the space data.
|As a workaround, choosing the option of migrating “All users and groups from the Confluence directory ” once prompted in the CCMA will ensure that all user data are migrated to Cloud.|
|Scaffolding data of a restricted page are not migrated to Cloud||This is a known bug with the Atlassian migration tool: https://jira.atlassian.com/browse/MIG-837|
Install the following Scaffolding OBR to work around this issue. then start the migration
Alternatively, make sure that pages do not contain restrictions in server before migrating to Cloud.
|Global templates are not migrated to Cloud||This is a known bug with the Atlassian migration tool: https://jira.atlassian.com/browse/MIG-190|
As a workaround, we can manually migrate the global template as a space template and copy it as a global template back in Cloud
Follow this document for more detailed step-by-step instructions Global Template is not automatically migrated to Cloud.
After clicking Migrate Scaffolding button, some content or white space appears
There's hidden content on the page, that's wrapped with the following inline style: <div style=”display:none”>. which is ignored by the Scaffolding Field group macro.
For example, the issue mentioned on the left side is due to the page containing whitespace that's wrapped by the hide inline style:
|After Data migration to Cloud, some pages that contain live template is empty and does not show the Migrate Scaffolding button|
Scaffolding Cloud did not recognize the live template content as a live template as it's missing a parameter value type.
The missing parameter value will only be detected in storage format mode.
The sample storage format of a problematic live template
The sample storage format of a working live template
It's currently unclear how customers may have this data on Server, as parameter type <ac:parameter ac:name="type"> is a required field in Scaffolding server.
After clicking the Migrate Scaffolding button, you see Unsupported Content error messages when there are Scaffolding macros inside a nested-bodied container.
|This is a Confluence Cloud limitation as it does not allow nesting macros inside a bodied macro (such as panel macros, nested tables, expand macro, etc)|
Errors/Issues - Bulk conversion
The "Bulk Convert tool" option does not appear on pages that need macro conversion, only single-page conversion is possible.
The Convert Scaffolding Server Macro under Manage Space does not show as well.
|The page or the parent page has page restrictions.|
Make sure to set "No restrictions" on all the pages in the space before proceeding with the migration.
After bulk converting the pages, you notice that the page status shows "Failed".
|The error message is generic to only notify the user that there is an issue with the migrated Scaffolding macros. It does not specify the exact issue that triggered this error.|
During the bulk conversion, you notice that the migration has stopped with the message"Critical error encountered".
|Response time from Confluence REST API being slower than usual or taking too much time to launch the bulk conversion process.|
After performing a bulk conversion, you notice a warning with the following message:
|You have a number of pages that have failed to convert or have not been converted.|