Known issues when migrating to Scaffolding cloud

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

• choose the option of migrating “All users and groups from the Confluence directory ” once prompted in the CCMA

Scaffolding data of a restricted page are not migrated to Cloud

In the Migration Assistant app a check has been included to track and list down restricted pages:

• update Scaffolding Forms & Templates for Confluence Server to version 8.28.0 or higher

In Apps vendor checks, you will reach the Restricted pages check section.

• download the .csv report of the restricted pages from App vendor checks and un-restrict the pages

Open

Proceed with the migration once the App vendor checks are resolved.

Global templates are not migrated to Cloud

As a workaround, we can manually migrate the global template as a space template and copy it as a global template back in Cloud

You can follow the detailed step-by-step instructions in the Global Template is not automatically migrated to Cloud page.

After clicking Migrate Scaffolding button, some content or white space appears

Open

There is hidden content on the page, that is wrapped with the following inline style

• <div style=”display:none”>

This 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 is wrapped by the hide inline style:

• make sure that there is no hidden content with the "display:none" inline styling inside templates/pages before migrating to Cloud

• remove whitespaces manually 

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 is only 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.

• compare your live templates storage format with the examples on this page

• try editing the live template macro and updating it. Check if this action will add the missing template parameter

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)

Ensure that

• Scaffolding macros are outside nested bodied macros in Server pages before migrating to Cloud

• Scaffolding macros are outside panel macros before clicking the Migrate Scaffolding macro button

•  

Errors/Issues - Bulk conversion

Cause

Solution

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.

Choose Bulk convert again and go through the conversion process one more time.  

• if the "Failed" status still persists, open the pages with the "Failed" status and refer to the Errors/Issues - Individual pages section for the relevant solution

Each page may have different issues that trigger the error message, thus you will have to identify and resolve them individually. 

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.

Choose Bulk convert again and go through the conversion process one more time.  

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. 

Choose Bulk convert again and go through the conversion process one more time. 

• if the "Failed" status still persists, open the pages with the "Failed" status and refer to the “Errors/Issues - Individual pages" section above

Each page may have different issues that trigger the error message, thus you will have to identify and resolve them individually.