Migration from Data Center to Cloud

Learn about migrating configuration of the forms from Jira Data Center to Jira Cloud.

Overview of main differences

Two app versions — for both Jira Cloud and Data Center — offer the same business value but differ slightly in features and design.

The Cloud version offers a different set of tools tailored to the cloud environment. It simplifies configuration and focuses on using native Jira fields with flexible conditions. Unlike the Data Center version, it currently doesn’t include features such as Bundled Fields or tabbed layouts (coming soon).

We’re actively exploring solutions and working closely with Atlassian to bridge these gaps. Before you start your migration, it’s important to understand the main differences between Cloud and Data Center versions of the app to avoid losing the necessary data or functionalities.

Feature comparison

Feature	Data Center	Cloud	Data Center details	Cloud details
Bundled fields			Allows you to group multiple related subfields into one structured custom field.	Coming Soon
Dynamic Forms Assistant			-	Helps you manage Dynamic Forms in Jira by allowing you to create new rules or display existing configurations directly through chat.
Import/Export configuration			Allows admins to transfer Fields Visibility configurations via JSON files.	Allows admins to transfer rule configurations via JSON files
Read only			-	Makes the field visible to the user, but prevents them from editing its value.
Required action			Offers the same functionality - makes the field required.	Offers the same functionality - makes the field required.
Mapper/Set Value			Allows you to create mapping between other custom field’s value and text or group, user, project (all provided from dictionary).	Allows you to have fields automatically filled with predefined or dynamic values based on set conditions.
Fields visibility/Show field			Offers the same functionality - makes the field visible after selecting an option in the previous field..	Offers the same functionality - makes the field visible after selecting an option in the previous field..
Show/Hide options (Options Visibility)			-	Allows you to decide which options will be displayed in the select and multi-select fields.
Tabs visibility			Allows you to hide or display screen tabs based on the selected value in a related field. Tabs Visibility connects the related field with visibility settings.	-
Team-managed projects			-	Supports team-managed projects.
Transition Screens			Offers the same functionality - supports transition screens.	Offers the same functionality - supports transition screens.
Translations			Allows you to translate options in custom fields.	-
Variables			-	Allows you to use dynamic placeholders (variables) that automatically insert real-time data into forms or fields during issue creation.
Visibility Fields Visualisation			Allows you to check the relations between your Dynamic Forms custom fields on the dependency graph.	-

Migration process

Visibility

DC

In DC, to configure field’s visibility you have to add a custom field that was provided by Dynamic Forms.

Then, you have to go to Manage Apps>Dynamic Forms>Fields Visibility to configure it. Go to the DF Fields visibility configuration and select the custom field that was added to the screen. Set related fields, that will be displayed in the form after selecting a specific option of a dynamic field.

Cloud

To recreate your settings in Dynamic Forms Cloud it’s best to create identical fields (with the same name) as in your DC environment. For each of these fields follow the steps below to recreate your configuration:

1. In Cloud you also need to add a custom field (or use an already-existing field such as description), but it’s just a Jira custom field (see supported fields).

   

2. Go to Project Settings>Dynamic Forms.

3. Select the field that you want to hide and set a condition based on a field that has been added to the screen.

4. Add the Show field action.

5. Configure the action by adding a condition block.

   

For a detailed configuration see Show field and Configuration.

Set Value/Mapper

DC

In DC you create conditions for set values with mapper (Manage Apps>Dynamic Forms>Mapper).

1. Add a mapper custom field provided with Dynamic Forms.

   

2. Create a configuration - which values are set under which conditions.

   

Refer to respective documentation for details.

Cloud

To recreate your settings in Dynamic Forms Cloud it’s best to create identical fields (with the same name) as in your DC environment. For each of these fields follow the steps below to recreate your configuration:

1. In Cloud you can also add a custom field (or use an already-existing field such as description), but it’s just a Jira custom field (see supported fields).
2. Go to Project Settings>Dynamic Forms.
3. Select the custom field that has been added in the previous step (or use an already-existing field).
4. Add the Set value action.
5. Configure the action by adding a condition block.

   

For a detailed configuration see Set value and Configuration.

Migration FAQ

Can I directly migrate my Dynamic Forms configurations from Data Center to Cloud?

No, there is no direct migration path yet; you need to recreate your forms and rules manually in the Cloud version.

Are all features from Dynamic Forms Data Center available in the Cloud version?

Not all features are identical - some functionality differs or is limited in the Cloud version, so check the feature comparison before migrating.

How should I prepare my Jira Data Center instance before migrating forms to Cloud?

Review your existing configurations, export relevant data if possible, and document your forms and rules to aid manual recreation in Cloud.

Will my custom fields and screen schemes work the same after migration?

Custom fields and screen schemes need to be set up separately in Cloud, and certain configurations might require adjustment.

Is there any tool or automated process to help with migration?

Currently, migration must be done manually; no official automated migration tool is provided.