This step will contain all page includes details of a number of known issues of secure macros that are not migrated to Cloud, along together with possible solutions and workarounds.
Symptom in Confluence Cloud after migration | Cause | Solution/Workaround |
|---|
Secure macros appear on their relevant pages as |
on their relevant pages | These are Secure macros that are yet to be transformed. |
Go to the Secrets , then tab . |
Secure macros appear innested macros as |
innested macros. | Confluence Cloud currently does not support nested macros (See CONFCLOUD-68323) which means integration with other apps by way of nesting will be limited. In the example below, a Secret macro is nested within an Expand macro (a standard Confluence macro). This Secret would not be migrated unless it is moved out of the Expand macro. |
Image Removed Image Added |
As , .The The Security & Encryption for Confluence app user |
has to must have permission at space settings for the migration to be successful. |
Check , see . This , the app user should exist and have sufficient permissions. |
Image Removed Image Added |
Migration is incomplete | Secure macros belonging to owners with no product access to Confluence Cloud will not be transformed correctly to Cloud - this will result in the error Migration is incomplete. |
.
Image Removed Image Added | Run through the steps below |
:In - .In - Navigate Ensure | Expand |
|---|
| title | Here is an example .. |
|---|
|
 Image Removed
|
 Image Added |
Secure macros cannot be transformed if the Confluence administrator does not have Add page access to the target page where the Secret will be transformed to. |
This This too will result in the error Migration is incomplete. |
.Image Removed Image Added | Run through the steps below |
:In - .In - . Enable Add page .