Moving from Jira Data Center to Cloud used to mean rebuilding every Microsoft Teams notification rule by hand. Not anymore. Advanced Microsoft Teams Connector for Jira now includes a migration assistant that brings your configuration from the Data Center app to the Cloud app, so your teams keep getting the right notifications after the move.
Get the Cloud app on the Atlassian Marketplace →
What comes across
- Notification rules at every level: global, project, personal and per-issue rules.
- Filters: issue types, priorities, statuses, components, labels and JQL, plus user filters such as assignee, reporter and watchers, matched to the right Cloud accounts.
- Saved Jira filters: converted to their JQL, because filter IDs change when you migrate.
- Personal rule options: watching, assigned, created and mentioned.
- Webhook URLs and bot configuration, so channel notifications keep flowing to the same places.
- The events you rely on: issue, comment, worklog, link, version released and sprint events map directly to Cloud.
For the complete list, see the migration guide.
Two ways to migrate
With the Cloud Migration Assistant
If you're moving with Atlassian's Cloud Migration Assistant, include the app in your migration plan and your Teams configuration travels with the rest of your data. The migration guide walks you through it step by step.
With a JSON export
Already migrated, or can't use the Cloud Migration Assistant? Export your configuration as a JSON file from the Data Center app and upload it on the new Migration page in the Cloud app. Before you import, the page shows a preview of how many rules and URLs are in the file. You can protect webhook URLs in the export with a migration secret of your choice.
The Migration page also shows live progress while a job runs and a history of past jobs. Re-running a migration updates existing records instead of creating duplicates.
No surprises: the gap report
Jira Cloud doesn't support everything Data Center does. Instead of dropping settings silently, the assistant lists anything that couldn't be carried over in a gap report, so you know exactly what to review after the move.
After you migrate
- Check notifications arrive as expected. Data Center and Cloud can both send notifications for a while, so you can compare before you switch Data Center off.
- Review flagged rules. Some rules may be split or switched off for review. The Migration page tells you which.
- Reconnect and check users. Follow the post-migration checklist in the migration guide to reconnect the bot and make sure Teams users are linked to the right Jira Cloud accounts.
The Jira side now runs on Forge
There's another change under the hood: the Jira side of Advanced Microsoft Teams Connector for Jira Cloud now runs on Atlassian Forge. Configuration, rule matching, scheduling and the Rovo agent's data now live on Atlassian's platform, while Teams messages are still delivered by our Microsoft Teams bot. Existing customers move over when their Jira admin accepts the latest major version update. We wrote about how we sped up our Forge migrations with AI on the Atlassian blog.
Moving other apps too?
Several of our other apps support the move to Cloud as well, including GitHub links, GitLab and Azure DevOps for Confluence, Advanced Google Chat for Jira and Jigit. See what moves for each app.
More new from Move Work Forward
- Meet Platypus: Jira dates that reschedule themselves
- Moving from Data Center to Cloud? Our apps move with you
- Two-way sync between Jira and Azure DevOps is here
Keep reading
- Microsoft Teams Jira notifications: configuration guide
- Microsoft Teams and Atlassian: the definitive guide
- Jira notifications in Microsoft Teams not working? Here's how to fix it
Plan your move
Install the Cloud app, then migrate with the Cloud Migration Assistant or a JSON upload, using the migration guide. If you'd like help planning, our support team is happy to walk through it with you.
