Advanced Google Chat for Jira - Migrating from Data Center to Cloud

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

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

Prerequisites

Jira Data Center

• Jira Data Center instance with Advanced 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

• 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

Recommended: Migrate with the Jira Cloud Migration Assistant

The Jira Cloud Migration Assistant (JCMA) is Atlassian's own tool for moving a whole Jira Data Center site to Cloud. Advanced Google Chat for Jira participates directly in it - your notification rules travel across as part of the same migration run as your projects and issues, rather than needing to be rebuilt separately afterwards.

Step 1. Install the Cloud app first

Install Advanced Google Chat for Jira (Cloud) from the Atlassian Marketplace on your target Jira Cloud site, before you run the migration. JCMA transfers notification-rule data into an app that's already installed - it doesn't install the app for you.

Step 2. Launch the Jira Cloud Migration Assistant

1. In Jira Data Center, navigate to Jira Administration → System → Migrate to Cloud.

2. Launch the Jira Cloud Migration Assistant and select your projects, issues, users, and other Jira data as usual.

3. When choosing which Marketplace apps to include, select Advanced Google Chat for Jira.

Step 3. Review the app's pre-migration checks

Advanced Google Chat for Jira runs its own checks as part of JCMA's pre-migration assessment, and will flag anything worth knowing before you proceed - for example, rules that use Data Center-only features with no direct Cloud equivalent. Review these before continuing.

Step 4. Run the migration

Once you start the migration, notification rules are exported from Data Center and transferred to Cloud automatically in the background, alongside the rest of your Jira data. You don't need to trigger anything separately for the Google Chat integration.

Step 5. Review the migration log

JCMA keeps a migration log on the Cloud side. Look for a summary line similar to:

"Data Center reported N notification rule(s) exported... M rule(s) use Data Center features that do not exist on Cloud."

Step 6. Review any rules flagged for attention

Open the Google Chat admin page in Jira Cloud. Any imported rule that would otherwise have started notifying more broadly than it did on Data Center - because of a filter or event type with no exact Cloud equivalent - is imported disabled, with a notice on the rule explaining exactly what changed. This is a deliberate safety measure: migration will never silently widen who gets notified. Review each flagged rule and re-enable it once you're satisfied with its behaviour; saving the rule clears the notice.

What migrates automatically vs. what needs a manual check

Carries over automatically, unchanged

• Rule name, enabled/disabled state, and level (global or project)

• Most event types map 1:1 (issue created, updated, commented, assigned, deleted, moved, work logged, issue linked/unlinked, and more)

• Project, issue type, priority, component, and label filters (values are re-resolved against your Cloud data)

• Message settings: "do not send message details," message fields shown, and "use threads"

• The Google Chat webhook URL itself - no re-authentication or re-entry required

Carries over, but approximated - may land disabled for review

• Five Data Center-only events (Issue resolved, closed, reopened, work started, work stopped) have no direct Cloud equivalent and are mapped to Cloud's general Issue transition event - which fires on any transition, so it's broader than the original.

• Data Center's "all available values selected" and "any change" filter-matching modes are approximated to Cloud's All/Any matching.

• A Data Center rule referencing a project key that doesn't yet exist on Cloud is imported and kept, but stays dormant until a matching project is created.

Does not carry over - needs manual setup if you rely on it

• Excluded-projects lists - Cloud only supports an include-list, not an exclude-list. A rule using exclusions is imported without that exclusion (widening it), so it lands disabled for review.

• Status filters - no Cloud equivalent; dropped from any rule that used one (also lands disabled for review, since this widens scope).

• "Notify only if these specific fields changed" (Data Center's field-level update filter) - no Cloud equivalent; dropped (also lands disabled for review).

• Attachment added / attachment removed events - no Cloud equivalent at all. A rule using only these events won't have anything left to trigger it; a rule using these alongside other events keeps working for its other events, just narrower than before.

• "Show action buttons" toggle - no Cloud equivalent; Cloud always shows the action button. Cosmetic only, no action needed.

How to verify notifications after migration

There's no built-in "test send" feature - the most reliable check is to trigger a real event and confirm delivery:

1. Check the Google Chat admin page in Jira Cloud for any rules still showing a migration notice, and resolve those first (see Step 6 above).

2. Pick a project and event type covered by one of your migrated rules.

3. Create or update a test issue to trigger it (for example, add a comment, or transition its status).

4. Confirm the notification arrives in the expected Google Chat space, with the expected content.

5. Repeat for each distinct rule you depend on - a rule with no matching test event won't be exercised by any single test.

Post-migration reconfiguration checklist

• Review and re-enable every rule flagged with a migration notice, once you've confirmed its new (narrower or approximated) behaviour is acceptable

• For any dormant rule referencing a not-yet-created Cloud project, revisit it once that project exists

• If you relied on excluded-projects, status filters, or the field-level update filter on Data Center, rebuild the equivalent behaviour manually where possible (for example, an include-list instead of an exclude-list)

• No Google Chat re-authentication is required - the webhook URL migrates as-is

Fallback: Manual migration

Use this if you're not using the Jira Cloud Migration Assistant, or if you'd simply rather rebuild your rules by hand.

Step 1. Install the Cloud version of the app

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

Step 2. Review existing notification configurations (optional)

This step is optional. If you already know which notification rules you want to recreate in Cloud, skip ahead to Step 3. The export below is a convenient reference if you'd like a complete list of your existing rules and their 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: <JIRA_BASE_URL>/rest/google-chat/1.0/configurations

2. 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 (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 3. Recreate notification rules in Jira Cloud

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

• How to Set Up Notification Rules

  • Global Notifications (Jira Admin)

  • Space Notifications (Space or Jira Admin)

Step 4. 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, or 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 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

• Advanced Google Chat for Jira Cloud Documentation

• How to create Incoming Webhooks for Google Chat Spaces

• Advanced Google Chat for Jira Cloud vs Data Center Comparison

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: September, 2026