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.
The Jira Cloud Migration Assistant will only add data to your cloud site, not overwrite it – meaning you can move to a new or existing cloud site without issue.
The Jira Cloud Migration Assistant is still currently in development. When you migrate, not all data will be copied to your cloud site. See the table below for detail on what is migrated with the most recent version of the Migration Assistant.
If you are unable to use the Jira Cloud Migration Assistant to migrate, you can use the Jira Site Import method instead (although it has other limitations). Use our guide to determine the best migration method for your situation.
What is migrated
What isn't migrated
Jira Software project data
Jira Core project data
Jira Software Boards - connected to projects selected in the migration (boards linked to more than one project will not be migrated)
Users and groups from active directories
Other project types
Other project types
Jira global entities and permissions
Users and groups
Other issue types
Adding additional entities using CSV import
After migrating, it’s possible to manually add missing fields using CSV import. 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, URL, project picker
Include any other custom fields that are used on issue screens (using data from logs).
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?