Dataplane Reports is not available for Cloud, but now, you can migrate your Dataplane Reports Server/Data Center to Cloud using Dashboard Hub Pro.

Due to Dashboard Hub Pro’s high compatibility with Dataplane, we’re adding Dataplane’s best features to Dashboard Hub Pro to give you a Dataplane Reports-compatible Cloud solution. For that, we’ve enabled a seamless path to migrate your Dataplane Reports data to Dashboard Hub for Jira Cloud automatically using JCMA.

If you plan to migrate Dataplane Server/DC to Cloud, you must prepare, know the required steps, and choose the strategy that best fits your environment/business requirements

1. Assess your app, data, and users

2. Install or access the Migration Assistant

3. Create or have a Cloud site/instance.

4. Locate your base URL (source) - required when you connect to your Cloud instance.

How to Locate your base URL (source)

1. In your server instance, go to System.

2. Select General Configuration.

The Settings page shows the Base URL.

Required permissions for viewing report data:

• Appropriate Jira project permissions

• Developer role assignment in relevant projects

• Active membership in the jira-users group

Important: Direct Jira issue access doesn't automatically grant access through Dashboard Hub reports. You may need to configure project role memberships. Starting your migration.

The Migration Assistant provides automation when migrating the Dataplane Reports Server/DC instance to the Cloud. To learn more about planning and executing your migration, refer to:

Server to Cloud migration guide | Atlassian

The migration consists of two main phases: Assessing your app, data, and users, and the actual migration (Create migration).

The JCMA Migration workflow table shows the steps that you do in your instance and the ones you have to do in your Cloud instance.

Where	Activity

Where	Activity
ON JIRA DC/SERVER	Install and/or verify the JCMA app is installed and updated to the latest version.
ON JIRA CLOUD	Identify or create your target Jira Cloud instance.
ON JIRA CLOUD	Install the Dashboard Hub for the Jira Cloud app.
ON JIRA DC/SERVER	Go to the JCMA “Migration Assistant home” page by navigating to Jira Administration > System > Migrate to cloud.
ON JIRA DC/SERVER	On the JCMA “Migration Assistant home” page, prepare for migrating Jira data by selecting the Dataplane Reports app for migration, assessing and preparing your users, and reviewing your users and email domains.
ON JIRA DC/SERVER	Create a new JCMA Migration plan—using “Choose what to migrate”—for migrating your Jira users, groups, projects, boards, and filters (without Dataplane Reports data), and run this Migration plan to migrate the bulk of Jira data to Cloud.
ON JIRA DC/SERVER	Create a second JCMA Migration plan—using “Choose what to migrate”—for migrating Dataplane Reports app data. Run the pre-migration checks, select “View app vendor checks”, and review Dataplane Reports' pre-migration analysis of the availability of compatible reports in Dashboard Hub for Jira Cloud and any flagged issues such as invalid references to Jira projects, fields, filters, groups or users.
ON JIRA DC/SERVER and JIRA CLOUD	Correct any issues with the initial Jira data migration that were flagged by the Dataplane Reports' pre-migration checks.
ON JIRA DC/SERVER	Run the Dataplane Reports Migration plan to migrate app data to Cloud.
ON JIRA CLOUD	Navigate to Jira Settings > Apps > Post migration report (Dashboard Hub). For the migration just performed, click on “View Details” to review the post-migration report. The report also shows the total number of reports that were available for migration in the server instance Open
ON JIRA CLOUD	Navigate to Apps > Dashboard Hub to review the new Dashboard Hub dashboards and gadgets created from your Dataplane reports. Open
ON JIRA DC/SERVER and JIRA CLOUD	Correct any issues with the initial Dataplane Reports data migration
ON JIRA DC/SERVER	Re-run the Dataplane Reports Migration plan as many times as needed until you are satisfied with the migration

To start migrating your data, log in to the Dataplane server instance you want to migrate your users and projects from, this is also called base URL. This is the source from where you move your data.

When you connect to the Cloud, provide the following information:

• Migration name

• Migration stage, for example, test or production

• Destination - your cloud site

• Base URL from where you want to migrate, that is, your Dataplane Reports server instance.

Open

A cloud migration strategy is the high-level plan an organization adopts to move an existing server DC installation and co-located applications and their associated data into the cloud.

Open

Specific to the migration of Dataplane Reports to Cloud, you can choose from two migration options:

• Migrate all your data at once

When you choose to migrate all at once, you need to start with an empty Cloud site.
You can also exclude or include the attachments by selecting the Exclude all attachments option.

• You choose your migration strategy in Dataplane Server/DC.

This option allows you to migrate selected data, projects, and users into an existing Cloud site.
You can repeat this option as many times as you require until everything is migrated to the Cloud site.

If you need to re-run part or all of the migration:

• Do not delete Cloud-based native dashboards prior to migration

• Dashboard relationships between DC and Cloud systems remain linked

• Removing Cloud dashboards triggers migration failures

Solution: To migrate native dashboards successfully, modify the dashboard names in your Dataplane Server/DC environment before initiating another migration.

After you choose your migration strategy, the Pre-migration page displays all the checks that are run.

The Pre-migration checks are standard Atlassian controls to verify the status and readiness of your:

• System

• User and Groups

• Projects

• Cross-projects

• Data preparation

• Apps

In addition to the standard Atlassian checks, two additional app vendor check is implemented for Dataplane.

The app vendor checks are designed to reduce the possibility of app migration failure.
Dataplane Reports performs the following two app vendor check:

• Invalid reference report
  This pre-migration check will detect any inconsistencies in your Dataplane Reports configurations. That actually might already be a problem in Dataplane Reports on your Jira Server / Data Center instance. Dataplane Reports might not be able to run those reports correctly.
  For best results after your cloud migration, we recommend you fix these problems already in Dataplane Reports on your Jira Server / Data Center instance.
  You could move on with your cloud migration without fixing anything. But the detected inconsistencies will be the same problem in Dashboard Hub Pro Cloud.

Open

• Permission and datasource verification
  This validation confirms that user accounts, groups, and roles in your Dataplane Reports configuration will migrate correctly. Address these alerts before migrating:

  • User accounts not found in the Cloud environment

  • Differences in group memberships

  • Incomplete project role configurations

Once the pre-migration checks are complete, you can review the items included in the migration, their status, logs, and reports.

Open

Open

The Review page

You can run your migration now or save it and come back later.

When you are ready, click on Run to start migrating to your Cloud instance.

When the migration is complete a link is created.

Click the link to view the post-migration report. In the post-migration report, messages are displayed showing items that were skipped in the migration and why.

The types of messages that are provided are:

• Skipped messages

• Warning message

• Error message

Error messages let you know of major problems encountered during the migration.

Access and permission notifications

Review these items carefully:

• Users with report visibility but insufficient data access permissions

• Missing project role assignments needed for viewing data

• Restrictions on datasource access

Verification tasks after migration:

When your migration finishes:

1. Check the post-migration report for access-related notifications

2. Confirm report viewers have necessary project role memberships

3. Test report functionality using non-administrator accounts that require access

4. If users see empty reports despite having project access, verify their Developer role assignment

Take immediate action on these items to guarantee proper user access across your organization.