About the Jira Cloud Migration Assistant early access program Edited

Jason Wong Atlassian Team Aug 28, 2019

We understand that migrating from Jira Server to Jira Cloud can be daunting and difficult. Many of you have also asked for an easier way to move single projects from server to cloud. The Jira Cloud Migration Assistant will make it easier to move from server to cloud in a way that best suits you.

Screenshot 2019-08-29 18.31.01.png

The migration assistant is currently in development and soon we will be looking for people to participate in a trial. The Jira Cloud Migration Assistant early access program will allow you to try an early version of the Jira Cloud Migration Assistant prior to the official release.

The goal of this program is to allow you to test and benefit from new features in advance and provide us with some useful feedback as we continue to build this tool.

The early version of the migration assistant is not a full release and will not have full features. The trial of the Jira Cloud Migration Assistant is most suitable for people who are planning to:

  • perform a Jira Core or Jira Software migration from server to cloud in October/November 2019

  • migrate individual projects from server into a new or existing cloud site using CSV 


How to participate in this program

After submitting the form, you’ll be contacted if your migration plans match our program criteria and we have available spots.

Once the Jira Cloud Migration Assistant is available, we'll contact eligible customers via a Jira ticket at getsupport.atlassian.com with instructions on how to use it.


We want your feedback

We will be asking for feedback from all participants in the early access program. This feedback will help us improve the migration assistant for all customers and will help us understand your needs.

You can give us feedback through the same Jira ticket that the support team will assign to you for this program.

We’re looking for feedback on:

  • Whether the experience worked for you, including any bugs or issues

  • What documentation or information you need to use the tool

  • What was helpful and easy

  • What was difficult or just didn’t work


What will (and won’t) be migrated

When you use the early access version of the Jira Cloud Migration Assistant, most of your project data will be migrated. However, this is not a full release of the tool, so there may be some things that don’t get copied over. The table below outlines what will be migrated and what won’t.

The early access program will be suitable for you, if most of the data you need to migrate is in the first column.

Items that aren’t migrated may be included in future versions of the migration assistant.

Data that is migrated Data that isn’t migrated
Project setup
  • Project details
    • name
    • key
    • project type
    • project category
    • description
    • project lead
    • default assignee
  • project roles
  • issue types
  • issue type scheme
  • issue type screen scheme
  • workflows scheme
  • field configuration scheme
  • workflows - basic: links to the correctly migrated workflow scheme with status and transitions.
  • screens schemes
  • screens
  • status category
  • permission schemes
  • issue security


Issues - basic fields only

  • summary

  • description

  • issue type

  • status

  • priority

  • resolution

  • labels

  • reporter

  • assignee

  • due date

  • subtasks

  • some custom fields

    • text

    • date

    • number

    • time

    • labels

    • dropdown

    • checkbox

    • user picker (single/multiple)

  • @mentions

  • watchers / votes

  • issue links (including link types)

  • attachments

  • comments

  • comments with security

  • issue history



Users and groups

Users and groups will be migrated each time*. In the tool, you will have an option to choose whether you want to give your users Jira access or not.

Project setup

  • other custom fields

  • workflows - advanced: status, transitions, transition options (Properties, Triggers, Conditions, Validators, Post Functions)

  • project avatars


Jira Software fields

  • epics (epic link)

  • versions (affects versions, Fix versions)

  • sprints

  • components

  • issue rank

  • Jira Software specific custom fields and custom field values in issues

  • estimates (story points)

  • estimates (time)

  • Jira Software fields:

    • environment

    • linked issues


Jira Software boards

  • boards

    • name

    • filter

    • column names (no column status mappings)

    • location

  • advanced board settings

    • column status mapping

    • quick filters

    • swimlanes

    • sprint permissions

    • card colors

    • time statistic / estimation


Jira global entities

  • global permissions

  • general configuration (timezone, language, etc)

  • dashboards

  • cross-project boards

  • filters


App data - No app data is migrated

*More information about how users and groups are migrated will be given to participants of the program.


Planning and troubleshooting your migration

It’s important to be prepared for your migration. Many of the steps in our Jira migration planning guide are still relevant even when using the early access version of the Jira Cloud Migration Assistant. You will also find other relevant information on our Jira migration resources page.

If selected for the early access program, you’ll also be given a step-by-step guide for migrating projects with the Jira Cloud Migration Assistant.

If you have questions throughout the process you’ll be able to ask them in a private Atlassian Community group specifically for this early access program.

You will also be able to contact support at any time through your Jira support ticket.


Get involved

Sign up to the early access program, or follow the progress of this work.


Antonio Ferruz Community Leader Sep 14, 2019

Thanks for the info!

Like Jason Wong likes this

Hello @Jason Wong

At the Atlassian Open in Vienna last week, the cloud migration assistant was already shown with the "project only" migration capability if I am not mistaken. I signed up for the beta as indicated and have a client that pretty urgently needs to migrate a single project to the cloud. Is there any chance to get access to the beta already?

Cheers & thx :-)

Like Jason Wong likes this
Jason Wong Atlassian Team Oct 09, 2019

Hi @Andreas Krupp thanks for signing up for the Early Access Program.

I got your request and setup a support ticket for you which should have sent you a notification. Let me know if you didn't get that in your inbox (it went out on Sept 20th).

The latest guidance I can give on timeframes is as per my update over here on JRACLOUD-31806.

We've very keen to move the Early Access Program through to the next phase where we are able to give Partners a copy of the app and give it a try. Will be back with an update on where we are at in about 2-3 weeks time.

Hi @Jason Wong ,


Does this apply to Data Centre as well?  We are a Jira Data Centre customer.




Like Jason Wong likes this
Jason Wong Atlassian Team Oct 17, 2019

Hi @Leng Be ,

While the early access versions may work, we have not yet certified DC compatibility. For that reason I would not recommend using the early access version on DC.

Once the Jira Cloud Migration Assistant app is out of the early access program, DC compatibility will be put on the roadmap.

Hi @Jason Wong ,

We would be highly interested in migrating also our JIRA Software Projects to the cloud. Is this something what will come eventually? 



Like Jason Wong likes this
Jason Wong Atlassian Team Oct 17, 2019

Hi @Felix Bauer ,

Support for the migration of data such as sprints, versions, issue rank etc is already in development and so I do expect to be able to announce Jira Software project data migration support soon.

I will get back to you as soon as I can give guidance on when these features will be made available. 

Will old project keys be reserved in the Jira Cloud environment?

Jason Wong Atlassian Team Nov 06, 2019

Hi @Alex van Vucht -GLiNTECH-

Yes, we've built the Jira Migration Assistant to never overwrite data in Cloud. If there is a projects with the same key in Server and Cloud, we will not be able to migrate the Server project into Cloud until you change the project key on either side. 

Given most people are migrating to Cloud, the Cloud tends to be more often the source of truth, and so I expect most people to keep their project key in Cloud, but rename their Server side project.

If you want to merge the issues into the same project, I think there will be a little bit of a workaround:

1. Rename the project in Server.

2. Migrate the project to Cloud.

3. Do a bulk move of the issues into the desired project. In this case the issues from Server will undergo a change in project key number.

Thanks for the detailed response. Then the implication is that if a Server project is renamed, then the old key will not be reserved when the Server project is migrated to cloud.

I am currently investigating a case where a server to cloud migration also involves migrating Bitbucket Server repositories integrated with Jira Server to Bitbucket Cloud. In cases where I must change a project key, I will have to edit branch names, commits and pull requests to maintain references when the projects and repositories are migrated to Cloud.

By and large, Bitbucket Server does not make this available via REST. The Bitbucket Git API could do it, so I could do it in Scriptrunner for Bitbucket, or I could script out git client commands to make the changes.

Thanks for flagging that @Alex van Vucht -GLiNTECH- . Let me know how you go and if you need any further assistance with getting the integration working prior and after migration.

I will put this through to our integrations team to consider such situations when issue key changes break integrations with source code management tools.

Jason Wong Atlassian Team Sunday

Hi @Alex van Vucht -GLiNTECH-

Thanks again for raising this. We are investigating improvements to the migration of apps (formerly called add-ons), in which we'll investigate a longer term solution. 

There is an alternative approach. Y

  1. Rename the project key in Cloud that is in conflict. Renaming a project key in Cloud will not break the associations with your dev tool artefacts.
  2. With the Cloud project renamed, you no longer have a project key clash and so you could try migrating the project in server over to cloud without having to rename the project key.
  3. When you setup the integration in Cloud, it can then use the same project key it had in Server and reindex the associations.

Best to test, but this may be a way to make avoid scripting or modifying git history.

Jason Wong Atlassian Team Thursday

Update Nov 8th 2019 - Jira Cloud Migration Assistant Early Access Program for Partners is starting
This Monday Nov 11th, we will start providing the Early Access Program app to a few Partners who have have signed up and responded on their MOVE ticket expressing interest in participating. We will continue distributing the app on a rolling basis over the next weeks, so please stay tuned on your MOVE ticket where we will share the jar and corresponding documentation.
We are actively developing the app, and adding more capabilities. Over and above the original spec I posted above on this page, the app now also migrates the following data:

  • Epics (including colour, Epic Link, Epic Name and Epic Status) 
  • Issue rank
  • Flagged issues
  • Estimated & remaining time
  • Story points

Looking forward to expanding the program and getting the app into your hands for an early preview as soon as we can.
Jason Wong
Product Manager, Cloud Migrations

That's great progress! The only remaining items that as far as I can tell are still offered in a CSV import over this importer is:

  • Versions
  • Components
  • Sprints (although that requires specific IDs in the CSV importer)
  • Environment field

You mention that "Issue links" can be imported, but Jira Software "linked issues" cannot be imported. Can you please advise on the difference?

Finally, can you please advise if the Parent Link field used by Portfolio for Jira can be imported?

Like Jason Wong likes this
Jason Wong Atlassian Team Sunday

@Alex van Vucht -GLiNTECH-

Thanks for the feedback. I'm pleased to let you know that Versions, Components and Sprints are currently in-progress so it shouldn't be too long til we have support.

The linked issues in the notes on this page will be rewritten with the new docs - what we were referring to before were things like Epic links, which are now covered in the Early Access Program app as per my update above.

We do currently support issue linking with the following notes:

  • Links are only migrated if the linked issues (& their parent projects) have all been migrated to Cloud.
  • Links to issues that remain in server will not be linked from Cloud back to Server. However, if you later on decide to migrate the projects that remain in Server to Cloud, the Jira Cloud Migration Assistant will automatically restore the links between the projects and issues that have all been migrated to Cloud.

Unfortunately Portfolio for Jira isn't currently on our roadmap but we might be able to consider adding Parent Link field support as a stepping stone.

The Parent Link field can be updated programmatically in Cloud through the Edit Issue REST endpoint so it is not a big deal that Porfolio isn't on the roadmap. It would face the same challenge as supporting Epic Links and Linked Issues in that it requires the issues to be created first.

It would be hard enough to stage  the import with Epics, then standard issues, then sub-tasks, then issue links, so I do not envy the challenge the Cloud Migration team faces in introducing support for Portfolio's flexible issue hierarchy. I appreciate the openness with where you're at the with the migration; it makes me confident that the tool will work fine for our clients .

@Jason Wong I have signed to EAP cloud to cloud migration and eagerly looking forward to close the migration task. Please let me know the tentative date when we can try this much awaited feature.


Log in or Sign up to comment