Migrate Service Management projects to the Cloud

Streamlining your workflow: Migrating Jira Service Management projects from Cloud to Cloud

Configuration Manager for Jira (CMJ) Cloud now allows you to migrate your Jira Service Management projects. Our app automates and streamlines the migration process, ensuring a smooth transition.

Migrate Jira Service Management projects

Currently, the CMJ Cloud app manages the migration of request types, organizations, portal groups, SLAs, queues, and calendars when deploying service management projects. This is just the initial stage of full migration support for Jira Service Management projects. Over time, we plan to add support for the remaining configuration elements.

How service management projects are migrated

Configuration Manager for Jira (CMJ) Cloud can:

• add a source service project as a new one to the destination site, and

• merge a source service project with an existing destination service project.

The Analyze Changes document explains how CMJ Cloud migrates and reports projects. The information there applies to Jira Software and Service Management projects.

Case-sensitivity in SLA names

The source and destination SLA fields may use different letter capitalizations, which can affect mapping. For instance, a source SLA called "Time to resolution" won't match a destination SLA labeled "TIME TO RESOLUTION." In such cases, CMJ Cloud will not map these SLAs. Instead, it will create a new destination SLA that exactly matches the name and capitalization of the source field.

Work categories of request types not moved during migration

Currently, the work category property for request types can’t be migrated. This means that after migration, all request types will be moved to the Unassigned category on the destination Jira site. To ensure all request types are in the right place, you need to check and manually reassign each request type to its original work category.

Supported Service Management configuration