Documents to help you prepare 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.
Everything you need to know about moving your data from one cloud site to another.
As the Jira Cloud Migration Assistant is still in development, not all data will be migrated. This page outlines what is and isn’t migrated with the latest version of the Jira Cloud Migration Assistant.
The Jira Cloud Migration Assistant will add data to your cloud site without overwriting existing data. This means you can move to a new or existing cloud site. Learn how the Jira Cloud Migration Assistant links your data
If you’re unable to use the Jira Cloud Migration Assistant to migrate, there are other ways to move your data from server or Data Center to cloud. Learn about other methods and their limitations
What is migrated
What isn't migrated
Jira Software project data
Jira Work Management (formerly Jira Core) project data
Note: These entities are also part of Jira Software.
Users and groups from active directories
Other project types
Other project types
Jira global entities and permissions
Users and groups
Specific app data
Other issue types
Adding additional entities using CSV import
It’s possible to manually add missing fields using CSV import after migrating. Some of the fields that aren’t migrated include:
Cascading select list
Version picker (single & multi)
Any custom fields from add-ons
Follow the instructions below to add these fields or contact the support team for assistance. You’ll need access to the Jira Server logs to do this.
Manually create the missing fields:
Manually create any custom fields that were not migrated.
Assign the custom fields to the relevant screens (using data from the Jira Server logs, look for the string unsupported custom field).
Top up data for missing fields with CSV export-import:
Export data for all the fields and issues from server. Create a search and export as CSV.
Edit the CSV (in Excel, for example).
Leave only issue key, issue summary and all the missing fields that you want to top up. For example: cascading select list, version picker
Include any other custom fields that are used on issue screens based on data from logs (optional).
Run the CSV import in your cloud site and select the project previously migrated with the Jira Cloud Migration Assistant.
After completing these steps, all the issues should be updated with missing field data. Projects should now have up-to-date configuration, data and can be considered fully migrated.
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?