Documents to help prepare you to migrate your Atlassian server products.
Articles to help assess your migration costs license status.
Learn about migration timelines, roadmaps, app and Atlassian Access with these resources.
Look up resources on Jira and Confluence cloud, data hosting regions, LDAP, and ADFS.
Pre-migration checklists for Jira, Confluence, and Bitbucket.
A collection of topics that help prepare you to migrate your apps to the cloud.
Native tools and resources that will help with your migration.
Documents to help you use Jira Site Import to migrate to cloud.
Documents that walk you through using the Confluence Cloud Migration Assistant to migrate to cloud.
Resources to help get started and testing after you migrate.
Depending on your current self-hosted version, you may need to upgrade before migrating from Jira server to cloud using the Jira Cloud Migration Assistant. Below are guidelines for which self-hosted versions are compatible.
Jira Software or Jira Core
To use the Jira Cloud Migration Assistant, you’ll need to be on Jira Server version 7.6.0 or later.
If you're on an earlier version than this, you'll need to upgrade before you can use the migration assistant.
Upgrading with an expired server license
If you're on an unsupported server version and don't have active maintenance on your server license (which is required to upgrade), you can use a free trial license to upgrade in preparation for the migration. Learn more about how to migrate to cloud with an expired license
Jira Service Management
If you’re migrating Jira and need to integrate Bitbucket Server or Bamboo, refer to the Application links version matrix to make sure you are on the correct version of Bitbucket Server or Bamboo before starting your migration.
The Jira Cloud Migration Assistant is now available on Data Center. Before using the migration assistant on your Data Center instance, check what data is and isn’t migrated.
Limited recovery support
When installed on Data Center, Jira Cloud Migration Assistant supports limited recovery (in the case of a server failure) during migrations. To maximize recovery capabilities, we recommend only running one migration at a time per two Data Center nodes. This capability is only available on the Jira Cloud Migration Assistant.
In the case of a server failure during the migration, the Jira Cloud Migration Assistant will:
During export: Automatically recover the migration up to two times - as long as there are two Data Center nodes per migration, and both don’t crash at the same time.
During import: Automatically recover the migration (unlimited times) - as long as there are two Data Center nodes per migration, and both don’t crash at the same time.
In the event that all Data Center nodes crash, then recovery (as per above) isn’t guaranteed. Although, it could occur if 1 node (per migration) is restarted within 3 minutes.
Internet Explorer 11 is no longer supported for Jira Cloud Migration Assistant. If you are still using Internet Explorer 11, we recommend switching to one of our supported browsers. See this community post for more details
More information and support
We have a number of channels available to help you with your migration.
For more migration planning information and FAQs, visit the Atlassian Cloud Migration Center.
Have a technical issue or need more support with strategy and best practices? Get in touch.
Looking for peer advice? Ask the Atlassian Community.
Want expert guidance? Work with an Atlassian Partner.
Was this helpful?