Migrating from Confluence Data Center to Cloud

If you're moving your Confluence instance from Data Center to Cloud, here's what to expect for Page Branching.

Your content is safe. Every page migrates, including pages that were branches in Page Branching for Data Center - with their full content, history, attachments, and permissions intact.

What doesn't carry over is the branch relationship itself. Page Branching (Data Center) keeps track of which page is a branch of which original using Confluence page properties attached to those pages. The Atlassian Cloud Migration Assistant transfers standard page content, but not this kind of app-specific metadata. As a result, after migration:

• Former branch pages appear in Cloud as regular, standalone pages

• Page Branching Cloud has no way to know they were branches, or which page they belonged to

• They won't show up in the Branches overview, and merge/diff/status features won't be available for them

This isn't something we can currently work around on our end - it applies to any app that stores this kind of relationship data outside of standard page content, and it's a limitation of what the Cloud Migration Assistant transfers.

Recommended: clean up branches before you migrate

1. Merge any branches that are finished and ready - this folds the changes into the original page, so nothing is lost.

2. Delete or archive branches you no longer need.

3. For branches you want to keep working on after the move, note down the original page and the branch content. Once you're on Cloud, you can start fresh: create a new branch on the original page in Page Branching Cloud and bring over the relevant changes.

Doing this cleanup beforehand means you land on Cloud with a clean slate - no orphaned "used-to-be-a-branch" pages sitting in your tree.