CCMA Limitations and Disparities
Migration limitations
Details | Limitations |
---|---|
Internal inbox collected type | Email replay and script-runner will not be migrated. Only the Internal inbox collector type will be migrated. |
Global Configuration | The Global Configuration will be replicated and migrated as space configuration when there are usages in the migrated space. The responses macro permission for this type of configuration will default to admin and space admin after migrating. |
Cross space configuration | For any forms that use configuration from a different space in Server, the configuration will not be migrated to Cloud. |
Attachments larger than 10MB | Any attachments larger than 10MB will not be migrated. |
Multiple Destination | Any Multiple Destination will not be supported nor migrated to Cloud. |
Confluence value | Confluence value is not supported in Forms for Confluence Cloud. |
Try Forms for Confluence Server/Data Center for free on the Atlassian Marketplace.
Feature disparity
The table below shows which features are available for CCMA actions:
Server/Data Center | Cloud | ||
---|---|---|---|
Key Features | Create fillable forms directly inside a Confluence page using Forms macros. | ||
Preview forms before they go live. | |||
Display form responses on a Confluence page in table format. | |||
Save and manage responses securely in Confluence. | |||
Easy export to CSV, JSON, and XML formats. | |||
Send custom success messages to respondents after submitting the form. | |||
Form Builder | |||
Analyze form responses with built-in statistics visualization. | |||
Show only relevant questions based on answers using conditional fields macro. | |||
Make long forms more user-friendly with section breaks and a progress bar display. | |||
Enable spam prevention by adding a Captcha field. | |||
Ability to send form submissions to multiple destinations (Confluence users, email addresses) *Forms for Confluence Cloud now has response notifications but the Cloud platform does not currently support custom email address notifications. | * | ||
Ability to create Jira issues via form submission through ScriptRunner for Jira integration *Forms for Confluence Cloud does not require a Scriptrunner integration for this feature to work. | * | ||
Ability to create a Confluence page via form submission through ScriptRunner for Confluence | |||
Built-in templates, including:
| |||
Confluence admins can view and manage forms they've created and forms that space admins created in the administration console | |||
Ability to add predefined values, such as Confluence user or user group, to a specific field using Confluence variables. | |||
Forms Homepage: A homepage to view, manage, and analyze all forms created in one centralized location. | |||
Collaborators: Add team members to share data and insights. | |||
Polls | |||
Embedded Visualizations | |||
Server/Data Center | Cloud | ||
Forms Macros/Questions(F4CC Questions in parenthesis) | Input Fields (Short Answer) | ||
Checkbox Group (Checkboxes) | |||
Radio Button Group (Radio Buttons) | |||
Textarea (Long Answer) | |||
Dropdown List (Dropdown) | |||
Datepicker (Date) | |||
Hidden Field | |||
Responses Table (Responses Table View) | |||
Destination List | |||
Additional Recipients | Available through Jira Task Forms | ||
Attachment | |||
Success Message | |||
Fieldset | |||
Mail Body Formatter | |||
Spam Prevention | |||
Submit and Submit Image Buttons | |||
Form Page | |||
Conditional Fields | |||
User Picker | |||
Radio Matrix | |||
Checkbox Matrix | |||
Star Rating |
Requirements to migrate using CCMA
While we know some feature gaps between the Server and Cloud apps, this will not affect the migration using CCMA. All existing server and cloud app features can still be migrated.