Here is what you need to know about migrating your Jira Server instance with Chat for Jira Service Management to Jira Cloud.
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.
Chat conversations from signed-in and anonymous users.
Chat conversations' metadata (including custom metadata).
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.
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, set Issue Type for Chat and verify settings there.
- On Chat Settings page disable and enable Chat of the migrated projects in order to see Chat Dashboard in them.
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.
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:
issue.property[com.spartez.supportchat.chat.metadata].migrated IS NOT EMPTY ORDER BY issue.property[com.spartez.supportchat.chat.metadata].lastUpdatedBeforeMigration DESC
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.