Migrate Jira Software configuration

Owned by
Rosen Marinkov
Last updated: May 22, 2024 by
Julver Petrova (Deactivated)
2 min read

On this page:

Migrate Jira Software configuration

By pairing our Cloud Migration Tool and CMJ Cloud apps, you can migrate Jira Software projects together with boards, filters, and sprints from a Jira Server/Data Center instance to a Jira Cloud site.

We do not modify existing boards, filters, and sprints in the cloud site. This way, we ensure that the Jira Software configuration from the server instance will be added to the cloud without overwriting the existing configuration there.

As the Cloud Migration Tool is still in development, we advise checking the complete list of Jira configuration elements we’re currently able to migrate.

Below, you'll find the built-in principles for migrating boards, filters, and sprints to a new or existing Jira Cloud site with the latest version of the Cloud Migration Tool.

Boards

  • Jira Server and Jira Cloud boards are matched by name, type, and project key for project boards or user key for user boards.

  • Boards associated with a project through a filter are migrated. A board’s entire configuration is migrated, including quick filters, swimlanes, etc.

  • Boards for sprints referenced in issues or an issue’s history are also migrated.

  • We don’t modify existing boards in the Jira Cloud site. This means that a board from the Jira Server instance won’t be migrated if it matches an existing board in the Jira Cloud site.

Filters

  • Jira Server and Cloud filters are matched by their name and owner.

  • Filters associated with boards being migrated are migrated too. 

  • We don’t modify existing filters in the Jira Cloud site. This means that a filter from the Jira Server instance won’t be migrated if it matches an existing filter in the Jira Cloud site.

  • Before filters are migrated, their JQL entry is validated.

How do we handle invalid JQLs in filters?

If the JQL entry of a filter being migrated isn’t valid on the Jira Cloud site, the JQL is migrated to the Cloud as is. Therefore, after the migration, you need to check all filters to ensure everything works as expected.

There are many reasons why a JQL entry may not be valid. For example, it might contain unsupported JQL functions or custom fields.

Sprints

  • Jira Server and Cloud sprints are matched by their boards, name, state, start date, and end date attributes. If there are multiple sprints with the same attributes, they are also matched by their order.

  • Sprints that are part of boards being migrated are migrated too.

  • Sprints referenced in issues or an issue's history are migrated, even if these sprints don’t have an associated board.

  • Sprints that do not belong to any board are migrated.

  • We don’t modify existing sprints in the Jira Cloud site. This means that a sprint from the Jira Server instance won’t be migrated if it matches an existing sprint in the Jira Cloud site.