Known issues when migrating to Scaffolding Forms & Templates Cloud
This document contains all known Confluence structures/data that are not able to be migrated 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 the cloud partially, and the users inside the picker field are not part of your space and, hence, have not migrated to the Cloud along with the space data. This is a known bug with the Atlassian migration tool. | As a workaround
This ensures that all user data are migrated to the Cloud. |
Scaffolding data of a restricted page are not migrated to the Cloud. | This is a known bug with the Atlassian migration tool. | In the Migration Assistant app, a check has been included to track and list down restricted pages:
In Apps vendor checks, you will reach the Restricted pages check section.
Proceed with the migration once the App vendor checks are resolved. |
Global templates are not migrated to the Cloud. | As a workaround, we can manually migrate the global template as a space template and copy it as a global template back into the Cloud. You can follow the detailed step-by-step instructions in the Global Template, which is not automatically migrated to the Cloud page. | |
After clicking the Migrate Scaffolding button, some content or white space appears. | There is hidden content on the page that is wrapped with the following inline style
The Scaffolding Field group macro ignores this. For example, the issue mentioned on the left side is due to the page containing whitespace that is wrapped by the hide inline style: |
|
After Data migration to the Cloud, some pages that contain live templates are empty and do 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 the Server, as parameter type <ac: parameter ac:name="type"> is a required field in the 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.) | Ensure that
|
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.
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.
Each page may have different issues that trigger the error message, thus you will have to identify and resolve them individually. |
Related pages
Support
Contact us via our support portal.