Scaffolding blueprints are not available in cloud.

Confluence blueprints are supported as live templates in cloud.

The data in the Live Template macro migrates to the Scaffolding - Live Template macro only if:

• The Live Template macro is at the root level of the page structure.

• The Live Template macro is based on one of the following:

  • Confluence page

  • global page template

  • space template

The data in the Live Template macro doesn’t migrate in the following cases:

• The Live Template macro is based on a Scaffolding blueprint.

• The Live Template macro is nested within another macro.

-

The data in the Group Data macro migrates to the Scaffolding - Field Group macro in cloud only if:

• The Group Data macro is at the root level of the page structure.

• The Group Data macro contains Scaffolding macros that can convert to input fields within the Scaffolding - Field Group macro:

  • Attachment Data

  • Date Data

  • List Data (with an option-generating sub-macro)

  • Number Data

  • Table Data

  • Repeating Data

  • Text Data

The value of the Field name parameter of the Scaffolding - Field Group macro inherits the value of the Field name parameter of the Group Data macro.

One additional empty Scaffolding - Field Group macro is created with the Field name parameter value migrated. This can be deleted.

The data in the Group Data macro doesn’t migrate in the following:

• The Group Data macro is nested within any other macro.

• The Group Data macro contains incompatible or non-migratable Scaffolding macros unavailable in cloud:

  • Evaluation Data

  • Excerpt Data

  • Get Data

  • Hidden Data

  • Set Data

  • Group Data

Cannot combine different option types into a single dropdown menu. Each input field within the Field Group macro generates a separate dropdown menu.

The following parameters are not available in cloud and, therefore, their values don’t migrate:

• Type

• Separator

• Custom separator

• Blank Text

• Width

• Height

The data in the List Data macro migrates to the Scaffolding - Field Group macro with a corresponding field in cloud only if:

• The List Data macro is at the root level of the page structure or nested only within one of the following compatible macros:

  • Group Data

  • Repeating Data

  • Table Data

• The List Data macro is not set with a custom separator.

• For options generation, the List Data macro contains one of the following:

  • multiple List Option macros

  • a single Content Options macro

  • a single User Options macro

  • a single Attachment Options macro

  • a single Label Options macro

The Field name, Required, and Allow Multiple parameters of the corresponding field within the Field Group macro inherit the parameters of the List Data macro.

The data in the List Data macro doesn’t migrate if:

• The List Data macro is nested within an incompatible macro.

• The List Data macro is set with a custom separator.

• The List Data macro contains multiple option-generating macros that are different from the List Option macro.

The following macro parameters are not available in cloud and, therefore, their values don’t migrate:

• Label

• Sort Value

New parameter in cloud:

• Helper text

An option to select a color for each label.

The data in the List Option macros migrate to the Dropdown list field within the Scaffolding - Field Group macro only if:

• The parent List Data macro is either at the root level of the page structure or nested only within one of the following compatible macros:

  • Group Data

  • Repeating Data

  • Table Data

• The List Option macros are the only sub-macros or the first sub-macros within the List Data macro.

The macro parameters after the migration are as follows:

• The value of the Field name parameter of the Scaffolding - Field Group macro is migrated.

• The Field name, Required, and Allow multiple parameters of the Dropdown list field inherit the corresponding parameters of the parent List Data macro.

• The Labels parameter of the Dropdown list field inherits the Value parameters of the List Option macros.

The data in the List Option macros is not migratable in the following cases:

• The parent List Data macro is nested within an incompatible macro.

• The parent List Data macro contains another option-generating sub-macro preceding the List Option macros.

The following macro parameters are not available in cloud and, therefore, their values don’t migrate:

• Search result limit

• Parent

• Ancestor

• Branches

• Labels

• Sort by

• Order by

New parameter in cloud:

• Helper text

The data in the Content Options macro migrates to the Page list field within the Scaffolding - Field Group macro only if:

• The parent List Data macro is either at the root level of the page structure or nested only within one of the following compatible macros:

  • Group Data

  • Repeating Data

  • Table Data

• The Content Options macro is a single sub-macro or the first sub-macro within the List Data macro.

The macro parameters after the migration are as follows:

• The value of the Field name parameter of the Scaffolding - Field Group macro is migrated.

• The Field name, Allow multiple, and Required parameters of the Page list field inherit the corresponding parameters of the parent List Data macro.

The data in the Content Options macro doesn’t migrate in the following cases:

• The parent List Data macro is nested within an incompatible macro.

• The List Data macro contains another option-generating sub-macro preceding the Content Options macro.

The following macro parameters are not available in cloud and, therefore, their values don’t migrate:

• Space(s)

• User(s)

• Match

New parameter in cloud:

• Helper text

The data in the User Options macro migrates to the User list field within the Scaffolding - Field Group macro only if:

• The parent List Data macro is either at the root level of the page structure or nested only within one of the following compatible macros:

  • Group Data

  • Repeating Data

  • Table Data

• The User Options macro is a single sub-macro or the first sub-macro within the List Data macro.

The macro parameters after the migration are as follows:

• The value of the Field name parameter of the Scaffolding - Field Group macro is migrated.

• The Field name, Allow multiple, and Required parameters of the User list field inherit the corresponding parameters of the parent List Data macro.

The data in the User Options macro doesn’t migrate in the following cases:

• The parent List Data macro is nested within an incompatible macro.

• The List Data macro contains another nested macro preceding the User Options macro.

The following macro parameters are not available in cloud and, therefore, their values don’t migrate:

• Include

• Exclude

• Allow multiple

New parameters in cloud:

• Helper text

The data in the Attachment Options macro migrates to the Files list field within the Scaffolding - Field Group macro only if:

• The parent List Data macro is either at the root level of the page structure or nested only within one of the following compatible macros:

  • Group Data

  • Repeating Data

  • Table Data

• The Attachment Options macro is a single sub-macro or the first sub-macro within the List Data macro.

The macro parameters after the migration are as follows:

• The value of the Field name parameter of the Scaffolding - Field Group macro is migrated.

• The Field name and Required parameters of the Files list field inherit the corresponding parameters of the parent List Data macro.

• The Page parameter of the Files list field inherits the Content parameter of the Attachment Options macro.

The data in the Attachment Options macro doesn’t migrate in the following cases:

• The parent List Data macro is nested within an incompatible macro.

• The List Data macro contains another nested macro preceding the Attachment Options macro.

The following macro parameters are not available in cloud and, therefore, their values don’t migrate:

• Allow multiple

New parameters in cloud:

• Helper text

The data in the Label Options macro migrates to the Files list field within the Scaffolding - Field Group macro only if:

• The parent List Data macro is either at the root level of the page structure or nested only within one of the following compatible macros:

  • Group Data

  • Repeating Data

  • Table Data

• The Label Options macro is a single sub-macro or the first sub-macro within the List Data macro.

The macro parameters after the migration are as follows:

• The value of the Field name parameter of the Scaffolding - Field Group macro is migrated.

• The Field name and Required parameters of the Files list field inherit the corresponding parameters of the parent List Data macro.

• The Labels parameter of the Labels list field inherits the Name parameter of the Label Options macro.

The data in the Label Options macro doesn’t migrate in the following cases:

• The parent List Data macro is nested within an incompatible macro.

• The List Data macro contains another nested macro preceding the Label Options macro.

New parameter in cloud:

• Helper text

The data in the Attachment Data macro migrates to the Attachment upload field within the Scaffolding - Field Group macro in the following cases:

• The Attachment Data macro is at the root level of the page structure.

• The Attachment Data macro is nested only within one of the following compatible macros:

  • Group Data

  • Repeating Data

  • Table Data

The macro parameters after the migration are as follows:

• The value of the Field name parameter of the Scaffolding - Field Group macro is migrated.

• The parameters of the Attachment upload field inherit the corresponding parameters of the Attachment Data macro.

The data in the Attachment Data macro doesn’t migrate if the macro is nested within an incompatible macro.

The following macro parameters are not available in cloud and, therefore, their values don’t migrate:

• Minimum Date

• Maximum Date

• Display Format

New parameter in cloud:

• Helper text

The data in the Date Data macro migrates to the Date field within the Scaffolding - Field Group macro in the following cases:

• The Date Data macro is at the root level of the page structure.

• The Date Data macro is nested only within one of the following compatible macros:

  • Group Data

  • Repeating Data

  • Table Data

The macro parameters after the migration are as follows:

• The value of the Field name parameter of the Scaffolding - Field Group macro is migrated.

• The Field name and Required parameters of the Date field inherit the corresponding parameters of the Date Data macro.

The data in the Date Data macro doesn’t migrate if the macro is nested within an incompatible macro.

The following macro parameters are not available in cloud and, therefore, their values don’t migrate: