Jira Instance Migration

Google Sheets exports are stored on Google's servers and tied to your Google Service Account. This means that the same credentials file can be used in any Jira instance type and the Published Sheets page will show the same exports, regardless of whether they were originally created from Jira Server, Data Center, or Cloud. All of your exported data will still be accessible. However, there are some subtle but important differences between instance types that will impact add-on functionality when changing instance types. These differences should be considered when migrating from one instance type to another, and may require Mobility Stream's assistance in order to maintain full functionality.

Server ↔ Data Center Migration

If you are migrating between Jira Server and Data Center and keeping the same Jira instance URL, no additional changes will be necessary. With regards to the Google Sheets Integration add-on, these two platforms are functionally the same. If you are changing your Jira instance URL, you may want to update any links in your exports to point to the new instance URL.This change can be performed manually or by Mobility Stream if you have a large number of exports to change.

Server/Data Center ↔ Cloud Migration

If you are migrating between Jira Server/Data Center and Cloud, there are several changes required. Because of the differences in identifiers stored in export metadata, the following must be changed:

1. Sheet Owner: Server/Data Center uses the user key to identify the owner of an export, while Cloud uses the user's account ID. If exports are not updated after migration, non-admin users will no longer be able to access or manually update their exports from Jira. The exports will still be accessible in Google.

2. Filter ID: Depending on your migration, the ID of the filter used to create an export may change. If it does, exports must be updated in order to retain filter-related functionality.

3. JQL: Exports created from JQL that includes user identifiers will need to have the JQL updated to use the new instance's identifiers or export updates from the new instance type will fail.

4. Instance URL: Exports will need to be updated so that any links point to your new instance URL, if the instance URL is changing and you have not set up a redirect from the old URL to the new URL.

Jira Cloud supports custom update schedules for exports but the functionality is different between Server/Data Center and Cloud. Any sheets that have custom update schedules will initially revert to manual update in your Cloud instance, and users will have to recreate their custom schedules.

Mobility Stream has developed a utility to automate the majority of the changes required for a Server/Data Center ↔ Cloud migration. We encourage users to remove any unused exports before migration, in case it may be easier to recreate the exports from the new instance. Please contact us to discuss additional details if you are planning this type of migration.