How to use Space Sync with Atlassian’s Confluence Cloud Migration Assistant

Atlassian’s Confluence Cloud Migration Assistant (CCMA) is the starting point for most Confluence Cloud migrations. It helps teams move spaces from Data Center to Cloud efficiently and reliably.

However, many teams discover that migration does not end when a space is moved. During phased or extended migrations, teams often continue working across both Confluence Cloud and Confluence Data Center. This is where gaps begin to appear.

This guide explains how teams can use Space Sync for Confluence (Data Center) alongside Atlassian’s Confluence Cloud Migration Assistant to support hybrid migration and ongoing collaboration.

When this approach makes sense

Using Space Sync together with CCMA is especially useful when:

• Your Confluence migration is happening in phases

• Some teams have migrated to Cloud while others remain on Data Center

• Shared spaces need to stay aligned after migration

• Updates continue in both environments during the hybrid phase

If your migration is a single cutover with no overlap, CCMA alone may be sufficient.

What CCMA does well and where gaps appear

CMA is designed to support one-time migration. It helps you:

• Assess migration readiness

• Move spaces and users from Data Center to Cloud

• Validate migration results

Once a space is migrated, however, CCMA does not provide:

• Ongoing synchronization between Cloud and Data Center

• Support for hybrid collaboration after migration

• A way to keep content aligned if migration is paused or extended

During a phased migration, these limitations become more visible.

Step 1: Use CCMA for initial migration

CMA remains the foundation of your Cloud migration.

Teams typically:

• Prepare spaces and users using CCMA

• Migrate selected spaces to Confluence Cloud

• Validate content post-migration

At this stage, the goal is to move content, not to manage long-term coexistence.

Step 2: Identify spaces that require post-migration alignment

After migration begins, identify spaces that:

• Continue to be referenced by teams on Data Center

• Require updates during the hybrid phase

• Act as shared documentation across departments

These spaces are at the highest risk of content drift once migrated.

Not every space needs post-migration synchronization. Focus on content where misalignment creates real operational risk.

Step 3: Introduce Space Sync for hybrid coexistence

Once hybrid usage is unavoidable, Space Sync is introduced to support ongoing alignment.

Space Sync is used to synchronize selected Confluence spaces between Cloud and Data Center after migration. Rather than replacing CCMA, it extends your migration strategy by supporting hybrid coexistence.

Admins typically:

• Select migrated spaces that must stay aligned

• Define sync scope intentionally

• Establish a clean baseline through initial synchronization

This allows teams to continue working in their respective environments while keeping shared content consistent.

Step 4: Manage hybrid collaboration during migration

With Space Sync in place, teams can:

• Update shared content without manual coordination

• Avoid duplicate or conflicting versions of pages

• Maintain visibility across Cloud and Data Center

CCMA handles migration milestones. Space Sync handles day-to-day content alignment during the hybrid phase. Together, they cover different but complementary needs.

Step 5: Reduce sync scope as migration progresses

As teams complete migration and fully adopt Cloud, some spaces no longer need to stay in sync.

To keep the hybrid setup clean:

• Review synchronized spaces regularly

• Remove spaces from sync once Data Center usage ends

• Treat Space Sync as a transitional tool, not a permanent dependency

This ensures your migration continues moving forward.

Common mistakes to avoid

Teams often run into issues when they:

• Expect CCMA to handle hybrid collaboration

• Sync too many spaces without clear ownership

• Assume hybrid usage will be short-lived and skip planning

Treating CCMA and Space Sync as complementary tools avoids these pitfalls.

How this supports a smoother migration

Using Space Sync alongside CCMA allows teams to migrate incrementally without breaking collaboration. Shared Confluence spaces remain aligned, manual coordination is reduced, and admins spend less time resolving inconsistencies.

Most importantly, this approach supports real-world migration timelines, where hybrid phases are common and flexibility matters.

Extend your Confluence migration beyond one-time moves

Use Space Sync for Confluence (Data Center) together with Atlassian’s Confluence Cloud Migration Assistant to support hybrid migration and ongoing collaboration.