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
Jira Software project data
Epics (epic link)
Issue history (including some custom fields)
Versions (affects versions, Fix versions)
Filters associated with boards being migrated
Boards connected to only one project that is being migrated
Jira Core project data
Issue type scheme
Issue type screen scheme
Field configuration scheme
Workflows - basic links to the correctly migrated workflow scheme with status and transitions
Condition: permission, allow only reporter
Post Function: update resolution field, assign to current user, assign to reporter, assign to lead
Some custom fields
Select List (single choice)
User Picker (single/multiple)
Group custom fields
Issue links (including link types)
Comments with security
Issue work log
- Issue key history
Jira Software Boards - connected to projects selected in the migration (boards linked to more than one project will not be migrated)
Filter & permissions
Advanced board settings
Column names & status mapping
Time statistic / estimation
Users and groups from active directories
Jira Core and Jira Software users, and Jira Service Management agents
Deleted users from server are migrated as “Former user”. Only deleted users connected to the projects being migrated will be created in cloud.
All groups in active directories
- Users managed by external directories.
Other project types
- Archived projects
What isn't migrated
Other Custom Fields
Single and Multi-version picker
- Select List (cascading)
Select List (multiple choice)
- Project picker
Custom field language translations
Validator: required field, field changed
Condition: user in group, in project role, field value, subtask blocking
Post Function: clear field value, update custom field, copy value from other field, delegating
Notification schemes - projects are added to the default schemes in cloud.
- Mail handlers
Links to issues or entities that are not migrated
Other project types
- Jira Service Management projects (formerly Jira Service Desk)
Jira global entities and permissions
General configuration (timezone, language, etc)
Boards not connected to the projects being migrated
Filters on boards that are not migrated
Users and groups
Jira Service Management customers - Only agents are migrated.
Users and groups from inactive directories - make directories active to migrate them.
Apps. App data is not included in the backup when migrating from Jira Server to Jira Cloud. Some apps do have the capability to export and import their data but you'll need to check with the app developers or their documentation to confirm if this is possible. Your licenses for Atlassian Marketplace apps can be viewed on https://my.atlassian.com/.
Portfolio for Jira is handled the same as other server apps.
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.
Other issue types
After migrating, it’s possible to manually add missing fields using CSV import. Some of the fields that aren’t migrated include:
Adding additional entities with CSV
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.