- IT admins running Server/Data Center → Cloud migrations
- Teams reorganizing Confluence spaces after a reorg or M&A
- Engineering converting Confluence content to/from Markdown, HTML, or JSON
- Which tool fits each scenario — CCMA, built-in XML, or Modern Importer Exporter
- The 5 most common migration pitfalls (broken links, missing attachments, macro failures) and how to avoid each
- How to choose an export format by fidelity vs portability
- A copy-paste migration checklist for pre-migration, export, import, and validation
Migrating Confluence content is something most teams eventually face. Whether you are moving from Confluence Server to Cloud, reorganizing spaces after a company merger, or splitting a monolithic workspace into focused team spaces, the process can feel overwhelming. Pages link to each other, attachments sit deep in page trees, permissions are inherited from parent spaces, and macros pull data from external sources.
This guide walks through the entire Confluence content migration process from start to finish. You will learn how to plan your migration, choose the right tools for your scenario, export and import content without losing data, and validate the result. We cover both Atlassian's built-in export features and the Modern Importer Exporter for Confluence app for format-based migrations.