Migration Steps

On this page

1 Migration from Server / Data Center to Cloud
2 Migration from Server to Data Center
3 Migration from Cloud to Cloud
- 3.1 Migration of app data during a Jira Cloud-to-Cloud migration
- 3.2 Migration of app data during a Confluence Cloud-to-Cloud migration

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.

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. 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. No other migration steps are needed. There is no data to migrate because this app just processes and displays issue-related data taken from Jira.

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).

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 Copy data from one instance of a cloud product to another | Atlassian Support).

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 consists only of macros that are added to Jira dashboards. The app has no global or user-specific settings, so the only data that needs to be migrated is the gadgets added to Jira dashboards along with their configuration settings.

Currently, the Atlassian migration tool does not support dashboard migration between Jira Cloud instances (see https://jira.atlassian.com/browse/CLOUD-11480), so the migration of the Jira dashboards and the app gadgets will be a manual process:

Migrate your Jira Cloud data (projects, filters, boards, fields, states, etc.) to the new Jira Cloud instance. This can be done by using the tools provided by Atlassian, see Copy data from one instance of a cloud product to another | Atlassian Support.
Once the Jira data is migrated to the new Jira Cloud instance, you will need to install Great Gadgets for Jira Cloud in the new Jira Cloud instance.
Since Atlassian tools do not support dashboard migration, create Jira dashboards manually in the new Jira Cloud instance (unless you have found a better method).
Add the necessary gadgets to the newly created dashboards and configure them manually as in the old 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 Great Gadgets for Jira Cloud or StonikByte Connector for Jira Cloud 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 Copy data from one instance of a cloud product to another | Atlassian Support.
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.