Supported Configuration Elements

On this page:

Supported configuration elements in cloud-to-cloud deployments

The table below lists the configuration CMJ Cloud is able to deploy in the cloud-to-cloud use case.

✅ Supported

❌ Not yet supported

⚠ Supported with some specifics

Configuration	CMJ Cloud
Jira Work Management projects	✅
Jira Software company projects Project configuration ✅ Boards and Sprints ✅	✅
Jira Service Management projects	❌
Boards	✅
Filters	⚠ Only the filters associated with boards in the deployment scope are moved. JQL isn’t transformed.
Users	✅
Groups	⚠ Group membership will not be transferred
App data	❌

Deploying boards, filters, and sprints

When deploying boards, filters, and not closed sprints from a Jira Cloud site, CMJ Cloud is able to:

add the ones that don’t exist in the destination Jira Cloud, and
modifies the existing ones on the destination Jira Cloud if differences are detected.

When migrating from Jira Server to Cloud, however, Jira Server boards, filters, and sprints are only added to Jira Cloud. For such migrations, the boards, filters, and sprints existing in the destination aren’t modified in any way.