Versions Compared

Version Old Version 13 New Version 14
Changes made by

Magdalena Żaczek

Magdalena Żaczek

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Contents:

Table of Contents
minLevel2
maxLevel3
outlinefalse
stylenone
typelist
printablefalse

...

  • What If Scenario is not migrated.

  • JQL can be incomplete and may require manual changes. JQL is used in Scope definition → Additional Filtering and Quick Filters.

How to prepare for migration

The steps below are necessary to migrate the plugins to Jira Cloud. Ensure you have all the plugins (BigPicture, BigTemplate) installed on your Jira Cloud before you begin.

Jira Data Center

When you migrate from Jira Data Center to Jira Cloud, you will be asked to reinstall BigPicture to prepare a JCMA dump.

Expand
titleSee the steps
Info

Creating a JCMA snapshot will restart the App and may take a significant amount of time and resources, so the process is recommended during non-business hours. Do not interrupt the process or disable the App until the JCMA snapshot is complete.

  1. Prepare a JCMA snapshot in BigPicture on Jira On-premise:

    1. Navigate to BigPicture App Configuration > Advanced > Database dumps > New dump > JCMA dump.

      Screenshot of the App configuration page.Image RemovedScreenshot of the App configuration page.Image Added

    2. Enter a unique Migration name, as you will later need to identify this snapshot in JCMA and complete the Description field.
      The provided Migration name can be edited later.

      Screenshot of creating a new JCMA snapshot.Image RemovedScreenshot of creating a new JCMA snapshot.Image Added

  2. For BigPicture on Jira Cloud:

    1. Navigate to Apps > BigPicture App Configuration > Advanced > Technical info > Others > Data migration.

    2. Enable the Allow JCMA migration option.

      Screenshot of enabling the Allow JCMA migration toggle switch. Image RemovedScreenshot of enabling the Allow JCMA migration toggle switch. Image Added

  3. On Jira On-premise:

    1. Navigate to Jira Administration > System > Import and Export > Migrate to cloud > Assess your apps.

    2. Assign the Needed in cloud status for each App.

    3. Click Done.

      Screenshot of assessing apps before the migration.Image RemovedScreenshot of assessing apps before the migration.Image Added

Migration process

Expand
titleSee the steps

  1. Initiate a migration process in JCMA:

    1. Navigate to Jira Administration > System > Import and Export > Migrate to cloud.

    2. Click the Create a migration button.

      Screenshot of initiating the migration process.Image RemovedScreenshot of initiating the migration process.Image Added

  2. Get familiar with information about the migration process.

    Screenshot of migration process explanation.Image RemovedScreenshot of migration process explanation.Image Added

  3. Provide the migration name (the one you used for creating the JCMA snapshot in BigPicture).

  4. Choose your destination Jira Cloud.

    Screenshot of providing the migration name.Image RemovedScreenshot of providing the migration name.Image Added

  5. Click on the preferred migration method:

    1. Choose what to migrate; or

    2. Migrate all data at once.

      Screenshot of migration options.Image RemovedScreenshot of migration options.Image Added

  6. If you have selected Choose what to migrate in the previous step:

    1. Define your migration options, such as Projects, User and groups, and Apps.

    2. When ready, click the Check for errors button.

      Screenshot of checking errors before the migration.Image RemovedScreenshot of checking errors before the migration.Image Added

    3. Select All to migrate all the apps with an automated path that are marked as Needed in cloud in your app assessment.
      If you select None, no apps will be migrated.

      Screenshot of selecting apps to be migrated.Image RemovedScreenshot of selecting apps to be migrated.Image Added

  7. Proceed by clicking Review migration.

    Screenshot of checking for errors before the migration.Image RemovedScreenshot of checking for errors before the migration.Image Added

  8. You can run your migration now or save it and come back later. You will not be able to add or remove projects after you have saved so if you would like to make any changes, perform them now.

    Screenshot of reviewing the migration.Image RemovedScreenshot of reviewing the migration.Image Added

  9. After running the migration, you can track its progress from the Migration dashboard.

    (info) Info: During migration, your BigPicture on Jira Cloud will restart to reflect the state of the migrated BigPicture from Jira On-premise.

  10. Once the migration is complete, the status will be updated accordingly.
    (BigPicture Jira Cloud) You will see the Migration completed successfully message once you enter Apps > BigPicture App Configuration > Advanced > Technical info.
    The message will disappear after the next BigPicture update.

    Screenshot of checking the migration completion on the BigPicture App configuration page.Image RemovedScreenshot of checking the migration completion on the BigPicture App configuration page.Image Added

    (Jira On-premise) The Progress column in the Migration dashboard (Jira Administration > System > Import and Export > Migrate to cloud)informs about the migration status.
    You can also expand the Actions menu and click View details. 

    Screenshot of the Migrations dashboard in Jira.Image Removedjira-administration-system-migration-dashboard.pngaScreenshot of the Migrations dashboard in Jira.Image Added

    You will find detailed information on the migration.

    Screenshot of the Migrations dashboard details in Jira.Image RemovedScreenshot of the Migrations dashboard details in Jira.Image Added

Additional instructions for the Migrate all data at once option

...

Expand
titleSee the screenshot
Screenshot of additional instructions for the migration.Image Removed

Screenshot of additional instructions for the migration.Image Added

If you see the following screen, it indicates the lack of sufficient permissions for add-ons on Jira Cloud. In this case, you must follow the procedures described on the Insufficient JIRA Permissions in BigPicture page.

Expand
titleSee the screenshot
Screenshot of a message that access to BigPicture is needed.Image Removed

Screenshot of a message that access to BigPicture is needed.Image Added

Once you define sufficient permissions, return to BigPicture/BigGantt on Jira Cloud:

Expand
titleSee the steps

  1. Go to App Configuration > Advanced > Technical info.

  2. Under the Others > Data migration section, enable the Allow JCMA migration toggle switch. 

  3. Under the Pending data migration section, click the Trigger pending migration button.

    Screenshot of the Trigger pending migration button on the BigPicture App configuration page.Image RemovedScreenshot of the Trigger pending migration button on the BigPicture App configuration page.Image Added

  4. After refreshing the page, you will see a message that the migration is in progress.

    Screenshot of the message that migration is in progress.Image RemovedScreenshot of the message that migration is in progress.Image Added

  5. Now, you can return to the Migration dashboard on Jira On-premise and track the progress.

    Screenshot of the Migrations dashboard in Jira.Image RemovedScreenshot of the Migrations dashboard in Jira.Image Added

How to repeat migration

Warning

It is not recommended to reset Jira Cloud to solve migration problems. However, if there is no other way and you decide to reset Jira Cloud, you have to uninstall BigPicture first. Once BigPicture is uninstalled, you can reset Jira Cloud.

In case of any mistakes during the migration process in JCMA (for example, forgetting to provide the correct Migration name of your JCMA snapshot), you can run the migration process again.

Expand
titleSee the steps

  1. Prepare a JCMA snapshot in BigPicture on Jira On-premise.
    You can either: 

    1. Edit the Migration name and use the same JCMA snapshot (if you entered the wrong Migration name for your JCMA snapshot).
      Go to BigPicture App Configuration > Advanced > Database dumps and edit the JCMA snapshot you created before.

      Screenshot of editing a JCMA snapshot on the BigPicture App configuration page.Image RemovedScreenshot of editing a JCMA snapshot on the BigPicture App configuration page.Image Added

      or

    2. Create a new JCMA snapshot as described in the How to prepare for migration section above.

  2. Enable the Allow JCMA migration option in Apps > BigPicture App Configuration > Advanced > Technical info > Others > Data migration section on Jira Cloud.
    This option needs to be enabled each time before migration.

  3. Go to the Jira Administration > System > Import and Export > Migrate to cloud > Assess your apps section.

  4. Assign the Needed in cloud status for each App.

  5. Click Done.

    Screenshot of assessing apps before the migration.Image RemovedScreenshot of assessing apps before the migration.Image Added

  6. Initiate the migration process as described in the Migration process section.

...

Once the migration process is finished, it is recommended to check the following:

In Jira:

  • Review imported groups

Expand
titleSee the steps

You will see a message that imported groups need your review. Click on the banner to start reviewing or navigate to Directory > Groups.

Screenshot of reviewing imported users and groups in Jira.Image RemovedScreenshot of reviewing imported users and groups in Jira.Image Added

You can select a group to review their pending product roles.

Screenshot of reviewing imported groups in Jira.Image RemovedScreenshot of reviewing imported groups in Jira.Image Added

You can approve or deny a group.

Screenshot of reviewing imported groups in Jira.Image RemovedScreenshot of reviewing imported groups in Jira.Image Added

When ready, the status Reviewed will appear next to a group. 

Screenshot of confirming the imported groups in Jira.Image RemovedScreenshot of confirming the imported groups in Jira.Image Added

  • Verify permissions

  • Check migrated custom fields

Expand
titleSee the steps

Migrated custom fields can be recognized by the (migrated) additional note.
To find out more about duplicates, refer to the Jira Cloud Migration Assistant duplicates and tracking entities article.

Screenshot of checking migrated custom fields in Jira.Image RemovedScreenshot of checking migrated custom fields in Jira.Image Added
Info

Duplicated fields after migration in Jira Cloud
During migration with JCMA to Jira Cloud you can see duplicated custom fields, Migrated and Locked ones. Custom fields marked as Migrated are used for default field mapping in Jira Cloud.

In BigPicture:

  • Field mapping in App Configuration > General > Fields

  • Scope definition in Boxes

  • Content of Boxes such as tasks, projects, etc.

  • Editing and assigning tasks (it can be necessary to correct permissions)

  • Individual resources 

  • Permissions assigned in App Administration > Security

BigTemplate migration

Note

The migration using JCMA is available for BigTemplate version 8.17.1 and later.

You can migrate BigTemplate alone or together with BigPicture using JCMA. As a result, the BigTemplate database and all files with templates are migrated to your Jira Cloud.

How to prepare BigTemplate for migration

Make sure you have BigTemplate installed on your Jira Cloud before you begin. 

  1. A JCMA snapshot for BigTemplate on Jira On-premise is created automatically.

  2. On Jira On-premise:

    1. Go to the Jira Administration > System > Import and Export > Migrate to cloud > Assess your apps section.

    2. Assign the Needed in cloud status for BigTemplate.

    3. Click Done.

BigTemplate migration process

...