Visibility for Confluence Feature Differences

Migration Path

Original Platform

Target Platform

Available App Migration Path

License Migration

Notes/Consideration

Server/DC

Cloud

Migration Path is available

Needed

  • Understand the feature difference (see below) between the application for Confluence Server and Confluence Cloud.

  • Allocate time for a test migration to understand the steps required to migrate data and complete re-configuration.

  • This guide assumes you have successfully migrated your  Confluence Server data into Confluence Cloud, per  Atlassian's instructions (CCMA). More Atlassian resources are available here.

Feature Differences

Migration Focus Area

Feature

Platform


Server

Cloud

Versioning/LicenseVersion Support

Min migratable Version : 4.2.2

Migrate to Visibility for Confluence using steps at Migration Path
LicenseAvailable through both Atlassian Marketplace and ServiceRocket Marketplace.Available through Atlassian Marketplace only. Monthly subscriptions are the default option; however, discounted annual subscriptions are available upon request to our Atlassian Sales team.
Confluence DifferencesIntegration with other macros

Visibility for Confluence server allows

  • Integration with other macros.
  • Support of nested macros which means Visibility macros can easily be nested and integrated with other Confluence native macros or any third-party macros

Visibility for Confluence cloud has the following Confluence Cloud limitations:

  • Does not support nested macros.
    • Visibility macros cannot be placed in a container (such as inside an expand macro, etc.)
    • Cannot place a container inside Visibility macros (such as inserting an Expand macro, etc.)
  • Due to the above, integration with other macros may be difficult.

Macro Differences Overview

Server Macros 

Cloud Macros 

Macros availability

All macros in Visibility for Confluence are available in Cloud:

  • Look out for icons highlighting how the data will be migrated.
    • (tick)  Available 
    • (error) – Unavailable

    • (warning) – Partially available

  • All macros are migratable to Cloud


  • Find details of each migratable macro below and the differences in terms of behavior once migrated to Cloud.

Macro Differences Breakdown

Macro Name

Key Differences

Server

Cloud

Supported macro parameters

  • Match Using (tick)
  • Users (tick)
  • Special Usernames
  • User Groups (tick)
  • Space Permissions
  • Content Types
  • Display Types
  • Current Space
  • Action Types
  • Labels
  • HTTP Headers
  • Scope
  • Trim

Supported macro parameters

  • Match Using
  • Users
  • User Groups

(warning) Notes about Cloud migration and Cloud behavior

  • While the functions of these parameters do not have any output and the values are ignored in Cloud, all migrated data will be retained. Some of the parameters may be coming to Cloud in future releases.

Which server feature would you like to see in Cloud? Please feel free to take our ongoing survey and we will prioritize accordingly.