• Products
  • Documentation
  • Resources

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

Starting January, 2024, we’re renaming the Jira cloud-to-cloud migration feature to Copy product data. We’re moving this feature to Atlassian Administration at admin.atlassian.com in a unified experience along with Confluence cloud-to-cloud data copy.

We’re rolling out the change slowly, so if you aren’t able to access this feature by logging into your Jira Cloud and selecting System > Settings > Migrate cloud site, we recommend you go to admin.atlassian.com, and select:

Settings > Data management Copy product data

You’ll need to have organization administrator permissions to access and use the Copy product data feature.

Learn more about this change



Move data from one instance of your cloud to another. You can move data to a new instance or an instance with existing data without overwriting existing data. This page outlines what is and isn’t moved in a cloud-to-cloud migration.

Before you start moving data, learn about:

What is moved and what isn’t


What is moved

What isn’t moved

Users and groups

  • Users and groups from active directories including Jira Service Management agents

  • Portal-only customer accounts and Atlassian accounts with Customer role assigned

  • Customer organizations related to selected Jira Service Management projects

Customer organizations that are not related to selected Jira Service Management projects

Project types

  • Company-managed projects

  • Team-managed projects

    • Any related issues, entities, and configurations

    • Any project references within company-managed projects

  • Archived projects


Project data

  • Workflow functions

    • Validator: permission, required field, field changed

    • Condition: permission, allow only reporter, user in group, user in project role, field value

    • Post function: update resolution field, update issue field

    • assign to current user

    • assign to reporter

    • assign to lead

  • Custom field language translations

  • Workflow functions

    • Condition: subtask blocking

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

  • Notification schemes (Supported for team-managed projects only. For company-managed projects, projects added to the default schemes in cloud)

  • Project avatars

  • Links to issues or entities not migrated

  • Automation rules (including project-level automation rules)

  • Custom issue type icons

  • Mail handlers


Jira 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)

  • Screens

  • Screen schemes

  • Status category

  • Permission schemes

  • Issue security (level, scheme, permission)

  • 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 Service Management project data

  • Queues

  • Request types

  • Request type groups

  • Customer organizations

  • Customer organization user associations

  • SLA calendars

  • SLA Time Metric configuration

  • Approvals

  • Customer notifications

  • Reports

  • CSAT setting

  • CSAT comment

  • Portal settings

  • Language support

  • Features

  • Both team and company-managed projects

  • Forms (and form data attached to issues)

  • Knowledge base

  • Jira automation

  • Email settings

  • Assets

  • Services

  • On-call Schedule

  • Change calendar

  • Chat

  • Widget

  • External resources

  • Login message

  • Site-wide announcement

  • Customized look and feel for help center

  • Help center home page layout

  • Issue collector

  • Versions

  • People

Issue data

  • Summary

  • Description

  • Issue type

  • Status

  • Priority

  • Resolution

  • Labels

  • Reporter

  • Assignee

  • Due date

  • Subtasks

  • Some custom fields

    • Text

    • Date

    • Number

    • Time

    • Labels

    • URL

    • Select list (single choice)

    • Select list (multiple choice)

    • Checkbox

    • Radio button

    • User picker (single, multiple)

    • Single and multi-version picker

    • Group custom fields

    • Multi-line text

    • Environment

    • Asset object

  • @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

Some custom fields

  • Select list (cascading)

  • Project picker

  • Affected services

  • Responders

Jira boards

  • Boards linked to one project only

  • Boards

    • Name

    • Administrators

    • Filters and permissions

    • Share permission

    • Location

  • Advanced board settings

    • Column names and status mapping

    • Swimlanes

    • Time statistic/estimation

    • Quick filters

    • Card colors

    • Subquery

  • Boards

    • Shared permission

  • Boards linked to more than one project

  • Filters linked to more than one project

  • Filters not linked to any boards

Entities and permissions

Remote links

  • Global permissions

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

  • Dashboards

  • Boards with non-existent/deleted filters won't be migrated

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



Apps and app data. To migrate app data, contact the respective Marketplace Partner.

Advanced Roadmaps


Advanced Roadmaps plans and Advanced Roadmaps data. View open feature request


Additional Help