Migration using Jira Cloud Migration Assistant (JCMA)
The migration using JCMA is available for:
BigPicture/BigGantt version 8.11 and later
BigTemplate version 8.17.1 and later
If you don't know how to check the current version, refer to the Checking the App version article.
With the Atlassian JCMA tool, you can migrate selected projects or divide the migration process into a few stages. It is possible to:
Migrate Jira On-premise and the BigPicture / BigTemplate / BigGantt plugins to Jira Cloud.
Migrate only Jira On-premise without the BigPicture/BigGantt plugin to Jira Cloud.
After migration, the App data from Jira On-premise will overwrite data on Jira Cloud.
Make sure you have JCMA installed on your Jira. If you do not have JCMA installed:
Navigate to Jira Administration.
Go to ATLASSIAN MARKETPLACE in the left sidebar.
Select Find new Apps.
Search ‘Jira Cloud Migration Assistant’ and install it.
To find out more about JCMA, read the Use Jira Cloud Migration Assistant to migrate (legacy) article.
In case of any doubts, contact our Support.
What is not migrated
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.
Migration process
Additional instructions for the Migrate all data at once option
The following steps apply only to the Migrate all data at once option.
If BigPicture/BigGantt migration got stuck at 0% and there is no progress in the last 15 minutes, go to BigPicture/BigGantt on the target Jira Cloud instance.
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.
Once you define sufficient permissions, return to BigPicture/BigGantt on Jira Cloud:
How to repeat migration
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.
After migration
Once the migration process is finished, it is recommended to check the following:
In Jira:
Review imported groups
Verify permissions
Check migrated custom fields
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
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.
A JCMA snapshot for BigTemplate on Jira On-premise is created automatically.
On Jira On-premise:
Go to the Jira Administration > System > Import and Export > Migrate to cloud > Assess your apps section.
Assign the Needed in cloud status for BigTemplate.
Click Done.
BigTemplate migration process
The migration process for BigTemplate is almost identical to BigPicture (two preparation steps are not needed when migrating only BigTemplate):