Migration step by step
You need to have Jira Administrator rights in order to perform the migration.
1. Install - Jira Cloud Migration Assistant
Make sure you have the latest version of the Jira Cloud Migration Assistant installed on your Jira server. If not, update it.
2. Go to “Migrate to cloud” page
Navigate to Jira Administration (1) → System (2)
then on the left side in section IMPORT AND EXPORT, please go to Migrate to cloud (1)
Then you should see Migration Assistant home screen similar to this one:
For a successful migration, you need to prepare your instance to migration. You can also choose if you want to create your migration plan - test and migrate to a cloud-hosted site (2.1) or create a proper migration (3).
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 a server project on the cloud site.
2.1 Migration plan
a) asses your apps - assess and select the apps you need to migrate (1). When you ready click button Done and connect to your cloud site (2).
b) prepare your apps - at first choose your cloud side (3). After clicking Continue (4) you should be redirecting to next step.
Fill in base URL of your instance (5) → choose a cloud site (6) and tick the box to complete this step (7). After confirming the information you have entered ( 8 ), you will return to the Connect stage. To continue process, click Continue (9).
Next step is installing app on cloud site. If everything is as you expected, select the Continue button (9) .
Read the privacy policy (10) and proceed with the application migration by giving your consent (11).
If you do not agree to the terms, you can cancel the migration.
Return to main screen by clicking Done button.
c) assess and prepare users (12)
You will be redirected to a page where you can verify the email addresses of the migrated users (13).
Depending on the results, you will be able to move on to the next stage or correct errors. To do this, click on Done (14).
d) review all emails domains - this is where you decide whether all domains specified on your server instance are reliable and can be migrated with all the data (15). When verifying domains, you can choose between 3 actions (16). Classifying the data will allow you to proceed to the next step (17).
On this screen you can see all your email domains with the number of users in each domain. If you trust the email domains, you need to mark all your domains as trusted.
e) migrate your users in advance in advance
At first connect to cloud: name your migration (18). Choose between production stage or testing stage (19) - you can select any option. Specifying this will help you identify migration plans on your dashboard. To go on next step (21) you need also selected once again your destination cloud site (20).
An equally important action is to choose how to migrate users and groups (22). Only then can you start the pre-migration checks (23).
After creating a migration plan, the Jira Cloud Migration Assistant runs a set of pre-migration checks to make sure your data can be migrated to cloud.
3. Create new migration
Please proceed to Create new migration (1)
then click on Connect to cloud (2)
next you need to define migration name (3), it will help you later to identify your migration in migration panel. Then you need to choose to which Jira Cloud you want to migrate (4) (if you don’t see your Jira cloud in dropdown then please proceed to Chose cloud site (5) and add it). Once you set your name and choose your Jira cloud then go next to Choose migration options (6)
Here you can define migration options (7) of your choice to make migration fits your needs. You have two possibilities to do it: Choose what to migrate or Migrate all date at once. The more recommended option is to Choose what to migrate (8), 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 (9):
You need to go step by step to get to the next stage.
First decide what you want to do with Advanced Roadmaps, then Select Projects (10). You can decide which projects to migrate, which issue to migrate and what to do with the attachments. Simply mark your choices (11) and click Add to migration (12) button. Next you will need to select users and groups (13) to be migrated and continue by clicking Add to Migration (14). The following step will be the selection of the application (15) and apply changes (16).
Once you set everything up proceed to Pre-migration checks (17) section. Here you can see if there is any obstacle to migrate, once you will get error/warning you will get notified about that fact and possible solution (18). When you fix all your errors and/or warnings (warnings don’t need to be fixed to migrate but keep in mind possible unwanted effects of it), you can Continue (19) and proceed to Review migration (20) section.
4. Review migration
Next double check if everything you selected before is on that summary, then you are ready to Run (1) migration
5. Migration run
You will be moved to Migrations dashboard where you can track your migration status.
then if it’s finish it will change 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 - then you will see updated status). You can also go directly to the instance by Go to cloud site (2) option.
Selecting View details will take you to a page with a summary and details of your migration.
The Go to cloud site action will take you to your cloud instance.
Feel free to tell us what topic should be covered: thescheduler@psc-software.atlassian.net