Learn about migrating templates from Jira Cloud to Jira Cloud
There are two methods to migrate your templates from one Jira Cloud instance to another:
You can use either of these methods to migrate your template repository.
These methods migrate only your template issues and the repository project, not app configuration.
| CSV file method benefits | JCMA plugin method benefits |
|---|---|
| Templates are ready to use immediately after import | The source template repository project is automatically migrated |
| No configuration required for users | No configuration required for an admin (for example, additional import of issues) |
| CSV file method limitations | JCMA plugin method limitations |
|---|---|
| Additional export/import of template issues is required after migrating the whole Jira site | Templates are not activated after migrating the project - additional activation is required (see, Migration from Data Center to cloud) |
| You need to exclude the source template repository project for this method to work, when you migrate your jira with the JCMA plugin. | - |
With this method, when an issue is imported into the repository project, it’s recognized as a newly created issue, therefore it’s automatically set as a template by the app. All imported issues are enabled as templates after completing the import wizard.
When an issue is imported from the csv file, the issue is created by Jira without issue properties, because the CSV export file doesn’t contain them. That’s why template configuration, such as template name or scope, won’t be migrated.
The import issues from CSV option from issue navigator doesn’t work if you want to import subtasks. Use System → External System Import.
Jira might fail to import epic links from the file generated by Jira export producing the following error - Cannot add value [ [SPSTEMPL-1] ] to CustomField Epic Link in Issue with summary 'Story template'. Probably value was in incorrect format.
If such a case occurs, change the Custom field (Epic Link) column and replace the issue key value, for example “SPSTEMPL-1“ to the name of the epic.
Once the source template repository project is exported and imported into the target Jira site, all issues are automatically enabled as templates with default settings.
JCMA migrates a whole project. It recreates the same project from the source Jira site in the target Jira site. This method requires no configuration, as all templates are copied automatically, although you need to activate them after the project migration is complete.
The source templates repository project is moved to the target Jira site with all template issues. All template issues are available and can be found in the Issue navigator.
