Skip to main content
Skip table of contents

Google Chat for Jira - Migrating from Data Center to Cloud

This guide describes how to migrate Google Chat for Jira from the Data Center version to the Cloud version.

Important: Notification configurations are not migrated automatically. You will need to install the Cloud app and manually recreate your notification rules and configurations.

Before starting your migration, review the feature differences between the Cloud and Data Center versions.


Prerequisites

Jira Data Center

  • Jira Data Center instance with Google Chat for Jira (Data Center) installed

  • Jira global administrator permissions

  • Jira system administrator permissions to install Marketplace apps

  • Space admin permissions if you have space-level configurations

Jira Cloud

  • Jira Cloud instance

  • Google Chat for Jira (Cloud) installed

  • Jira site administrator (or organisation administrator) permissions to install Marketplace apps

  • Space admin permissions if you have space-level configurations

Google Workspace

  • Access to the required Google Workspace environment

  • Permissions to configure and manage Google Chat spaces


Migration Steps

Step 1. Migrate Jira Data from Data Center to Cloud

Before migrating the Google Chat integration, migrate your Jira projects and data to Jira Cloud.

It is recommended to use Atlassian’s Cloud migration tooling to ensure a successful migration.

If using the Jira Cloud Migration Assistant:

  1. Navigate to Jira Administration → System → Migrate to Cloud

  2. Launch the Jira Cloud Migration Assistant

  3. Migrate your:

    • Projects

    • Issues

    • Users

    • Attachments

    • Workflows and configurations as required


Step 2. Install the Cloud Version of the App

Install the Google Chat for Jira (Cloud) app from the Atlassian Marketplace on your Jira Cloud instance.


Step 3. Review Existing Notification Configurations

This step is optional. If you already know which notification rules you want to recreate in Cloud, you can skip this step and go straight to Step 4. Recreate Notification Rules in Jira Cloud. The export below is just a convenient reference if you'd like a complete list of your existing notification rules and parameters before rebuilding them.

Accessing the REST endpoint requires you to be logged in to Jira Data Center as a Jira global administrator:

  1. Open in a browser:

CODE
<JIRA_BASE_URL>/rest/google-chat/1.0/configurations
  1. It returns a JSON array of all notification rules, including all filters and parameters (project, issue type, event, JQL, target webhook, message template, etc.). Save it as e.g., google-chat-jira-configurations.json for reference when rebuilding rules on Cloud.

Troubleshooting

  • Empty [] — no rules configured, or the app is disabled. Re-enabling the app under Manage apps requires Jira system administrator.

  • 401 / 403 — your account is not a Jira global administrator.


Step 4. Recreate Notification Rules in Jira Cloud

Using the export from Step 3 as a reference, recreate the equivalent rules in the Cloud connector. Setup is documented in our existing guides:


Step 5. Validate and Cut Over

After configuration is complete:

  1. Create or update Jira issues

  2. Trigger notification events such as:

    • Issue creation

    • Comments

    • Status transitions

    • Mentions

  3. Confirm notifications are delivered successfully to the expected Google Chat spaces

  4. Validate permissions and notification visibility

If possible, briefly run both the Data Center and Cloud integrations in parallel briefly to compare notifications and validate behaviour.

Once the Cloud integration has been verified:

  • Disable Data Center notification rules to avoid duplicates

  • Decommission the Data Center integration when appropriate


Additional Resources


Contact Us

If you have any questions or need help with migration, please contact our Support Team. Our dedicated team will answer all your questions and expertly guide you through the entire migration process.


Updated:

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.