Smart Issue Templates for Jira Cloud
Smart Issue Templates for Jira Cloud
Breadcrumbs

Migrate from Data Center to Cloud

This guide covers two methods for migrating Smart Issue Templates data from Jira Data Center/Server to Jira Cloud. Choose the method that best fits your migration scenario.

Migration Methods Comparison

Feature

JCMA (Automated)

Manual Export/Import

Best for

Enterprise migrations using Jira Cloud Migration Assistant

Smaller migrations or when JCMA is not available

Automation level

Fully automated within JCMA workflow

Manual file export and import

Data mapping

Automatic user, project, and field mapping

Requires manual field and user alignment

Progress tracking

Real-time dashboard and logs

Limited visibility

Re-run capability

Can re-run and overwrite previous migration

Manual process each time

Method 1: JCMA Automated Migration (Recommended)

This method uses the Jira Cloud Migration Assistant (JCMA) to automatically migrate Smart Issue Templates data as part of your Jira migration.

For complete step-by-step instructions, prerequisites, and troubleshooting, see the https://appsdelivered.atlassian.net/wiki/x/CIAJ1w.

Method 2: Manual Export/Import

Use this method when JCMA is not available or for smaller, targeted migrations.

Pre-Migration Steps

  1. Prepare the Jira backup

  2. Set the custom fields for Jira Cloud to correspond to the names, values, and types in Jira Data Center/Server

  3. Create Jira users in Jira Cloud with the same usernames as on Jira Data Center/Server for the correct functioning of user picker fields (Assignee, Reporter, etc.)

  4. Create the Scopes that will correspond to the Jira Cloud workflow

Important: The manual method requires careful alignment of custom fields, users, and scopes between your DC and Cloud instances before importing data.

Known Limitations

  • Hierarchies: Template hierarchy structures are not yet supported in JCMA migration (coming soon)

  • User mapping: Users must exist in Cloud for proper owner/assignee mapping; otherwise, they appear as "Migrated User"

  • Custom field mapping: Custom fields must have matching names and types in Cloud for values to migrate correctly

  • Global templates: Templates with global scope may require manual scope adjustment after migration

Getting Help

If you encounter issues not covered here:

  1. Collect the migration logs from JCMA and migration dashboard information

  2. Note the migration ID and timestamp

  3. Contact support with this information