Migration from Confluence Data Center to Confluence (v 3.1)

Fully Automatic Approach

We recommend using the Fully Automatic Approach whenever possible to save time and minimize manual effort.

Preconditions

The automatic migration is available for:

Confluence Data Center

All Confluence versions supported by Atlassian

Confluence Cloud Migration Assistant, version 3.11.3 (or higher)

SubSpace Navigation for Confluence 3.5.9 or 4.0.2 (or higher)

Confluence Cloud

SubSpace Navigation for Confluence Cloud 4.0.0 (or higher)

How To

The Subspace Navigation for Confluence app has to be installed and licensed in Confluence Cloud.

Follow the official Atlassian Documentation for migrating app data from your server to a cloud instance. Use the Confluence Cloud Migration Assistant to complete the migration.

After the migration, the configured SubSpace Menu will be set as the default and will be present on the administration page of SubSpace Navigation - Menu Configuration.

Limitations

All the contents (internal links) from the spaces that won’t be migrated to the cloud instance will be shown in the SubSpace Menu as an “Inaccessible item”.

Alternative Approaches

Approach	Description	Recommended For	Limitations
Semi-Automatic Approach	Generates a JSON file in Server/DC and imports it into Cloud via a guided process.	Users from versions 3.5.4 (DC) and 3.x (Cloud).	Spaces and internal links might not migrate completely, and some manual adjustments may still be required.
Manual Approach	Requires manual extraction and transformation of data from Server/DC, then configuration in Cloud.	Users with unsupported versions or specific needs to use this method.	Requires technical knowledge, internal links might not migrate successfully, manual steps needed.

Add a Page tree macro and add the parent page