What gets migrated with the Jira Cloud Migration Assistant

Jira Software project data

• Issue rank

• Epics (epic link)

  • Epic name

  • Epic color

  • Epic link

  • Epic status

• Issue history (including some custom fields)

  • Epic Name

  • Epic Color

  • Epic Link

  • Epic Status

  • Issue rank

  • Original Estimate

  • Remaining Estimate

  • Flagged

  • Components

  • Environment

• Sprints

• Versions (affects versions, Fix versions)

• Filters associated with boards being migrated

• Boards connected to only one project that is being migrated

Jira Work Management project data

• Project details:

  • Name

  • Key

  • Project type

  • Project category

  • Description

  • Project lead

  • Default assignee

• Project roles

• Issue types

• Issue type scheme

  • Default issue type

• Issue type screen scheme

• Workflows scheme

• Field configuration scheme

• Workflows - basic links to the correctly migrated workflow scheme with status and transitions

• Workflow functions

  • Full list of workflow rules that are migrated

• Screens schemes

• Screens

  • Tabs

• Status category

• Permission schemes

• Issue security

Issue data

• Summary

• Description

• Issue type

• Issue number

• Status

• Priority

• Resolution

• Labels

• Creator

• Reporter

• Assignee

• Due date

• Subtasks

• Some custom fields

  • Text

  • Date

  • Number

  • Time

  • Labels

  • Select List (single choice, multiple choice, cascading select)

  • Checkbox

  • User Picker (single/multiple)

  • Project picker (single project)

  • Group custom fields

  • Multi-line text

  • Radio button

  • Environment

  • URL

• @mentions

• Watchers/ Votes

• Issue links (including link types)

• Attachments

• Comments

• Comments with security

• Story points

• Time spent

• Issue history

• 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)

• Boards

  • Name

  • Administrators

  • Filter & permissions

  • Location

• Advanced board settings

  • Column names & status mapping

  • Quick filters

  • Swimlanes

  • Sprint permissions

  • Card colors

  • Time statistic / estimation

Users and groups from active directories

• Jira Work Management 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

Project setup

• Other custom fields

  • Single and Multi-version picker

• Custom field language translations

• Workflow functions

  • Validator: 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

• Project avatars

• 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

• Global permissions

• General configuration (timezone, language, etc)

• Dashboards

• Cross-project boards

• Boards not connected to the projects being migrated

• Boards that belong to inactive users

• Filters on boards that are not migrated

• Confluence links

• Webhooks

Users and groups

• Jira Service Management customers - Only agents are migrated

• Users and groups from inactive directories - make directories active to migrate them

App data

• 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 profiles

• 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

• Archived issue