Migration from Data Center to Cloud

Learn about migrating templates from Jira Data Center to Jira Cloud.

Overview

Issue Templates for Jira provides a dedicated migration tool that makes moving from Jira Data Center to Cloud simple and efficient. The migrator transfers your templates along with their configuration and automatically activates them in the Cloud environment.

This significantly reduces manual work and ensures a smooth transition, allowing you to continue using your templates with minimal setup after migration.

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.
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.
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.	Available in the advanced version. See Default Templates and Jira Service Management 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

The migration process is simple and requires no additional configuration. It’s performed using Jira’s native migration app, with the Issue Templates migrator handling the transfer in the background.

Templates, along with their settings, are automatically moved and activated in the Cloud instance, allowing you to start using them right away without extra setup.

Before you start

To perform the migration you’ll need two separate licenses, one for the Data Center version and one for the Cloud. Read more about Dual Licensing.

Read the official Atlassian Migration Guide and proceed accordingly. You can check official Atlassian documentation for migration details.

If you have some questions regarding Jira contact Atlassian support selecting Migration Support.

Steps

1. In Jira DC, navigate to System → Logging and profiling → Default loggers → Configure and add com.intenso.jira.plugins.it.migration to logging and profiling as Trace.

   

2. Use Jira Cloud Migration Assistant to migrate your project and templates following official Atlassian instructions.
3. Select a project/space that stores your templates in Jira Cloud Migration Assistant.

   

4. Select Issue Templates for Jira in Jira Cloud Migration Assistant.

   

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

Result

Your templates and settings were migrated to Jira Cloud, simple as that. They are active and ready to use.

You can navigate to Jira Cloud Settings → Marketplace apps → Issue Templates For Jira → Migration to Cloud to check the status of your migration:

Migration FAQ

How does the migration process work?

Are there any differences in how the app works?

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

How do I copy subtasks on the Cloud?

Are stories copied under an epic?

Are variables migrated?

What happens if I repeat the migration process?

I need to migrate in a few batches, when should I include Issue Templates?