--- title: "Known issues when migrating to Scaffolding cloud" canonical: "https://support.appfire.com/space/SCAFS/477604479/Known%20issues%20when%20migrating%20to%20Scaffolding%20cloud" format: markdown --- 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. > ℹ️ > ℹ️ - [https://jira.atlassian.com/browse/MIG-919](https://jira.atlassian.com/browse/MIG-919?__hstc=72543820.4e76311f874131a99198a462418b615c.1662100942946.1677542271684.1677550101602.435&__hssc=72543820.22.1677550101602&__hsfp=179215543) | As a workaround
- choose the option of migrating “*All users and groups from the Confluence directory* ” once prompted in the CCMA
> ✅ 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. > ℹ️ > ℹ️ - [https://jira.atlassian.com/browse/MIG-837](https://jira.atlassian.com/browse/MIG-837?__hstc=72543820.4e76311f874131a99198a462418b615c.1662100942946.1677542271684.1677550101602.435&__hssc=72543820.22.1677550101602&__hsfp=179215543) | In the **Migration Assistant **app, a check has been included to track and list down restricted pages:
- update [Scaffolding Forms & Templates for Confluence Server](https://marketplace.atlassian.com/apps/190/scaffolding-forms-templates-for-confluence?tab=overview&hosting=server) to version 8.28.0 or higher
In **Apps vendor checks**, you will reach the **Restricted pages check **section.
> ℹ️ The checklists are any restricted pages in the space being migrated.
- download the .csv report of the restricted pages from **App vendor checks **and un-restrict the pages.
![image](media://8bd5c1d5-f95a-49e5-9ec3-530ac908092f)
Proceed with the migration once the **App vendor checks** are resolved. | | After clicking the **Migrate Scaffolding button**, some content or white space appears.
![image](media://dda6c994-517c-4a25-92ee-bc52c408c579) | 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:
> Macro (nested-table) | - Make sure that there is no hidden content with the "display:none" inline styling inside templates/pages before migrating to the Cloud. - Remove whitespaces manually. | | 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.
> Macro (nested-table)
The sample storage format of a working live template.
> Macro (nested-table)
It's currently unclear how customers may have this data on the Server, as parameter type  is a required field in the Scaffolding server.
![image](media://cae37a96-f41f-4ce5-98d7-14596a198ba0) | - Compare your live template [storage format](https://confluence.atlassian.com/doc/confluence-storage-format-790796544.html?__hstc=72543820.4e76311f874131a99198a462418b615c.1662100942946.1677542271684.1677550101602.435&__hssc=72543820.22.1677550101602&__hsfp=179215543) 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 this does not work, you may need to update the storage format manually with the required parameter. | | A live template loads infinitely after converting.
![live_template.png](media://6228e0a8-7d64-4d39-9b26-8d2059801a07) | The `Custom Separator` field is not supported in the Cloud.
![custom_separator.png](media://164b8bb5-b695-453d-8a3d-86bccf1ec247) | Remove the `Custom Separator` value from the `multi-select` field and retry the migration. | | After clicking the **Migrate Scaffolding button, **you see **Unsupported Content** error messages when there are Scaffolding macros inside a nested-bodied container.
![image](media://c55fd91a-c77d-465a-823b-5628c17c25dd) | This is a Confluence Cloud limitation as it does not allow [nesting macros inside a bodied macro](https://jira.atlassian.com/browse/CONFCLOUD-68323?__hstc=72543820.4e76311f874131a99198a462418b615c.1662100942946.1677542271684.1677550101602.435&__hssc=72543820.22.1677550101602&__hsfp=179215543) (such as panel macros, nested tables, expand macro, etc.) | Ensure that
- Scaffolding macros are outside nested-bodied macros in Server pages before migrating to the Cloud - Scaffolding macros are outside panel macros before clicking the **Migrate Scaffolding macro **button -
> Macro (nested-table) | | **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.
![image](media://5335de6f-7493-4074-be72-113329cf42fc)
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.
![image](media://ddd76607-186b-477b-baf1-d99c46cb7671) | | After bulk converting the pages, you notice that the page status shows **Failed**.
![image](media://4a63ff66-91d8-4726-90f1-a5f7c8c19e03) | 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.
> ℹ️ If you are still unable to find a solution, reach out to our [customer support ](https://appfire.atlassian.net/servicedesk/customer/portal/11)team. | | During the bulk conversion, you notice that the migration has stopped with the message **Critical error encountered**.
![image](media://041eec97-97b9-4711-bea6-07eb6d1135a4) | 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.
> ℹ️ If the error message still persists, reach out to our [customer support](https://appfire.atlassian.net/servicedesk/customer/portal/11)[ ](http://appf.re/support)team. | | After performing a bulk conversion, you notice a warning with the following message:
![image](media://9aa7073b-37b9-4a27-960c-02b960c35b85) | 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.
> ℹ️ If the error message still persists, reach out to our [customer support ](https://appfire.atlassian.net/servicedesk/customer/portal/11)team. | ## Related pages > Macro (children) ## Support Contact us via our [support portal](https://appfire.atlassian.net/servicedesk/customer/portal/11).