Skip to main content
Skip table of contents

Migrating from Visibility Server to Visibility Cloud

This page outlines the steps to migrate your Visibility data from Confluence Server or Data Center to Confluence Cloud

At the end of this guide, you will have:

  • Upgraded Visibility macro to at least version 4.2.2 and or above
  • Understand the macro differences and feature differences between Visibility for Confluence Server and Confluence Cloud. 
  • Perform the migration using Confluence Cloud Migration Tool or through Space Exports.
  • Check and re-configure your Visibility data in Confluence Cloud.

These may take a few hours to complete depending on how large your Confluence data is.


Step 1 - Plan out your migration

Before you start, consider the following:

  • Understand the macro differences and feature differences between Visibility for Confluence Server and Confluence Cloud. 
    • Understand what are the effect of Show if / Hide if macros that are using parameters that are not available in Cloud
    • Understand what are the effect of Show if / Hide if macros that contain elements that are not available in Cloud
  • Understand how many Visibility macros that are on your site
    • You can easily find out the location of all your Visibility macros by going to Confluence Admin > Macro Usage > Search for "Visibility "
  • Allocate time for a test migration to understand the steps required to migrate data using the Atlassian migration tool (CCMA)

Step 2 - Migrate your site using the Confluence Cloud Migration tool

  • Atlassian migration tool (CCMA) will migrate all Visibility macro data together with your pages.
  • Make sure you mark the app as "Needed in Cloud"

Step 3 - Check if your data are all intact

Things to take note of:

  • "User Groups" parameter in Cloud may not be working properly if the Groups are not migrated to Cloud.
  • Refer back to the feature differences for other Visibility macro behavior that is different from Server & Cloud

To go back to the migration hub, click here.

JavaScript errors detected

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

If this problem persists, please contact our support.