• Products
  • Documentation
  • Resources
Products
Documentation
Resources
Atlassian Support
/
Migration Resources
/
Jira Cloud Migration Assistant
/
How Jira Cloud Migration Assistant migrates data

What gets migrated with the Jira Cloud Migration Assistant

The Jira Cloud Migration assistant adds data to a Jira Cloud site without overwriting any existing data. This means you can migrate data to a new Cloud site or a site with existing data.

What can be migrated differs between the migration options:

  • Choose what to migrate

  • Migrate all data at once (same as Jira site import)

Migration option: Choose what to migrate

Here are the details on what is and isn’t migrated with the Choose what to migrate option.

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

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

    • Legacy automation rules

    • Customer notification template

    • Portal settings

    • Calendar

    • Workflow

    • Language support settings

    • Customer satisfaction settings

    • Reports

  • Queue

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

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

Advanced Roadmaps plans

  • Plans with issue sources as projects

  • 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

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. Learn more about Jira apps with migration paths

Other project types

  • Archived projects

Project setup

  • Custom field language translations

  • Workflow functions

    • Properties

    • Triggers

  • 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 following apps is not included in the migration:

    • Automation for Jira

    • Assets

    • ProForma

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

Some items from Advanced Roadmaps plans

  • Classic plans

  • Plans that have issue sources as private filters

  • Unsaved scenario data

  • Saved views

  • User defined custom fields of type

    • Parent Link

    • Team

    • Target start

    • Target end

Other issue types

  • Archived issue

Migration option: Migrate all data at once

Here are the details on what is and isn’t migrated with the Migrate all data at once option.

What is migrated

What isn’t migrated

  • Users, groups and permissions

  • Site data, including projects and issues

  • Jira configuration, including project setup, custom fields, and workflow schemes

  • Custom main handlers

  • Application links

  • Attachments

  • Project avatars

  • Logos

  • Portfolio for Jira: Note that Portfolio features differ in Server and Cloud. We recommend including Portfolio for Jira Cloud in your user acceptance testing to understand what differences your users can expect after migrating.

  • The migrator's group permissions: If you're the person performing the migration, you'll need to re-add yourself to your groups after migrating

  • Apps: App data is not included in the backup when migrating from Jira Server to Jira Cloud. Some apps have the capability to export and import their data but you'll need to check with the app vendors or their documentation to confirm if this is possible. Your licenses for Atlassian Marketplace apps can be viewed on https://my.atlassian.com/

  • Users managed by external directories: We recommend using the Jira Cloud Migration Assistant to migrate your data if you have users managed by external directories. If you can't use the Jira Cloud Migration Assistant to migrate all data, consider using it to migrate users only.

  • 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

Check what’s migrated in the pre-migration report

You can check what’s included in you migration in the pre-migration report. To get it, complete one of the following steps:

  • After you create a migration plan and add data to it, proceed to the Review your migration step. The Logs and reports section is included there.

  • View the details of your migration plan from the Migrations dashboard. The Logs and reports section is included there.

Learn more about logs and reports

Adding additional entities using CSV import

You can 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 apps

To add missing fields using CSV import:

  1. Create the missing fields in Jira Cloud:

    1. Create any custom fields that weren’t 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. Add 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 pageMigration option: Choose what to migrateWhat is migratedWhat isn't migratedMigration option: Migrate all data at onceWhat is migratedWhat isn’t migratedCheck what’s migrated in the pre-migration reportAdding additional entities using CSV importMore information and support
CommunityQuestions, discussions, and articles