Cloud-to-cloud migration is now available on all Jira Cloud sites For the latest guidance on performing a cloud-to-cloud migration, visit the new support documentation. This EAP documentation will be archived on May 31, 2022. |
Thank you for being a part of the early access program. This community site allows you to provide feedback through page or inline commenting. We will use your comments to improve our product and documentation. Anybody on the internet can view your comments. To know your rights and responsibilities as a customer of our cloud products, read our Atlassian Cloud Terms of Service. |
As cloud-to-cloud migration for Jira is still in development, some projects and issue fields or configurations are not yet supported. This page outlines what isn’t currently migrated.
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 how cloud-to-cloud migration links data between sites
What is migrated | What isn't migrated |
---|
Users and groups from active directories Jira Work Management project dataProject 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 - basic links to the correctly migrated workflow scheme with status and transitions Workflow functions Screens schemes Screens Status category (check comments, part of code and not a separate entity) Permission schemes Issue security (level, scheme, permission)
Issue data Jira Software project dataIssue rank Epics (epic link) Epic name Epic color Epic link Epic status
Issue history (including some custom fields) Epic Name Epic Color Epic Link Epic Status Issue rank
Original Estimate Remaining Estimate Flagged Components Environment Sprints Versions (affects versions, fix versions) Filters associated with boards being migrated Boards connected to only one project that is being migrated
Jira Software Boards (Connected to projects selected in the migration)Boards Name Administrators Filters and permissions Shared Permission Location
Advanced board settings
Project setup Workflow functions Validator: required field, field changed Condition: user in group, in project role, field value Post Function: update custom field
| 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)
App data Jira Software Boards (for those connected to projects being migrated) Project setup Custom fields 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)
|