• Products
  • Documentation
  • Resources
Products
Documentation
Resources
Atlassian Support
/
Migration Resources
/
Jira Cloud Migration Assistant

What gets migrated with the Jira Cloud Migration Assistant

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 premigration 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

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

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

    • automation rules

    • customer notification template

    • portal settings

    • calendar

    • workflow

    • language support settings

    • customer satisfaction settings

    • reports

  • queue

Jira Work Management (formerly 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

  • 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

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

App and app data

  • Advanced Roadmaps (formerly Portfolio for Jira)

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

Other project types

  • archived projects

Project setup

  • custom field language translations

  • workflow functions

    • properties

    • triggers

  • notification schemes - projects are added to the default schemes in Cloud

  • mail handlers

  • project avatars

  • links to issues or entities that are not migrated

  • custom issue type icons

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

  • webhooks

Users and groups

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

Specific app data

  • app data of the ‘Automation for Jira’ app is not included in the migration

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

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.

  1. Manually create the missing fields:

    1. Manually create any custom fields that were not migrated.

    2. Assign the custom fields to the relevant screens (using data from the Jira Server logs, look for the string unsupported custom field).

  2. Top up data for missing fields with CSV export-import:

    1. Export data for all the fields and issues from Server. Create a search and export as CSV

    2. Edit the CSV (in Excel, for example).

      1. Leave only issue key, issue summary and all the missing fields that you want to top up. For example, version picker.

      2. Include any other custom fields that are used on issue screens based on data from logs (optional).

    3. 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:

Additional Help

On this pageWhat is migratedWhat isn't migratedAdding additional entities using CSV importMore information and support
CommunityQuestions, discussions, and articles