Migration from Data Center to Cloud

Learn about migrating templates from Jira Data Center to Jira Cloud

Overview of main differences

Both versions of the Issue Templates app enable rapid issue creation using predefined templates. Core functionalities are available in both Jira Data Center and Jira Cloud, delivering the same business value.

The Cloud version introduces a streamlined UI tailored to its environment, including a template creation wizard and AI-powered support. While the Data Center version currently offers more advanced capabilities, we’re continuously closing the gap with ongoing improvements to the Cloud edition.

Migration involves two steps: exporting/importing templates and configuring settings manually. Jira’s native export/import tools support the first step. Due to platform-specific differences, a dedicated migration tool is not available.

Feature comparison

Feature	Data Center	Cloud	DC details	Cloud details
Multiple projects as a template repository			You can only have one repository. The app offers sample templates.	You can establish multiple repository projects and use an easy onboarding. You can use existing projects as repositories or create new ones.
Advanced template configuration			Available on the template’s issue view, as well as in the Template Navigator.	Available on every template’s issue view in a repository project. Offers an easy template configuration wizard, see Template’s configuration.
Static variables			There are two types of variables: User variables and System variables.	You can add Static variables that are equivalent to system variables in the Data Center version.
Dynamic variables			-	New Dynamic Variables.
Template selection on the native create screen			Available for all screen types delivered by Jira, including create, edit and transition screens.	You can automatically add the template select field to Jira native create screen. See more details in the Create from template chapter.
User-friendly template creation wizard			Templates are configured on the template’s issue view, as well as in the Template Navigator.	Offers an easy template configuration wizard - Template’s configuration.
Smart defaults			-	Provides a new feature - Smart Defaults which are configurable template fields that automatically calculate and fill in values using smart expressions at the moment an issue is created, enabling automation and dynamic data population.
JQL Support			Offers the same functionality - see JQL Searchers for more details.	Offers the same functionality - see JQL Searchers for more details.
Automation and app integration			The way the app is integrated differs. For more details, see REST API	The way the app is integrated differs. For more details, see Automation.
AI assistant			-	You can use Deviniti’s Rovo Assistant with this application.
Simple availability settings			Available under the Availability tab in particular templates and in the global Template Repository project’s settings.	Available in the Template’s configuration panel in Availability tab.
Advanced availability settings			You can restrict the template’s availability to the following categories: Projects, Project Categories, Issue Type, Screens, Groups, Users, Languages.	Allows to restrict the template’s availability to particular projects only.
Set of fields/Scope			Available on every template’s issue view (Fields tab) and under the repository project’s settings.	Available on every template’s issue view, under the repository project’s settings and global configuration.
Customer portal support			Supported with all functionalities such as autocomplete and variables. See Jira Service Management for more details.	Supported with limitations. See Jira Service Management for more details.
Templates with epics/subtasks/issue links			Supported with an additional workflow post function (Create Structure).	Supported with no additional settings needed.
Use as a template			You can convert any issue into a template. See Use as a template for details.	You can convert any issue into a template in every Repository project.
Default templates			Available under every project settings. See Default Template for details.	You can configure a default template only for Jira Service Management for particular request types. See Default Template for details.
Bulk actions			You can edit and manage templates in bulk, rather than template by template.	You can edit and manage templates in bulk, rather than template by template.

Migration process

In both versions, templates are stored in a project that serves as a repository. This project can be migrated, just as any other project, using Jira’s native importing tools.

In Jira Cloud, a template is just an issue with additional issue properties. Unfortunately, at the moment there is no easy way to migrate issue properties. After importing the repository project, all the issues should be visible in issue navigator, however they may not be visible as templates on the Manage templates page yet.

Steps

1. Use Jira Cloud Migration Assistant to migrate your project and templates following official Atlassian instructions.
2. Make sure your project that stores your templates is selected.

   

3. Finish the migration following the Jira Cloud Migration Assistant wizard.

Result

Your template repository project along with templates has been migrated, however you still need to activate them and recreate some features manually, such as certain types of variables.

Template activation

After the migration, the template issues are available in the repository project but they still need to be activated as templates for Jira Cloud. In order to do so, you need to use the Use as a template setting in each template issue.

After the activation, all the templates will be available on the Manage templates page in Jira Cloud:

Single activation

You can activate the templates one by one manually using the toggle:

Bulk activation

You can activate all templates that have no configuration and have the Use as a template toggle disabled. You should use this option right after migration.

Use bulk activation after:

• migrating templates from Jira Data Center to Jira Cloud.
• importing CSV templates with the native Jira Cloud feature Import data from a CSV file.

Templates will be activated and configured with default values from the template configuration panel:

• Template name set based on the issue summary
• Template selectable ON
• Default scope (inherit)
• Copy sub-task ON
• Template available in all projects

Steps

1. Navigate to Templates Repository > Project settings > Issue Templates and open Manage templates tab.
2. Click Activate templates

3. Once you click it, the app will scan for all issues in the repository that are not activated as a template and automatically activate these templates.

   

Result

The manage templates list has been updated and all templates have been activated.

Template details’ configuration

An activated template is practically ready to use on the Cloud. Fields and their contents are preserved in each template. You might want to additionally configure the following:

• Template name. By default, the template’s summary becomes its name. You can change the name at any time if you want it to be different from the summary.
• Scope (set of fields). After the migration, the template’s scope is set to inherit. This means that you only need to set the scope in an epic and it will be applied to the entire issue structure. The default scope is set to All fields except Reporter which means that even if you don’t configure the scope, all the template’s fields (apart from Reporter) will be copied to the target issue.
• Availability. The availability settings are not inherited from the Data Center version but you can use the Create from template button instead. It suggests matching templates for the chosen issue type and is a good alternative for setting availability per issue type.

Migration FAQ

Do I need to configure any post functions on the Cloud version?

No, on Cloud you can autofill fields and copy values from templates without any post functions.

How do I copy subtasks on the Cloud?

The Copy subtasks feature is enabled by default. Every template issue that has subtasks will create those subtasks in the target project without any additional configuration. However, you may need to select that option in child issues if you want to copy sub-tasks there as well. See Copy subtask for details.

Is a template name migrated?

A template name is replaced with summary in the Cloud version.

Are stories copied under an epic?

Yes. If you have a template that is an epic with stories, the entire structure will be created in the target project without any additional configuration.

Are variables migrated?

Variables in the Cloud version work from a technical point of view, in a different way than in the DC version. Therefore, it’s necessary to configure them again.

I’m using a template issue type, will it be migrated?

If you try to migrate your templates that are based on the template issue type it might disturb your migration process, if you don’t have this issue type added in your Cloud project.

Can I use default templates on the Cloud?

Because of the Jira API’s limitations, currently we are not able to offer a Cloud alternative for this feature.

You can reach a similar effect (although without the autocomplete feature) by adding the Apply template post function to the Create transition.

This feature is on the roadmap and will be added to the Cloud version.