If your team is planning a move from Jira or Confluence Data Center to Cloud, your apps need a plan too. Five Move Work Forward apps now support the move, and each has a step-by-step migration guide and a Cloud vs Data Center feature comparison.
Here's what to expect from each one: what comes across, what you set up again in Cloud, and where to find the guide.
The short version
- Your content comes with you. Pages with our Confluence macros and links move with your normal Confluence content migration.
- Confluence app connections are set up again. For GitHub links, GitLab and Azure DevOps for Confluence, connections and tokens are not copied across. You reconnect each integration in Cloud.
- Some apps bring their configuration too. Advanced Google Chat for Jira migrates your notification rules and keeps your Google Chat webhook URL, and Jigit brings over GitHub and Gerrit integrations.
Before you start
- Install the Cloud version of each app on your Cloud site before you run the migration, so app data has somewhere to go.
- Include the apps in your migration. When Atlassian's migration assistant asks which apps to migrate, select ours so their data moves along with your content.
- Plan time to reconnect. Have your GitHub, GitLab or Azure DevOps details ready so you can set up the Cloud connections straight after the migration.
- Check a few pages and rules afterwards. Open some migrated pages and notification rules to confirm everything works as expected.
GitHub links for Confluence
- Migrates: pages with GitHub macros move with your Confluence content through the Cloud Migration Assistant, and existing links keep working.
- Set up in Cloud: your GitHub connection. Reconnect with a GitHub App (recommended) or a personal access token, and the migrated macros render again.
- Guides: migration guide and Cloud vs Data Center comparison.
- Get it: GitHub links for Confluence Cloud on the Marketplace · product page
GitLab for Confluence
- Migrates: supported GitLab macros on your pages are converted to their Cloud equivalents.
- Set up in Cloud: your GitLab connection. Connections work differently in Cloud than in Data Center, so they are not migrated, which also keeps private repository data from reaching the wrong people.
- Good to know: migrated macros are marked (legacy) and can't be edited. To change one, insert a new Cloud macro in its place.
- Guides: migration guide and Cloud vs Data Center comparison.
- Get it: GitLab for Confluence Cloud on the Marketplace · product page
Azure DevOps Connector for Confluence
- Migrates: Azure DevOps links stay on your pages and are converted to macros automatically, as long as your new Cloud integrations can reach the same Azure DevOps organizations and projects.
- Set up in Cloud: your Azure DevOps integrations. Configurations are not migrated for security reasons, and some macro settings may need a quick review.
- Guides: migration guide and Cloud vs Data Center comparison.
- Get it: Azure DevOps Connector for Confluence Cloud on the Marketplace · product page
Advanced Google Chat for Jira
- Migrates: your notification rules, with their names, levels and on/off state; project, issue type, component and label filters, matched to your Cloud data; most event types; message settings; and the Google Chat webhook URL, so there's no need to re-authorize.
- Imported switched off, for you to review: rules that use options Cloud doesn't have (status filters, excluded projects or field-update filters), and any rule that would notify more widely than it did on Data Center. Each comes with a notice, and saving the rule switches it back on.
- Check after migrating: priority filters. Review them on your migrated rules and adjust if needed.
- Not migrated: personal notifications, and attachment events, which have no Cloud equivalent.
- Guides: migration guide and Cloud vs Data Center comparison.
- Get it: Advanced Google Chat for Jira Cloud on the Marketplace · product page
Jigit - GitHub, GitLab, Gerrit integration for Jira
- How to migrate: follow the migration guide, which walks you through moving your Jigit integrations to Jigit Cloud.
- Comes across: GitHub and Gerrit integrations, including their connections and authentication. Current branches and pull requests are re-indexed in Cloud.
- Review after migrating: point your webhooks at Cloud, ask each user to re-enter their personal credentials, and turn on commit-only integrations, which are imported switched off. Project-level settings become global. GitLab.com integrations need a quick review and save. Self-managed GitLab and Azure DevOps integrations aren't supported in Jigit Cloud; for Azure DevOps, take a look at Azure DevOps for Jira.
- Guides: migration guide and supported providers and feature comparison.
- Get it: Jigit for Jira Cloud on the Marketplace · product page
Why some connections start fresh
Moving connection details between environments is a security risk, and Cloud often handles connections differently from Data Center. Where an app doesn't carry a connection across, starting fresh in Cloud means only the people and repositories you choose are connected, with credentials created for the new site.
What's next
Migration support for our Microsoft Teams connectors is on the way. We'll link it here as soon as it's available.
More new from Move Work Forward
- Meet Platypus: Jira dates that reschedule themselves
- Two-way sync between Jira and Azure DevOps is here
Keep reading
- Azure DevOps Confluence Cloud connector
- Comparing GitHub links for Confluence and GitHub macros
- Jigit: GitHub and GitLab Jira integration features
Need a hand with your migration?
If something doesn't look right after you migrate, or you'd like a second pair of eyes on your plan, contact our support team. We're happy to help.
.png)
