Migration Steps

See below some details about migration to Data Center or Cloud. If you have additional questions or need assistance with the app migration, please contact StonikByte Support at support@stonikbyte.com.

Feature parity between Server, Data Center and Cloud

All gadgets and their functionalities available in Great Gadgets for Jira Server or Data Center are also available in the Cloud version.

Feature	Server	Data Center	Cloud

Feature	Server	Data Center	Cloud
Sprint Burdown Burnup Chart gadget
Release Burndown Burnup Chart gadget
Team Velocity gadget
Control Chart gadget
Cycle Time Trend gadget
Histogram Chart gadget
Time in Status gadget
Cumulative Flow Diagram (CFD) gadget
WIP Run Chart gadget
WIP Aging Chart gadget
Kanban Velocity / Throughput gadget
Pivot Table & Pivot Chart gadget
Issue Formula gadget
Advanced Issue Filter Formula gadget
Work Breakdown Structure (WBS) gadget
Team Wallboard gadget
Countdown gadget
Regional Clock gadget
Timesheets & Worklog Reports gadget	N/A	N/A	*
Data Residency	N/A	N/A
Ability to import the gadgets as macros in Confluence			N/A**

* Available with the Advanced Edition.

** Confluence Cloud does not support importing Marketplace app gadgets as macros. However, this functionality can be preserved by installing Great Gadgets for Confluence. See Using the gadgets in Confluence Cloud.

Migration from Server / Data Center to Cloud

The app has a Cloud version that offers the same functionality as the Server / Data Center version. It can be found on the Atlassian Marketplace. All gadgets and their functionalities available in Great Gadgets for Jira Server or Data Center are also available in the Cloud version.

If you migrate your Jira instance from Server / Data Center to Cloud, this will be like a new app installation. You will have to reconfigure the app gadgets from scratch.

To determine the gadgets usage in your Jira Server / Data Center instance, you can run this SQL query on the Jira database:

SELECT portletconfiguration.gadget_xml, portalpage.pagename, portalpage.id, portalpage.username
FROM portletconfiguration INNER JOIN portalpage
ON portletconfiguration.portalpage = portalpage.id
WHERE portletconfiguration.gadget_xml LIKE '%com.stonikbyte.great.gadgets%'

This returns a list with the gadget identifier (gadget_xml), the name (pagename) and the identifier (id) of the dashboard where the gadget is located, and the user who added the gadget to the dashboard (username).

Our recommended approach is as follows:

Migrate your Jira data first using the appropriate migration tools provided by Atlassian.
During this process, your Jira dashboards may be migrated; however, the app gadgets will not be included.
Install Great Gadgets in the new Jira Cloud instance.
If your new Jira Cloud instance uses IP allowlists, add the Great Gadgets IPs to the allowlist. See https://stonikbyte-production.atlassian.net/wiki/spaces/GG/pages/62291970/Technical+Notes#IP-Allowlisting.
Optionally, enable and configure https://stonikbyte-production.atlassian.net/wiki/spaces/GG/pages/1092911106.
Run the SQL script above on the old Jira Data Center database to identify which gadgets were used, in which dashboards, and who the dashboard owners are.
Send the list of dashboards to each respective owner (via e-mail) and ask them to review and reconfigure their dashboards by manually re-adding and configuring the gadgets in the new Jira instance, matching their previous setup in Jira Data Center.
This approach distributes the effort across multiple users and may also lead to cleanup, as some dashboards or gadgets may no longer be needed.

If you had the app gadgets imported as macros in Confluence Data Center, you will not be able to do the same on Cloud because Confluence Cloud does not support importing gadgets from Jira Cloud apps. You can preserve the functionality of the macros added to Confluence pages by installing Great Gadgets for Confluence Cloud (along with its dependency StonikByte Connector for Jira Cloud) and then manually re-configuring the macros from the Confluence pages. The app macros that rely on data from Jira cannot connect to the old Data Center instance, so make sure to migrate Jira first in order to preserve macro functionality in Confluence.

Migration from Server to Data Center

If you migrate your Jira instance from Server to Data Center by preserving the existing Jira data, there are no special steps to follow in order to migrate Great Gadgets app. After applying the new Data Center specific license key, the app will continue to work as before.

If you migrate to Data Center without preserving the existing Jira data, this will be like a new app installation. You will have to create new Jira dashboards and configure the app gadgets from scratch.

Migration from Cloud to Cloud

Migration of Jira and/or Confluence data from a Cloud instance to another Cloud instance is usually done by using data copying process recommended by Atlassian (see https://support.atlassian.com/organization-administration/docs/copy-product-data/).

Please consider the following when planning a Cloud to Cloud migration of a Jira and/or Confluence instance that has the Great Gadgets app installed.

Migration of app data during a Jira Cloud-to-Cloud migration

Great Gadgets for Jira Cloud mainly consists of gadgets that are added to Jira dashboards.

Currently, Atlassian’s migration tools support dashboard migration between Jira Cloud instances; however, gadgets provided by third-party apps are not migrated as part of this process. As a result, migrating Jira dashboards along with the app gadgets must be done manually.

To complete the migration:

Migrate your Jira Cloud data (projects, filters, boards, fields, statuses, etc.) to the new Jira Cloud instance using Atlassian’s tools. For more details, see: https://support.atlassian.com/organization-administration/docs/copy-product-data/
After the data migration is complete, install Great Gadgets for Jira Cloud in the new Jira Cloud instance.
If Data Residency was enabled in the old Jira Cloud instance, configure the same settings in the new instance. See: https://stonikbyte-production.atlassian.net/wiki/spaces/GG/pages/1092911106.
If you use IP allowlists in the new Jira Cloud instance, make sure to allow the IP addresses required by the app in the new instance. See https://stonikbyte-production.atlassian.net/wiki/spaces/GG/pages/62291970/Technical+Notes#IP-Allowlisting.
Since Atlassian tool migrates dashboards without app gadgets, you need to manually add the app gadgets to the migrated Jira dashboards and configure them to match the setup in the original Jira Cloud instance.

Migration of app data during a Confluence Cloud-to-Cloud migration

Great Gadgets for Confluence Cloud consists only of macros that are added to Confluence pages. The app has no global or user-specific settings, so the only data that needs to be migrated is the macros added to Confluence pages along with their configuration settings.

When you migrate Confluence spaces from one Confluence Cloud instance to another Cloud instance, the app macros embedded in pages (and their configuration settings) are automatically migrated.

Once the spaces are migrated to the new Confluence instance, you will also need to install Great Gadgets for Confluence Cloud in the new Confluence instance. Also, install StonikByte Connector for Jira Cloud (free app) in the Jira Cloud instance linked to the new Confluence Cloud instance. See Using the gadgets in Confluence Cloud.

Most of the app macros use data from the Jira Cloud instance linked to the Confluence Cloud instance, so they will not be functional at this stage. To restore the functionality of the macros, please do the following:

Migrate your Jira Cloud data (projects, filters, boards, fields, states, etc.) to the Jira Cloud instance that is connected to the new Confluence Cloud instance, if it has not already been migrated. This can be done by using the tools provided by Atlassian, see https://support.atlassian.com/organization-administration/docs/copy-product-data/.
After you migrated your Jira Cloud data to the new Jira Cloud instance, the migrated objects (projects, filters, boards, etc.) have different IDs in the new instance and therefore will not match the IDs in the migrated macro configuration, so they will need to be manually reconfigured to point to the migrated Jira objects (projects, filters, fields, states, etc.). Our advice is to ask the space and page owners to check and reconfigure the macros one by one.
To determine the usage of each macro, go to Confluence administration > Data management > Macro usage. The app gadgets are the ones having “comStonikbyteGreatGadgetsConfluencePlugin“ in their name. Clicking link of a used macro, will show the Confluence pages that use that macro.