I’ve worked on a lot of Jira migrations from Data Center to Cloud. The core data usually moves well. The surprises come from apps: configuration that lived in an app’s own tables, and nobody planned for it.
If your teams use Epic & Issue Templates (formerly Smart Issue Templates) on Data Center, here is how its data moves to Cloud.
Two paths
Automated, with the Jira Cloud Migration Assistant (recommended). The app is part of your JCMA migration plan. Its data arrives in Cloud with the rest of the migration, matched to the spaces and users you migrate. You follow its progress on the app’s Migration status page in Cloud. If you run the migration again, it updates what it created instead of adding copies.
Manual, by export and import. You export files from Data Center, one per kind of data, and import them in Cloud. Use it when JCMA can’t complete the migration, when JCMA isn’t an option for your site, or when you want a copy of your data to keep.
Both paths carry scopes, templates and template sets.
Before either path
- Update the app. On Data Center, version 3.1.9 or later for Jira 10 and earlier, or 4.0.5 or later for Jira 11. On Cloud, 28.0.0 or later.
- Migrate what the templates point at first. The spaces, work types, groups and users your templates use should already be on the Cloud site.
- Pick one path for each kind of data. Records from one path aren’t matched to records from the other, so using both can create copies.
How the paths differ
| Automated (JCMA) | Manual (export and import) | |
|---|---|---|
| Missing space or work type | Templates that use it are not migrated; set levels are kept and marked Incomplete | The item is imported without it; set levels are marked Incomplete |
| Owners | Matched through JCMA, otherwise a site admin | Matched by email for templates and sets |
| Template custom fields | Carried, for supported field types | Not carried |
| Size | No per-file limit | Up to 1,000 scopes, 500 templates and 100 template sets per file |
My advice
Treat app data as its own line in your migration plan, with an owner and a test. Run a test migration, apply a few template sets in the Cloud test site, and check the work items they create. It takes an afternoon and saves a rough first week after cutover.
The full steps for both paths are in our documentation.



