• Products
  • Documentation
  • Resources

What migrates in a cloud-to-cloud migration for Jira

Important note about cloud-to-cloud migrations

Before you start a cloud-to-cloud migration, understand what you need to do to reduce your chance of encountering any errors and what a migration may mean for your billing. Learn about preparing for a cloud-to-cloud migration


A cloud-to-cloud migration will migrate data from one cloud site to another without overwriting any existing data. This means you can migrate data to a new site or a site with existing data. Learn about how cloud-to-cloud migration links data between sites

Cloud-to-cloud migration currently supports company-managed projects in Jira Software and Jira Work Management only. There are some issue fields, configurations, and other project types that we don’t support yet. This page outlines what is and isn’t migrated in a cloud-to-cloud migration.

What is migrated

Users and groups

  • Users and groups from active directories

Jira Work Management project data

  • Project details:

    • Name

    • Key

    • Project type

    • Project category

    • Description

    • Project lead

    • Default assignee

  • Project roles

  • Issue types

  • Issue type scheme

  • Issue type screen scheme

  • Workflow scheme

  • Field configuration scheme

  • Workflows (links to the migrated workflow scheme with status and transitions)

  • Workflow functions

    • Validator: permission

    • Condition: permission, allow only reporter

    • Post function: update resolution field

    • assign to current user

    • assign to reporter

    • assign to lead

  • Screens

  • Screen schemes

  • Status category

  • Permission schemes

  • Issue security (level, scheme, permission)

Issue data

  • Summary

  • Description

  • Issue type

  • Status

  • Priority

  • Resolution

  • Labels

  • Reporter

  • Assignee

  • Due date

  • Subtasks

  • Some custom fields

    • Text

    • Date

    • Number

    • Time

    • Labels

    • Select list (single choice)

    • Checkbox

    • Radio button

    • User picker (single, multiple)

    • Group custom fields

    • Multi-line text

    • Environment

  • @mentions

  • Watchers and votes

  • Issue links (including link types)

  • Attachments (media, files)

  • Comments

  • Comments with security

  • Story points

  • Time spent

  • Issue history

  • Issue work log

Jira Software project data

  • Issue rank

  • Epics (epic link)

    • Epic name

    • Epic color

    • Epic status

    • Issue rank

  • Original Estimate

  • Remaining Estimate

  • Flagged

  • Components

  • Environment

  • Sprints

  • Versions (affects versions, fix versions)

Jira Software Boards

(for those connected to projects being migrated)

  • Boards linked to one project only

  • Boards

    • Name

    • Administrators

    • Filters and permissions

    • Shared permission

    • Location

  • Advanced board settings

    • Column names and status mapping

    • Swimlanes

    • Sprint permissions

    • Time statistic/estimation

Project setup

  • Workflow functions

    • Validator: required field, field changed

    • Condition: user in group, user in project role, field value

    • Post function: update custom field

What isn’t migrated

Users and groups

  • Jira Service Management users (only Jira Service Management agents are migrated)

  • Users and groups from inactive directories (to migrate inactive directories, make them active before migrating)

User profiles

  • User avatars (users will need to update their avatars after migrating)

  • Passwords (unless you've set up SSO, users will need to reset their passwords after migrating)

  • Timezones (timezone information on a per-user profile will be lost)

Project types

  • Jira Service Management projects

  • Team-managed projects

  • Archived projects (to migrate archived projects, restore them before migrating)


  • Apps and app data (to migrate app data, contact the respective Marketplace Partner)

Jira Software Boards

(for those connected to projects being migrated)

  • Boards linked to more than one project

  • Boards

    • Shared permission

  • Advanced board settings

    • Quick filters

    • Card colors

    • Subquery

Project setup

  • Some custom fields

    • Single and multi-version picker

    • URL

    • Select list (cascading)

    • Select list (multiple choice)

    • Project picker

  • Custom field language translations

  • Workflow functions

    • Condition: subtask blocking

    • Post function: clear field value, copy value from other field, delegating

  • Notification schemes (projects are added to the default schemes in cloud)

  • Project avatars

  • Links to issues or entities not migrated

Entities and permissions

  • Global permissions

  • General configuration (e.g., timezone, language)

  • Dashboards

  • Cross-project boards

  • Boards not connected to the projects being migrated

  • Filters on boards not migrated

  • Confluence links (links in destination site will continue to link to source site)

Depending on your needs, you may need to consider other ways to move data between Jira Cloud sites. Learn about other methods and their limitations

Last modified on Oct 6, 2021
Cached at 1:43 AM on Oct 16, 2021 |

Additional Help