• Users and groups from active directories

  • Jira Cloud users (in both software and business projects), and Jira Service Management agents

  • Deleted users from Server are migrated as “Former user”

    • Deleted users connected who are part of projects being migrated will be created in cloud

  • All groups in active directories

  • Users managed by external directories

• Users and groups from inactive directories

  • To migrate these users, make the directories active.

• Jira entities and permissions

• Jira Software project data and boards

• Jira Core project data

Any data related to issues

Jira Service Management project data

Advanced Roadmap plans

Marketplace apps and app data

Project setup data

Jira global entities and permissions

User profiles

Services from Jira Server and Jira Data Center

• Jira global entities and permissions

  • Cross-project boards

  • Cross-project filters

  • Boards that belong to inactive users

  • Filters on boards that are not migrated

  • Filters that share permissions with projects

  • Dashboards

  • Filter subscriptions

• Project setup

  • Custom field language translations

  • Workflow functions

    • Properties

    • Triggers

  • Project avatars

  • Canned responses

  • Links to issues or entities that are not migrated

  • System dashboards

  • Custom issue type icons

  • Project shortcuts

  • Workflow UI Diagram Positioning

  • Knowledge base articles linked to service projects

  • Mail handlers

  • Issue collectors

  • Issue redirection of moved issues won’t work for migrated Jira tickets

  • Custom fields

    • Issue picker

  • Kanban board sub-filter

  • Issue type translations

• 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 global entities and permissions

  • Global permissions

  • General configuration (timezone, language, etc)

  • Webhooks

  • Customized filter columns

  • Comment reactions

  • Boards not connected to the projects being migrated

• Jira Software Boards

  • Boards

  • Name

  • Administrators

  • Filter & permissions

  • Location

  • Advanced board settings

    • Column names and status mapping

    • Quick filters

    • Swimlanes

    • Sprint permissions

    • Card colors

    • Time statistic / estimation

• Users and groups from inactive directories

  • Make directories active to migrate these users

• Jira Service Management project data

  • Jira Service Management projects

  • All users including agents

  • All groups

  • All customers

  • Request type

  • Request type groups

  • Custom fields

  • Customer organization

    • Approval

    • SLAs

  • Project settings

    • Legacy automation rules

    • Customer notification template

    • Portal settings

    • Calendar

    • Workflow

    • Language support settings

    • Customer satisfaction settings

    • Reports

  • Queue

• 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

  • Activity Stream: activity stream is not migrated to cloud

  • Jira user properties: Jira user properties are not migrated to cloud

• Jira Core project data (Note: These entities are also part of Jira Software and Jira Service Management.)

  • 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

  • Workflow transition properties

  • Screens schemes

  • Screens

    • Tabs

  • Status category

  • Permission schemes

  • Notification schemes

    • Only system events with default notifications are migrated. User-defined custom notifications are not migrated. Custom events are also not migrated.

  • Issue security

  • Priorities and priority schemes

• Some items from Advanced Roadmaps plans

  • Classic plans

  • Scenarios

  • Unsaved scenario data

  • Saved views

• Issue data

  • Summary

  • Description

  • Issue type

  • Issue number

  • Status

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

    • Text field (read only)

    • 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

• Other issue types

  • Archived issue

• Services from Jira Server and Jira Data Center

• Advanced Roadmaps plans

  • Plans with issue sources as projects

  • Plans that have issue sources as private filters

  • Plans with issue sources as single- or cross-project boards

  • Plans that have issue sources as filters

  • Users and groups

  • Shared teams

  • Global configuration

  • Custom issue types, custom fields and custom hierarchy mapping

  • Live plans will be migrated as plans with improved interface

  • User defined custom fields of type

    • Parent Link

    • Team

    • Target start

    • Target end

• Marketplace apps and app data*

  • Advanced Roadmaps (formerly Portfolio for Jira)

  • Automation for Jira. More on what automations are migrated

  • ProForma app data

  • Marketplace partners (also known as app vendors) need to provide an automated migration path for the Jira Cloud Migration Assistant to migrate app data. Learn more about Jira apps with migration paths

  • Assets (formerly Insights)*

• 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

• Archived projects