Migration path from On-Premises to the Cloud | Advanced Microsoft Teams Connector for Confluence

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

The connector's notification rules migrate automatically. Reports, alerts, personal sign-in data, app sign-in data, and spaces explicitly excluded from the app are not migrated - see below for each.

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's recommended to use Cloud migration methods for Confluence to ensure a successful migration.

If you use the 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. This same migration plan is where you'll also migrate the Microsoft Teams Connector app, in the steps below.

Already migrated your Confluence data and don't want to run the Migration Assistant again just for this app? Skip ahead to Alternative: manual migration.

Step 2. Include the connector in your migration plan

Make sure Advanced Microsoft Teams Connector for Confluence (Cloud) is installed on your Cloud site, then select it in your migration plan's list of apps to migrate.

Step 3. Run the migration

Start the migration plan. The import transfers your notification rules automatically, with no manual recreation needed:

Global and space-level notification rules, with their filters (labels, parent page, included/excluded users and groups)
Each rule's own webhook URL
Global settings: which spaces the app is allowed to be configured in

If you use any of these on Data Center, you'll need to set them up again in Cloud - they aren't migrated:

Task reminder, top items, content statistics, progress statistics and app update reports
Statistics reminder alerts
Personal sign-in data (users sign in again in Cloud) and app sign-in data (credentials are never exported)
Personal user settings

Spaces excluded from the app on Data Center don't stay excluded. There's no Cloud equivalent of DC's "exclude this app in these spaces" setting - rules will notify in those spaces on Cloud too, unless you remove or scope them down by hand after migrating.

What to expect when you review the results

A few differences between DC and Cloud show up automatically during migration - these are expected, not errors:

Any-label matching becomes all-label matching. DC's "match any of these labels" has no Cloud equivalent, so a rule using it imports disabled and needs review.
Group filters are replaced by their current members. Cloud doesn't filter by group, so DC's include/exclude group filters are expanded into the individual users who were in that group at export time. A group with more than 500 members couldn't be expanded and imports disabled instead.
A rule scoped to "no spaces" imports disabled. This matches what it did on DC - it never sent anything there either.
A few display options don't carry over - minimal message content, the hidden "View" action button, and expanded message cards. The rule itself still migrates and sends notifications; only that formatting choice resets to the Cloud default.

You can see exactly what happened to each rule by opening Data Center migration and selecting the import's Details. Rules are grouped as Imported, Imported disabled (needs review), or Skipped, and a gap report lists anything that didn't carry over, split into what's simply not built in Cloud yet, what Cloud can never support, and what changed shape during import.

Step 4. Validate and cut over

Review every rule that imported disabled on the Notifications page and decide whether to fix and re-enable it, or leave it off.
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.

Alternative: manual migration

If you've already migrated your Confluence content separately - for example, before this app supported the Cloud Migration Assistant, or you simply don't want to re-run a full migration plan - you can migrate this app's configuration on its own.

On Confluence Data Center, go to Microsoft Teams Connector > Global configuration > Cloud migration and click Export. Save the file.
On Confluence Cloud, go to Confluence admin settings > Apps > Microsoft Teams Admin Settings > Data Center migration and click Import from file. Select the file you exported.
Review what the import found, then start it. Progress updates in real time and you can close the dialog without stopping it.
When it finishes, open Details to see the same per-rule breakdown and gap report as the Migration Assistant path.

Manual imports and Cloud Migration Assistant imports both appear in the same Import history, reviewed the same way - the end result is identical either way. Everything in What to expect when you review the results applies here too.

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