Skip to main content
Skip table of contents

Redirection for Confluence Feature Differences

Migration Path

Original Platform

Target Platform

Available App Migration Path

License Migration




Migration Path is available


  • 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





Versioning/LicenseVersion Support

Min migratable Version :  5.3.2

Migrate to Redirection for Confluence using steps at Migration Path
LicenseAvailable through Atlassian 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 Differences

Integration with other macros

 Redirection for Confluence Server application allows

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

Redirection for Confluence Cloud application in cloud have the following limitations:

  • Does not support nested macros which means Redirection for Confluence Cloud macros cannot be placed in a nested container (such as inside an expand macro, etc.)
  • Due to the above, integration with other macros may be difficult.

Macro Differences Overview

Server Macros 

Cloud Macros 

Macros availability

Only some macros in Redirection for Confluence are available in Cloud:

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

    • (warning)  – Partially available

  • Macros that are migratable 

    • Migration for Redirect macro works out of the box.

  • For macros that are migrated but are unsupported, the following applies:

    • You may see an "unknown macro" where the macros were originally positioned in the documents.

  • 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




Supported macro parameters

  • Visible
  • Location
  • Delay

Supported macro parameters

  • Visible
  • Location
  • Delay
  • Confluence Attachment

(warning) Notes about Cloud migration and Cloud behavior

  • Redirecting to a Confluence attachment is available on both server and cloud. However, the location of the attachment is specified differently. 
    • Server uses the Location parameter.
    • Cloud uses the Confluence Attachment parameter.

    Migrating users who use this parameter will need to modify it or the Redirection macro will not work. For more details, refer to this KB article for the steps.
  • Blocked by browsers
    • On the Cloud platform, some browsers (e.g., Chrome) may attempt to block the redirect. If this happens, you will need to click the   Pop-up Blocked   icon in the address bar and configure the browser to always allow redirects for your Confluence site.
  •  Redirection notice
    • Due to Atlassian's security policies, there will always be a popup about "Redirection Notice".
    • Just click Allow for the Redirect macro to continue.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.