Migration path from On-Premises to the Cloud

This guide describes how to migrate the Advanced Microsoft Teams Connector for Jira from the Data Centre version to the Cloud.

Important: The connector's configurations are not migrated automatically. You will need to install the Cloud app and manually recreate the rules, using an exported reference of your Data Centre configurations.

Roadmap: We are exploring automating the migration of created notifications, including all filters and parameters. This guide will be updated as soon as this feature becomes available.

Before you start, review the feature differences between the Cloud and Data Center versions: Cloud vs Data Center comparison.

Prerequisites

Jira Data Center instance with Advanced Microsoft Teams Connector for Jira (Data Center) installed
Jira Cloud instance with Advanced Microsoft Teams Connector for Jira (Cloud) installed
Required user permissions:
- Jira Data Center
  - Jira global administrator to read/export the created configurations
  - Jira system administrator to install the Marketplace apps
  - Space admin permissions if you have space-level configurations
- Jira Cloud
  - Jira site administrator (or organisation admin) to install the Marketplace apps
  - Space admin permissions if you have space-level configurations

Migration steps

Step 1. Migrate Jira data from Data Center to Cloud

To start this journey, it is recommended to use Cloud migration methods for Jira to ensure a successful migration.

If you use Atlassian Migration Assistant, on Jira Data Center, go to Jira administration → System → Migrate to Cloud and run the Jira Cloud Migration Assistant for your projects, work items, users and attachments.

Step 2. Install the Cloud version of the app

Install the app on your Jira Cloud site from the Marketplace: Advanced Microsoft Teams Connector for Jira (Cloud).

Step 3. Export your existing configuration from Data Center

This step is optional. If you already know which notifications you need on Cloud, you can skip this step and go straight to Step 4. Recreate notifications 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.

The flow via accessing REST endpoint requires you to be logged in to Jira Data Centre as a Jira global administrator:

Open in a browser:

CODE

<JIRA_BASE_URL>/rest/microsoft-teams/1.0/configurations

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., teams-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.

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:

More information can be found here: Advanced Microsoft Teams Jira Connector (Cloud)

Step 5. Validate and cut over

Trigger a matching Jira event for each new notification rule (create/update/comment/transition) and confirm the message lands in the expected Teams channel with the right content.
If possible, run DC and Cloud in parallel for a brief period to compare volume and content.
Once Cloud is verified, disable or delete the notifications on Data Center to avoid duplicate notifications, and uninstall the DC version when the instance is decommissioned.

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:06 May 2026