Skip to end of banner
Go to start of banner

Migrating from Visibility Server to Visibility Cloud

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

This page outlines the steps to migrate your Visibility data from the Confluence Server or Data Center to the 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 and feature differences between Visibility for Confluence Server and Confluence Cloud. 

  • Perform the migration using the Confluence Cloud Migration Tool or through Space Exports.

  • Check and re-configure your Visibility data in Confluence Cloud.

Depending on how large your Confluence data is, these may take a few hours to complete.

Guide

Step 1 - Plan out your migration

Before you start, consider the following:

  • Understand the macro and feature differences between Visibility for Confluence Server and Confluence Cloud. 

    • Understand the effects of Show if / Hide if macros using parameters not available in the Cloud.

    • Understand the effects of Show if / Hide if macros that contain elements not available in the Cloud.

  • Understand how many Visibility macros are on your site

    • You can easily find 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 with your pages.

  • Make sure you mark the app as Needed in the Cloud.

Step 3 - Check if your data are all intact

Things to take note of:

  • The User Groups parameter in the Cloud may not work correctly if the Groups are not migrated to the Cloud.

  • Refer to the feature differences for other Visibility macro behaviors different from Server & Cloud.

  • No labels