Migration step by step
Jira Administrator permissions are required to perform this migration.
1. Install Jira Cloud Migration Assistant
Ensure the latest version of the Jira Cloud Migration Assistant (JCMA) is installed on your Jira Data Center (DC) instance. If it is outdated, upgrade it before proceeding.
2. Open the “Migrate to cloud” page
Navigate to Jira Administration (1) → System (2).
In the left-hand navigation, under IMPORT AND EXPORT, select Migrate to cloud (1).
You should now see the Migration Assistant home screen, similar to the following:
To ensure a successful migration, first prepare your instance. From this screen, you can either create a migration plan (recommended) to test and prepare for migrating to a cloud-hosted site, or start a production migration.
A migration plan is a checklist of the steps you need to take to migrate properly. It is designed to prepare you and your data for migration and to identify potential sources of problems. This checklist will help you avoid making mistakes during a proper migration.
Note that it ends with user migration, without the application being migrated, as it is only a preparation for the final migration. After that, there will be no server project on the cloud site.
More information about migration plan you can find in Atlassian’s documentation:
https://support.atlassian.com/migration/resources/ .
3. Create new migration
Please proceed to Create new migration (1)
A message will then appear in which you select the button Review domains (2). You decide whether all domains specified on your server instance are reliable and can be migrated with all the data.
You will then see a screen with the steps to take to create the migration. Click the Connect to Cloud button (3).
Next, define the migration name (4). Use a descriptive name that will help you identify this migration later in the migration panel. Choose the stage: production or testing (5). This setting is for identification only and helps you distinguish migration plans on your dashboard. Then select the Jira Cloud site you want to migrate to (6). If your Jira Cloud site is not visible in the dropdown, click Choose cloud site (7) and add it. After you have set the migration name and selected your Jira Cloud site, proceed to Choose migration options (8).
If you need to Choose your destination cloud site (7) fill in base URL of your DC instance (A) → choose a cloud site (B) and tick the box to complete this step. To continue process, click Continue button further down the page.
Here you can define migration options of your choice to make the migration fit your needs. You have two possibilities to do it: Choose what to migrate or Select all data. The more recommended option is to Choose what to migrate (9), as this gives you more flexibility and control over the selection of data to migrate. If you select the recommended option, you will be taken to the section Choose your migration options (10):
You need to go step by step to get to the next stage, so first Select Projects. Simply mark your choices and click Add to migration button. Next you will need to Select users and groups to be migrated and continue by clicking again Add to Migration. The following step will be the Select apps (11) and Apply changes (12).
If you didn't select an app during the previous migration preparation, you will need to select the App Assessment (13).
Here you can take the appropriate action - select the application as Needed in Cloud (14) and click the Done (15) button.
If everything is as you expected, View the privacy policy (16) and proceed with the application migration by giving your Consent (17).
After completing the setup, open the Pre-migration checks (10) section. Here you can see if there is any obstacle to the migration, once you get an error or a warning you will get notified about it and proposed a possible solution (18). When you fix all your errors and/or warnings, you can Continue (19) and proceed to the Review migration section (20).
Warnings don’t need to be fixed to migrate but keep in mind there might be some unwanted effects of not resolving them before proceeding with the migration
Depending on what you have selected, the following messages may appear and you can choose:
a) Continue without resolving warnings or Resolve warnings
b) Continue or View all app vendor checks
4. Review migration
Next double check if everything you selected before is on that summary, then you are ready to Run (1) migration
You have the option to perform the migration later, simply select the Save button instead of Run.
You can also use this option, if you want to fix the errors first and return to the migration later.
5. Migration run
You will be moved to Migrations dashboard where you can track your migration status.
Once the migration is finished it will change its status to complete (if loader spin all the time and it do not end then please refresh page or you can go to View details (1) in action menu). You can also go directly to the instance by Go to cloud site (2) option.
As a convenience, multiple migrations can be performed on a single Data Center instance, with the settings and defaults stored in the instance's memory after the first migration. They can be refreshed and changed at any time.
Selecting View details will take you to a page with a summary and details of your migration.
The Go to cloud site button will take you to your cloud instance.
Now your data has been migrated! You can go to Cloud instance.