Documents to help you prepare to migrate your Atlassian Server products.
A collection of topics that help prepare you to migrate your apps to the Cloud.
Ensure you’re ready to migrate with these pre-migration checklists for Jira, Confluence, and Bitbucket Server or Data Center.
Documents that walk you through using the Confluence Cloud Migration Assistant to migrate to Cloud.
Documents that walk you through using the Bitbucket Cloud Migration Assistant to migrate to Cloud.
Documents to help you use Jira Site Import 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.
Upgrade to Jira Cloud Migration Assistant 1.7.3 or higher
To give you a more stable and reliable migration experience, we’ve improved the way attachments and other media files are migrated.
Starting September 19, 2022, we recommend you upgrade to Jira Cloud Migration Assistant 1.7.3 or higher for all your migration needs in future.
Starting January 31, 2023, you won’t be able to use 1.7.1 and lower of the Jira Cloud Migration Assistant.
For any further details or technical concerns, contact us.
The Jira Cloud Migration Assistant will add data to a Jira Cloud site without overwriting any existing data. This means you can migrate data to a new Cloud site or a Cloud site with existing data. Not all data can be migrated yet with the latest version of the Jira Cloud Migration Assistant. Learn how the Jira Cloud Migration Assistant links your data.
This page outlines what is and isn’t migrated with the migration assistant. To see what this means for your data, we recommend using the migration assistant’s pre-migration report to check what will be migrated. This can be found under logs and reports when you get to the Review your migration screen.
If you’re unable to use the Jira Cloud Migration Assistant to migrate, you can compare other Cloud migration methods to move your data from Server or Data Center to Cloud.
What is migrated
What isn't migrated
Jira Software project data
Jira Service Management project data
Jira Work Management (formerly Jira Core) project data
Note: these entities are also part of Jira Software and Jira Service Management.
Users and groups from active directories
App and app data
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:
version picker (single and 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, 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:
Was this helpful?