--- title: "Macro differences between Scaffolding Data Center and Scaffolding Cloud" canonical: "https://support.appfire.com/space/SCAFC/1827012708/Macro%20differences%20between%20Scaffolding%20Data%20Center%20and%20Scaffolding%20Cloud" format: markdown --- > Macro (aura-html) ## Macros migratable to cloud ### [Live Template](https://appfire.atlassian.net/wiki/spaces/SCAFS/pages/477599986) The Live Template macro in data center converts to the [Scaffolding - Live Template](https://appfire.atlassian.net/wiki/spaces/SCAFC/pages/477470864) macro in cloud.
Migration considerations | **What’s different in cloud** | :check_mark: **Supported migration scenarios** | :cross_mark: **Unsupported migration scenarios** | | --- | --- | --- | | :minus: Scaffolding blueprints are not available in cloud.
:plus: 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
> ⚠️ When migrating a page with a Live Template macro, verify that you also migrate the template on which the macro is based. | 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. |
### [Group Data](https://appfire.atlassian.net/wiki/spaces/SCAFS/pages/477600026) The Group Data macro in data center converts to the [Scaffolding - Field Group](https://appfire.atlassian.net/wiki/spaces/SCAFC/pages/477470926) macro in cloud. The Scaffolding macros inside the Group Data macro convert to input fields within the Scaffolding - Field Group macro.
Migration considerations | **What’s different in cloud** | :check_mark: **Supported migration scenarios** | :cross_mark: **Unsupported migration scenarios** | | --- | --- | --- | | - | 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 |
### [List Data](https://appfire.atlassian.net/wiki/spaces/SCAFS/pages/477600000) The List Data macro in data center converts to the [Scaffolding - Field Group](https://appfire.atlassian.net/wiki/spaces/SCAFC/pages/477470926) macro in cloud. The option-generating macro within the List Data macro converts to a field within the Scaffolding - Field Group macro.
Migration considerations | **What’s different in cloud** | :check_mark: **Supported migration scenarios** | :cross_mark: **Unsupported migration scenarios** | | --- | --- | --- | | :minus: Cannot combine different option types into a single dropdown menu. Each input field within the Field Group macro generates a separate dropdown menu.
:minus: 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
> ⚠️ If the List Data macro is nested with multiple option-generating macros, only the first option-generating macro migrates to cloud. Multiple option-generating macros migrate only if they are List Option macros.
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. |
#### [List Option](https://appfire.atlassian.net/wiki/spaces/SCAFS/pages/477599993) (within List Data) Multiple List Option macros within the List Data macro in data center convert to the [Dropdown list](https://appfire.atlassian.net/wiki/spaces/SCAFC/pages/477471229) field within the Scaffolding - Field Group macro in cloud.
Migration considerations | **What’s different in cloud** | :check_mark: **Supported migration scenarios** | :cross_mark: **Unsupported migration scenarios** | | --- | --- | --- | | :minus: The following macro parameters are not available in cloud and, therefore, their values **don’t migrate**:
- *Label* - *Sort Value*
:plus: New parameter in cloud:
- *Helper text*
:plus: 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 *Label *parameters of the List Option macros don’t migrate. If the *Label *parameters are configured in data center, the dropdown list items in cloud differ from the dropdown list items in data center. | 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. |
#### [Content Options](https://appfire.atlassian.net/wiki/spaces/SCAFS/pages/477599859) (with List Data) The Content Options macro within the List Data macro in data center converts to the [Page list](https://appfire.atlassian.net/wiki/spaces/SCAFC/pages/477471316) field within the Scaffolding - Field Group macro in cloud.
Migration considerations | **What’s different in cloud** | :check_mark: **Supported migration scenarios** | :cross_mark: **Unsupported migration scenarios** | | --- | --- | --- | | :minus: 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*
:plus: 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. |
#### [User Options](https://appfire.atlassian.net/wiki/spaces/SCAFS/pages/477600103) (within List Data) The User Options macro within the List Data macro in data center converts to the [User list](https://appfire.atlassian.net/wiki/spaces/SCAFC/pages/477463915) field within the Scaffolding - Field Group macro in cloud.
Migration considerations | **What’s different in cloud** | :check_mark: **Supported migration scenarios** | :cross_mark: **Unsupported migration scenarios** | | --- | --- | --- | | :minus: The following macro parameters are not available in cloud and, therefore, their values **don’t migrate**:
- *Space(s)* - *User(s)* - *Match*
:plus: 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.
> ⚠️ When migrating a User Options macro, verify that you also migrate all users in order to appear in the dropdown list.
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. |
#### [Attachment Options](https://appfire.atlassian.net/wiki/spaces/SCAFS/pages/477599847) (within List Data) The Attachment Options macro within the List Data macro in data center converts** **to the [Files list](https://appfire.atlassian.net/wiki/spaces/SCAFC/pages/477463921) field within the Scaffolding - Field Group macro in cloud.
Migration considerations | **What’s different in cloud** | :check_mark: **Supported migration scenarios** | :cross_mark: **Unsupported migration scenarios** | | --- | --- | --- | | :minus: The following macro parameters are not available in cloud and, therefore, their values **don’t migrate**:
- *Include* - *Exclude* - *Allow multiple *
:plus: 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. |
#### [Label Options](https://appfire.atlassian.net/wiki/spaces/SCAFS/pages/477600007) (within List Data) The Label Options macro within the List Data macro in data center converts** **to the [Labels list](https://appfire.atlassian.net/wiki/spaces/SCAFC/pages/477463909) field within the Scaffolding - Field Group macro in cloud.
Migration considerations | **What’s different in cloud** | :check_mark: **Supported migration scenarios** | :cross_mark: **Unsupported migration scenarios** | | --- | --- | --- | | :minus: The following macro parameters are not available in cloud and, therefore, their values **don’t migrate**:
- *Allow multiple *
:plus: 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. |
### [Attachment Data](https://appfire.atlassian.net/wiki/spaces/SCAFS/pages/477599836) Тhe Attachment Data macro in data center converts to the [Attachment upload](https://appfire.atlassian.net/wiki/spaces/SCAFC/pages/477470275) field within the Scaffolding - Field Group macro in cloud.
Migration considerations | **What’s different in cloud** | :check_mark: **Supported migration scenarios** | :cross_mark: **Unsupported migration scenarios** | | --- | --- | --- | | :plus: 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. |
### [Date Data](https://appfire.atlassian.net/wiki/spaces/SCAFS/pages/477599897) The Date Data macro in data center converts to the [Date field](https://appfire.atlassian.net/wiki/spaces/SCAFC/pages/477471261) within the Scaffolding - Field Group macro in cloud.
Migration considerations | **What’s different in cloud** | :check_mark: **Supported migration scenarios** | :cross_mark: **Unsupported migration scenarios** | | --- | --- | --- | | :minus: The following macro parameters are not available in cloud and, therefore, their values **don’t migrate**:
- *Minimum Date* - *Maximum Date* - *Display Format*
:plus: 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. |
### [Number Data](https://appfire.atlassian.net/wiki/spaces/SCAFS/pages/477600141) The Number Data macro in data center converts to the [Number](https://appfire.atlassian.net/wiki/spaces/SCAFC/pages/477463865) field within the Scaffolding - Field Group macro in cloud.
Migration considerations | **What’s different in cloud** | :check_mark: **Supported migration scenarios** | :cross_mark: **Unsupported migration scenarios** | | --- | --- | --- | | :minus: The following macro parameters are not available in cloud and, therefore, their values **don’t migrate**:
- *Allow decimal values* - *Minimum Value* - *Maximum Value* - *Display Format* - *Width*
:plus: New parameter in cloud:
- *Helper text* | The data in the Number Data macro migrates to the Number field within the Scaffolding - Field Group macro in the following cases:
- The Number Data macro is at the root level of the page structure. - The Number 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 Number field inherit the corresponding parameters of the Number Data macro. | The data in the Number Data macro doesn’t migrate if the macro is nested within an incompatible macro. |
### [Text Data](https://appfire.atlassian.net/wiki/spaces/SCAFS/pages/477600110) The Text Data macro in data center converts to either the [Paragraph](https://appfire.atlassian.net/wiki/spaces/SCAFC/pages/477463865) or the [Short text](https://appfire.atlassian.net/wiki/spaces/SCAFC/pages/477463877) field within the Scaffolding - Field Group macro in cloud.
Migration considerations | **What’s different in cloud** | :check_mark: **Supported migration scenarios** | :cross_mark: **Unsupported migration scenarios** | | --- | --- | --- | | :minus: The following macro parameters are not available in cloud and, therefore, their values **don’t migrate**:
- *Type* - *Content Type* - *Language* - *Hide Full Text* - *Minimum Length* - *Maximum Length* - *Pattern* - *Pattern Error Message* - *Width* - *Height*
:plus: New parameter in cloud:
- *Helper text* | The data in the Number Data macro migrates to the Paragraph or Short text field within the Scaffolding - Field Group macro in the following cases:
- The Text Data macro is at the root level of the page structure. - The Text Data macro is nested only within one of the following compatible macros: - Group Data - Repeating Data - Table Data
> ℹ️ If the *Type *parameter of the Text Data macro is `area`, the macro converts to the Paragraph field within the Scaffolding - Field Group macro. **Note**: The Paragrah editor has a limited rich text support. > ℹ️ > ℹ️ If the value of the *Type *parameter of the Text Data macro is `line`, the macro converts to the Short text field within the Scaffolding - Field Group macro. > ℹ️ > ℹ️ If the value of the *Type *parameter of the Text Data macro is `password`, the macro converts to the Short text field within the Scaffolding - Field Group macro. **Note**: The Short text editor doesn’t provide a masked view on the page, so the passwords are visible.
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 Paragraph or Short text field inherit the corresponding parameters of the Text Data macro.
> ⚠️ Due to differences in the macros and limitations in cloud, the Paragraph macro can only accept some of the rich text content features. | The data in the Text Data macro doesn’t migrate if the macro is nested within an incompatible macro. |
### [Table Data](https://appfire.atlassian.net/wiki/spaces/SCAFS/pages/477600119) The Table Data macro in data center converts to the [Table field](https://appfire.atlassian.net/wiki/spaces/SCAFC/pages/477471139) field within the Scaffolding - Field Group macro in cloud.
Migration considerations | **What’s different in cloud** | :check_mark: **Supported migration scenarios** | :cross_mark: **Unsupported migration scenarios** | | --- | --- | --- | | :minus: The following macro parameters are not available in cloud and, therefore, their values **don’t migrate**:
- *Initial Rows* - *Order* - *Width*
:plus: New parameter in cloud:
- *Helper text* | The data in the Table Data macro migrates to the Table field within the Scaffolding - Field Group macro in the following cases:
- The Table Data macro is at the root level of the page structure or nested only within the Group Data. - The Table Data macro contains only 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 - Text 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 *parameter of the Table field inherits the *Name* parameter of the Text Data macro. | The data in the Text Data macro doesn’t migrate if:
- The Table Data macro is nested within another macro other than the Group Data macro. - The Table Data macro contains incompatible or non-migratable Scaffolding macros: - Evaluation Data - Excerpt Data - Get Data - Hidden Data - Set Data - Group Data - Repeating Data - Table Data - Live Template macro - Confluence macro, including a Confluence table - Non-Scaffolding third-party macro |
### [Repeating Data](https://appfire.atlassian.net/wiki/spaces/SCAFS/pages/477600134) The Repeating Data macro in data center converts to the [Table field](https://appfire.atlassian.net/wiki/spaces/SCAFC/pages/477471139) field within the Scaffolding - Field Group macro in cloud.
Migration considerations | **What’s different in cloud** | :check_mark: **Supported migration scenarios** | :cross_mark: **Unsupported migration scenarios** | | --- | --- | --- | | :minus: The following macro parameters are not available in cloud and, therefore, their values **don’t migrate**:
- *Initial Rows* - *Order* - *Width*
:plus: New parameter in cloud:
- *Helper text* | The data in the Repeating Data macro migrates to the Table field within the Scaffolding - Field Group macro only if:
- The Repeating Data macro is at the root level of the page structure. - The Repeating Data macro contains only migratable and compatible Scaffolding macros: - Attachment Data - Date Data - List Data (with an option-generating sub-macro) - Number Data - Text 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 *parameter of the Table field inherits the *Name* parameter of the Text Data macro. | The data in the Text Data macro doesn’t migrate if:
- The Repeating Data macro is nested within another macro. - The Repeating Data macro contains incompatible or non-migratable Scaffolding macros: - Evaluation Data - Excerpt Data - Get Data - Hidden Data - Set Data - Group Data - Repeating Data - Table Data - Live Template macro - Confluence macro, including a Confluence table - Non-Scaffolding third-party macro |