On this page: |
Streamlining your workflow: Migrating Jira Service Management projects from Server/Data Center to Cloud
In today's dynamic business landscape, organizations continually seek ways to enhance their project management processes. As part of this evolution, many are opting to migrate their Jira Service Management projects from Server or Data Centers to the Cloud. This transition brings numerous benefits, including improved scalability, enhanced collaboration, and seamless access to the latest features and updates.
Configuration Manager Cloud Migration Tool automates and streamlines the migration process, ensuring a smooth transition while preserving important configurations and data.
Migrate Jira Service Management projects
Currently, the Cloud Migration Tool handles the migration of request types and organizations when it migrates service management projects (service projects). It's important to note that this marks the initial stage in the full migration of Jira Service Management projects. Over time, we plan to add support for migrating the remaining Service Management configuration elements.
How service management projects are migrated
Cloud Migration Tool can:
add a source service project as a new one to the destination site, and
migrate a source service project’s configuration and issues to an existing destination service project without issues.
Problem
You can only migrate project configuration and data to an existing destination project if it has no issues. If the destination project contains issues, Cloud Migration Tool will report an error in the Analyze changes page. Also, because of this error, you won't be able to continue the migration.
Solution
The solution is to transform the source project in the migration to either create it as new or map it to a project without issues in the destination. To achieve that, change the project name and key or use the Customize mapping option to create the project as new or to map it to a project without issues in the destination.
The Analyze Changes document explains how Cloud Migration Tool migrates and reports projects. The information there applies to Jira Software and Service Management projects.
Case-sensitivity by SLA-type field 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, the Cloud Migration Tool will not map these SLAs. Instead, it will create a new destination SLA that exactly matches the name and capitalization of the source field.
Supported Service Management configuration
Jira Service Management configuration | Migration with Cloud Migration Tool |
|---|---|
Service Management project basics | AVAILABLE |
Organizations | PARTIALLY Organization membership isn’t migrated. If a source organization has 2 users, the same organization migrated to the destination will have 0 users. |
Request types | AVAILABLE |
Portal groups | AVAILABLE |
Portal settings | FUTURE |
SLAs | AVAILABLE |
Queues | AVAILABLE |
Calendars | AVAILABLE |
Email requests | FUTURE |
Forms | FUTURE |
Satisfaction settings | FUTURE |
Access settings | FUTURE |
Customer permissions | FUTURE |
Customer notifications | FUTURE |
Attachment security | FUTURE |
Sender names | FUTURE |
Templates (Premium Jira Cloud Only) | FUTURE |
Language settings | FUTURE |
Knowledge base | FUTURE |
Knowledge base labels | FUTURE |
Knowledge base enabled request types | FUTURE |
Reports | FUTURE |
Widgets | FUTURE |
Automation rules | FUTURE |