Reduce Migration Risk: Ensure Metadata Readiness Before Moving to Confluence Cloud

[#1]

Hello there!

I'm Elena from Elevatic. 

Planning a move to Confluence Cloud? One overlooked detail in your metadata setup could cause your migration to fail.

Migrating from Data Center to Cloud requires preparation. One of the most common challenges during migration is discovering blockers only after the migration has already been executed.

With the latest release of Metadata for Confluence Data Center, new pre-migration checks help administrators identify potential blockers before starting the migration process.

This update improves transparency and reduces unexpected issues during Cloud migration.

The most important preparation step is this:

Space metadata must be converted into global metadata in the Data Center instance before migration.

If this step is skipped, the space metadata cannot be migrated to Cloud. To simplify this process, a script is available that automatically converts space metadata into global metadata. The script can be requested through our support team.

The latest release of Metadata for Confluence Data Center introduces new checks that help teams identify such issues before starting the migration.

Convert Space Metadata into Global Metadata

Metadata Cloud app does not support space metadata in its current structure.

If space metadata is used in the spaces selected for migration:

• It must be converted into global metadata
• The conversion must be completed before migration
• Otherwise, space metadata will not be migrated

A new warning now automatically checks whether space metadata is used in the selected spaces.

If detected:

• A message appears in the interface
• The system informs you that a transformation is required
• You can contact support to apply the conversion

This allows teams to plan the conversion step instead of discovering the issue after a failed migration attempt.

Additional Checks

In addition to the space metadata warning, three checks now identify critical configuration issues before migration.

These prevent common issues that previously caused failed migrations:

1. Duplicate Metadata Titles

• Cloud requires unique titles for global metadata fields and sets.
• Duplicate titles will cause migrations to fail after execution.

With the new check:

• A report lists duplicates before migration
• Titles can be renamed in advance
• The migration can run successfully on the first attempt

2. Multiple Metadata Sets on the Same Content

• Cloud allows only one global metadata set per page or blog post.
• Multiple sets assigned to the same content block migration.

With the new check:

• A report lists affected pages
• Only one set per page should remain
• The migration can proceed smoothly

3. Select Fields with More Than 30 Options

• Cloud supports up to 30 options for single-select and multi-select fields.
• Fields exceeding this limit block migration.

With the new check:

• A report lists affected fields in advance
• Field options can be reduced before migration
• Migration can run successfully on the first attempt

What This Means for Migration Planning

With these checks in place:

• Issues are visible before migration starts
• Teams can fix problems in advance
• Failed migration attempts are reduced
• Planning becomes more reliable

Metadata structures support important business processes. Preparing them properly avoids interruptions during the Cloud transition.

For more details or guidance on your specific setup, reach out to us via support.