Automated DC to Cloud migration with JCMA
Starting from Agile Reports and Gadgets Data Center version 8.6.0, app data can be migrated from DC to Cloud automatically using the Jira Cloud Migration Assistant (JCMA). This allows you to transfer your existing chart configurations to Cloud as part of the standard Jira migration flow.
Step 1. Prepare your environment
Before starting the migration, verify that both instances are properly set up.
On Jira Data Center (source):
Install Agile Reports and Gadgets version 8.6.0 or later (latest version recommended)
Install the latest Jira Cloud Migration Assistant (JCMA)
On Jira Cloud (target):
Install and activate the Agile Reports and Gadgets app
Step 2. Plan your migration runs in advance
JCMA allows you to run multiple migration jobs between the same Data Center and Cloud instances, which can be useful if you migrate projects in stages.
However, for Agile Reports and Gadgets, we recommend completing both Jira data and app data migration in a single run whenever possible.
If your migration is split into multiple runs:
Enable Agile Reports and Gadgets migration only once
Do this either:
in the final migration run, or
in a separate app-only migration after all Jira data is migrated
Why this matters
Agile Reports and Gadgets configurations rely on Jira entities such as dashboards, filters, and custom fields. If these are not yet available in Cloud, chart configurations may be incomplete or broken after migration.
Step 3. Select the app for migration
On your Data Center instance, go to Jira Administration → System → Migrate to Cloud. Open the Access your apps section:
Search for Agile Reports and Gadgets and set its status to Needed in cloud:
Step 3. Verify permissions in Cloud
To allow the app to recreate configurations:
Grant Share dashboards and filters permission on the Cloud instance
Ensure the
atlassian-addons-admingroup has this permission
Step 4. Include filters and dashboards in migration
Agile Reports and Gadgets rely on Jira dashboards and saved filters. To preserve these relationships, make sure to include them in your JCMA configuration.
On the Choose what to migrate screen, select:
All dashboards
All filters and cross-project boards
If filters or dashboards are excluded, related charts will still be migrated, but missing dependencies will result in incomplete configurations.
Step 5. Enable app data migration
In the Select apps step of JCMA, choose All apps marked as “Needed in cloud” with a migration path. If other apps are included, check their documentation for additional requirements.
Step 6. Run the migration
Start the migration from JCMA:
The process runs in two stages:
Jira data is migrated
Agile Reports and Gadgets data is transferred and applied
After completion, check the migration details screen. A successful migration shows:
Status: COMPLETE
Progress: 100%
Partial migrations and missing dependencies
If app data is migrated before all Jira data is available in Cloud, some chart configurations may not be restored correctly. This happens because Agile Reports and Gadgets rely on Jira objects such as:
dashboards
saved filters
projects
custom fields
If these dependencies are not yet migrated, the app cannot fully configure the charts.
What happens in this case
Gadgets are still migrated and added to dashboards, but their configuration may be incomplete. As a result, charts may appear empty or not configured:
If you run the migration again after the missing Jira data becomes available, the app will retry configuring previously migrated gadgets. Charts that were incomplete in the first run can be correctly restored in subsequent runs.
How to avoid this issue
To ensure charts are fully migrated and configured:
Include all relevant Jira filters and dashboards in the migration
Make sure all referenced Jira data (projects, fields, filters) is migrated before or together with app data