Atlassian

Which Plugins Also Work in the Atlassian Cloud?

Which Jira and Confluence plugins keep working after migrating to the Atlassian Cloud – and how the Cloud Migration Assistant helps you check.

XALT favicon: white XALT logo on black background with digital light effects.TEAM XALTAtlassian Platinum Partner·11 October 2024·6 min
Digital cloud with pixel pattern in the foreground surrounded by icons and connection lines over a cityscape.

Migrating from Atlassian Data Center or Server to the Cloud brings numerous benefits: better scalability, automatic updates, and less maintenance effort. However, many companies face a question before migration: Which plugins also work in the Atlassian Cloud?

Atlassian products such as Jira and Confluence are often extended by various Marketplace apps that were specifically developed for the on-premise versions. When migrating to the Cloud, it is therefore important to know whether these extensions can still be used. In this article, we show you what you should pay particular attention to regarding app migrations to the Atlassian Cloud.

Fundamental differences between apps for Server/Data Center and Cloud

Extensions for the Server or Data Center versions of Atlassian products are often deeply integrated into the systems and use specific APIs or direct system access. In the Cloud environment, such access is often not possible or handled differently. Therefore, a plugin may not be available in the Cloud or may function differently than usual.

Some vendors have adapted their plugins for the Cloud or offer similar or extended features, while others focus exclusively on the on-premise versions.

App assessment with the Atlassian Cloud Migration Assistant

To find out which of your used plugins are available in the Cloud, the Atlassian Cloud Migration Assistant (Assistant for Jira or Assistant for Confluence) helps you. This tool supports you in planning and carrying out the migration and offers the following features:

  1. Analysis of your installed apps: The Migration Assistant lists all currently installed plugins and indicates whether a Cloud version exists.
  2. Compatibility check: You receive information on whether the Cloud version offers the same features or if there are differences.
  3. Contact options: For plugins that are not available in the Cloud, you can contact the vendor directly via the tool to ask about alternatives or future plans.
  4. Recommendations for alternatives: Where possible, the tool suggests alternative apps from the Atlassian Marketplace that offer similar features in the Cloud.

Specifics regarding Confluence: User Macros are not available in the Cloud

If you use Confluence, please note that User Macros are not supported in the Cloud. These custom macros, which are frequently used in the Server version for individual design and functional extensions, cannot be deployed directly in the Cloud. While this is not a limitation of Marketplace apps, it is still important for planning your migration, as it can affect the display and functionality of your Confluence pages. In principle, many functions of Confluence User Macros can also be replicated using built-in features such as Automations.

Challenges and tips for migration

  • Data transfer from plugins: Some plugins store their own data. Clarify before the migration how this data can be transferred to the Cloud and whether this is possible at all.
  • Functional differences: Even if a plugin is available in the Cloud, features may be missing or implemented differently. Therefore, test the Cloud versions of your most important plugins at an early stage.
  • Licensing and costs: In the Cloud, many apps are based on a subscription model. Check the costs and licensing terms to avoid surprises.

How to proceed best

  1. Create a list of your used plugins: Note down all extensions that are in use in your current environment.
  2. Use the Cloud Migration Assistant: Run an analysis with the tool to get an overview of Cloud availability.
  3. Plan replacements for unavailable plugins: Look for alternatives or consider whether certain functions are perhaps already covered by the standard Cloud version.
  4. Test the Cloud environment: Use a test migration or a sandbox to check functionality and identify potential problems at an early stage.

Find best practices for migrating to the Atlassian Cloud here: Atlassian Cloud Migration Best Practices

Conclusion

Migrating to the Cloud is a significant step that requires careful preparation. In particular, the availability and functionality of the plugins used are of central importance. The Atlassian Cloud Migration Assistant is a useful tool for assessing your applications and planning the transition. Answering the question "Which plugins also work in the Atlassian Cloud?" essentially depends on the migration and the requirements of the respective company.

Please note that not all functions can be transferred directly. It is advisable to make appropriate adjustments. In case of questions or uncertainties, it is recommended to contact the plugin providers or Atlassian experts directly.

The Cloud offers many advantages and opportunities – with the right preparation, you can use them optimally for your company.

BETTER CALL XALT

Do you know which of your plugins are cloud-ready?

We check your apps before the migration and find suitable alternatives for anything that isn't available in the cloud.

From the same category

More articles

Atlassian

Personal AI Agents Compared: Rovo, OpenClaw, and Agent SDKs Like Claude or OpenAI

Rovo, OpenClaw, or Claude/OpenAI: how personal AI agents differ in 2026 and which approach fits your team.

BaFin-compliant Atlassian Cloud migration for financial service providers
Atlassian

BaFin Compliance for Atlassian Cloud – What Financial Institutions Need to Know Now

New EU FSA rules have been in effect for Atlassian Cloud in financial services since December 2024. We show what has changed and how you can migrate to the cloud in a BaFin-compliant way.

Atlassian Team '26: the move to the AI-native organisation
Atlassian

Atlassian Team '26 Recap: The Shift to the AI-Native Organization and the Role of the Teamwork Graph

XALT was on the ground at Atlassian Team '26 in Anaheim. Our recap covers the Teamwork Graph, Rovo, and the new Teamwork, Service, Product, Software, and Strategy Collections – and what it means for enterprises in Germany.