Jira Cloud Migration Assistant
- Andrea Pedrollo
Since v7.1.0 (compatible with Jira 9) and 8.1.0 (compatible with Jira 10) Multi-Level Cascading Select has been integrated on Jira Cloud Migration Assistant.
Before we start
Error [JCMA 104] JCMA default values migration limitations
Before you begin the migration process, it is important to understand the limitations of Jira Cloud Migration Assistant (JCMA) regarding default values of third-party custom fields.
Due to Atlassian’s limitations, you are required to set your MLCS default value to none to complete the migration.
If you keep your default value set, the error [JCMA 104] will be thrown during the pre-migration check:
2025-02-17 10:53:29.043877587 ERROR PROJ project-export Custom field type: com.sourcesense.jira.plugin.cascadingselect:multi-level-cascading-select for Custom Field 'AAA MLCS' is not supported. [JCMA 104].
For more information on this, visit the related Jira issue: MIG-2180.
Migration process
In this section, we will go through the entire process of migrating data from an On-Premises Jira instance to your new Jira Cloud instance through the Jira Cloud Migration Assistant.
To open the Jira Cloud Migration Assistant, from your Data Center instance go to Administration → System → Migrate to Cloud. This is a driven process that will make your migration much easier.
Migration assessment
Before starting your migration, your organization is required to make a number of assessments to make your projects, apps, user accounts and email domains ready for migration.
Begin app assessment
This process will evaluate your applications to confirm the availability of all required apps for Cloud instances. This is essential for a successful migration.
In the Migration Assistant Home, in the ASSESS area, you can initiate the app's assessment by clicking “Begin assessing”.
Connect to Cloud
Early in the migration process, you will be asked to provide your destination Cloud site. This step is crucial as it connects the old Data Center / Server instance with the new one.
Prepare your apps
Once you have provided the destination site and decided on the apps you want to migrate, it’s time to make them ready for migration, installing the Cloud counterpart. Go on “Prepare your apps” and read and agree on the terms and conditions of each app. This will ensure App vendors have access to your server when migrating your app data.
Prepare your data
The result of this check will reduce the time of the migration.
Prepare your users
This will assess if all user emails are unique and valid, so they can be migrated to the Cloud instance.
Review your email domains
Review and trust your email domains to get them ready for migration, improving the security of the destination instance.
Begin your migration
You are now ready to begin the migration. Click on Create a migration and follow the steps:
Connect to your cloud site
After naming your migration, you can choose the stage, whether to perform a test migration or a production migration, as well as the destination cloud site.
Choose your migration options
You can choose what projects, roadmap plans, dashboards and users are going to be migrated. Once you have decided, click on “run pre-migration checks” to check if the migration is ready to run.
Run the migration.
This step will run the migration. The time needed to complete the process is related to the quantity of projects, issues and other data to be migrated. Based on Atlassian experience with previous enterprise migrations, they have determined that the average throughput of Jira Cloud Migration Assistant is 3,700,000 issues / 24 hours.