Here is what you need to know about migrating your Jira Server instance with Chat for Jira Service Management to Jira Cloud.Table of Contents
...
Table of Contents
| Info |
|---|
Automatic app data migration will be available as soon as Atlassian enables apps migrations in Jira Cloud Migration Assistant. As of 9 February 2021, migrating app data is not officially supported by the migration assistant. You can still use it, but this requires enabling the com.atlassian.jira.migration.app-migration.feature Dark Feature in your Jira Server instance (click the link to learn how to enable dark features in your Jira). After enabling the dark feature, you have to restart your Jira for the change to get applied to the system. |
When performing the migration, make sure that you have Chat version 1.8.0 or newer installed on your Jira Server. Then, verify that the app can be migrated:
Clicking Assess and install apps should bring up this page:
Green tick in the Can be migrated column means that Chat's data will be migrated to cloud during your migration process.
What is Migrated
| Note |
|---|
Chat conversations are stored as issues and comments. Therefore, the main part of conversation data migration will be done by Jira Cloud Migration Assistant. |
At this time, the set of Chat app data migrated from Server to Cloud includes:
- translations
- applicable global settings
What is NOT Migrated
At this time, the following are not migrated:
...
What is Migrated
At this time, the set of Chat app data migrated from Server to Cloud includes:
Applicable global settings.
Chat Settings for all the migrated Jira projects.
Agents online/offline schedule.
Translations.
Chat conversations from signed-in and anonymous users.
Chat conversations' metadata (including custom metadata).
| Info |
|---|
Chat global settings, translations, agent schedules and Chat project settings are overwritten with each migration. In other words, changes in Chat configuration made on Cloud instance are overwritten by the configuration from Server every time a migration runs. |
Running migration
Ensure that you have the latest version of Chat for Jira Service Management Server.
Ensure that you have Chat for Jira Service Management installed on your Cloud instance.
Run a migration of your Jira Service Management projects with the Chat add-on selected for migration.
To walk-around this issue with the Jira migration tool uninstall Chat for Jira Service Management on the Cloud instance and re-install it.
Run another migration. This time select no projects, but add to scope only Chat for Jira Service Management.
Verify that the data is migrated:
Go to the “Global Chat Settings” page and verify that the settings supported in Cloud are migrated.
Go to the “Translate and Customize” chat page and verify that translations have been properly migrated.
Go to the Chat Settings page for each of the migrated projects and verify settings there.
Ask each Jira Service Management agent to verify if their Chat schedule has been migrated.
Go to the Chat Dashboard page for each of the migrated projects and validate if the conversations have been migrated.
| Info |
|---|
During the migration, Chat changes the reporter of conversations which were created by anonymous users. This means, these issues will have a different last update time compared to the same issues on Jira Server. You can use the following JQL to show migrated conversations sorted by the update time from Jira Server: |
Feature Differences Between Cloud and Server
We are aiming at providing feature parity between Server and Cloud versions of Chat for most wanted features. New features are continually added to the Cloud version - watch the "What's New" announcement banners for details.
Configuration Differences
After migrating from Server to Cloud, you will have to update your Chat Settings inside your service project. If you are using Chat Widget at the external website, you should update your Chat Widget JavaScript code at your external website according to the Chat Settings provided code - compare code snippets for Cloud and Server.