...
| Tip |
|---|
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
| Note |
|---|
Error [JCMA 104] JCMA default values migration limitationsBefore 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 If you keep your default value set, the error [JCMA 104] will be thrown during the pre-migration check:
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
Evaluating This process will evaluate your applications to confirm the availability of all required apps for Cloud instances. This is essential for a successful migration process. This process will check this for you.
In the Migration Assistant Home, in the ASSESS area, you can initiate the app's assessment by clicking “Begin assessing”.
...