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

Cause

Solution

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.

This is a known bug with the Atlassian migration tool: https://jira.atlassian.com/browse/MIG-919

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

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.
If there are restricted pages in the space being migrated, the check will notify you.
Download the .csv report of the restricted pages from App vendor checks and unrestrict the pages.
Proceed with the migration once the App vendor checks are resolved.

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:

<div style=”display:none”><br/></div>

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 will only be detected in storage format mode.

The sample storage format of a problematic live template

<p>
  <ac:structured-macro ac:macro-id="3ec078cf-81cb-4e4b-b2a4-7aab9e164e4d" ac:name="live-template" ac:schema-version="1">
    <ac:parameter ac:name="template">Decision Template</ac:parameter>
  </ac:structured-macro>
</p>

The sample storage format of a working live template

<p>
  <ac:structured-macro ac:macro-id="3ec078cf-81cb-4e4b-b2a4-7aab9e164e4d" ac:name="live-template" ac:schema-version="1">
    <ac:parameter ac:name="template">Decision Template</ac:parameter>
    <ac:parameter ac:name="type">template</ac:parameter>
  </ac:structured-macro>
</p>

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 template's 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.
If that does not work, you may need to update the storage format manually with the required 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
Ensure that Scaffolding macros are outside panel macros before clicking the Migrate Scaffolding macro button

Before

After

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.

Click 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.
If you are still unable to find a solution, reach out to our customer support team.

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.

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

If the error message still persists, reach out to our customer support team.

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.

Click 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.
If the error message still persists, reach out to our customer support team.