DC to Cloud migration guide

DC to Cloud migration guide

Here is what you need to know about migrating your Jira Data Center instance with Chat for Jira Service Management to Jira Cloud.

What is migrated

At this time, the set of Chat app data migrated from to Cloud includes:

  • Applicable global settings

  • Chat for JSM 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)

Global Chat settings, translations, agent schedules, and Chat project settings are overwritten during each migration. In other words, changes in Chat configuration made on the Cloud instance are overwritten by the configuration from Data Center every time a migration runs.

How to run the migration

  1. Ensure that you have the latest version of Chat for Jira Service Management Data Center.

  2. Ensure that you have Chat for Jira Service Management installed on your Cloud instance.

  3. Run a migration of your Jira Service Management projects with the Chat add-on selected for migration.

  4. To work around this work item with the Jira migration tool, uninstall and reinstall Chat for Jira Service Management on the Cloud instance.

  5. Run another migration. This time select no projects, but add to the scope only Chat for Jira Service Management.

  6. Verify that the data is migrated:

    1. Go to the Global Chat Settings page and verify that the settings supported in Cloud are migrated.

    2. Go to the Translate and Customize page, and verify that translations have been properly migrated.

    3. Go to Project Settings > Chat for JSM page for each of the migrated projects, set Work Item Type for Chat, and verify settings there.

    4. On the Chat for JSM page, disable and enable Chat of the migrated projects to see Chats dashboard in them.

    5. Ask each Jira Service Management agent to verify if their Chat schedule has been migrated.

    6. 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 that were created by anonymous users. This means these work items will have a different last update time compared to the same work items on Jira Data Center.

You can use the following JQL to show migrated conversations sorted by the update time from Jira Data Center:

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 Data Center

Check out this page to see how Chat for JSMdiffers between Cloud and Data Center. We're continuously working to bring the most popular features to both versions. New Cloud features are released regularly. Watch the What's New banners for the latest updates.

Configuration differences

After migrating from Data Center to Cloud, you will have to update your Chat settings inside your service project. If you are using Chat Widget on an external website, you should update your Chat Widget JavaScript code on your external website according to the provided code in Chat for JSM settings.

Need support? Create a request with our support team.

Copyright © 2005 - 2025 Appfire | All rights reserved.