Migration path from On-Premises to the Cloud
This guide describes how to migrate the Advanced Microsoft Teams Connector for Confluence from the Server/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 Server comparison.
Prerequisites
Confluence Data Centre instance with Advanced Microsoft Teams Connector for Confluence (Data Center) installed
Confluence Cloud instance with Advanced Microsoft Teams Connector for Confluence (Cloud) installed
Required user permissions:
Confluence Data Center
Confluence global administrator to read/export the created configurations
Confluence system administrator to install the Marketplace apps
Space admin permissions if you have space-level configurations
Confluence Cloud
Confluence site administrator (or organisation admin) to install the Marketplace apps
Space admin permissions if you have space-level configurations
Migration steps
Step 1. Migrate Confluence data from Data Center to Cloud
To start this journey, it is recommended to use Cloud migration methods for Confluence to ensure a successful migration.
If you use Atlassian Migration Assistant, on Confluence Data Center, go to Confluence administration → General configuration → Migration Assistant and run the Confluence Cloud Migration Assistant for your spaces, pages, users and attachments.
Step 2. Install the Cloud version of the app
Install the app on your Confluence Cloud site from the Marketplace: Advanced Microsoft Teams Connector for Confluence (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 Confluence 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 Confluence Data Centre as a Confluence global administrator:
Open in a browser:
CODE<CONFLUENCE_BASE_URL>/rest/microsoft-teams/1.0/configurationsIt returns a JSON array of all notification rules, including all filters and parameters (space, content type, event, target webhook, message template, labels, etc.). Save it as e.g.,
teams-confluence-configurations.jsonfor reference when rebuilding rules on Cloud.
Troubleshooting
Empty
[]— no rules configured, or the app is disabled. Re-enabling the app under Manage apps requires Confluence system administrator.401 / 403 — your account is not a Confluence global administrator.
Step 4. Recreate notification rules in Confluence 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 Connector for Confluence (Cloud)
Step 5. Validate and cut over
Trigger a matching Confluence event for each new notification rule (page created/updated/commented/labelled) 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: