Cloud Migration Hub: Metadata for Confluence

Cloud Migration – Metadata for Confluence

Atlassian is ending support for Confluence Data Center by March 2029.
This page explains how Metadata for Confluence will be migrated from Data Center to Confluence Cloud, what you need to prepare, and what you can expect.

🔎 Quick overview

Question	Answer for Metadata for Confluence
Migration effort and automation level	Medium effort Global Metadata values: Largely migrated automatically. Global Metadata definitions: Automatically migrated starting with Metadata DC 3.16.0. (Manual recreation required for older versions). Display Metadata macro: Automatically migrated starting with Metadata DC 3.15.0. Manual Review required: Space Metadata, Overview macros, and specific field restrictions require manual updates.
Main risks/limitations	At the moment, migration is only supported for global Metadata sets and fields. We offer a solution to convert Space metadata into global metadata. Then you can migrate them as global metadata. To get the solution, please contact us via support. Metadata definitions: Starting with Metadata DC 3.16.0, Content Categories (Metadata sets) are migrated automatically. For older versions, manual recreation is required. The Display Metadata macro is now automatically migrated when using Metadata DC 3.15.0 or newer. Overview macro (report macro in the cloud app) will still require some manual work, but we will show the Data Center configuration of the macro. Metadata History is not supported in the cloud app. When migrating Metadata values, restrictions may apply to certain field types. Select field limit: Migration will fail if a Single or Multi-select field has more than 30 options. Link fields: Only Confluence page links are migrated; external URL links are ignored.
Key prerequisites	Metadata DC 3.16.0+ for automatic definition migration; 3.15.0+ for Display macro migration. Manual creation of Content Categories is only required for versions 3.15.0 or earlier.
Best practice	Complete the Pre-migration Checklist: Thoroughly check and establish all preconditions in the Pre Migration Checklist before starting. Update to Metadata DC 3.16.0+: Ensure you are on the latest version to benefit from automated definition migration and avoid manual recreation. Clean up duplicate titles: Ensure all Metadata sets and fields have unique titles to prevent migration failures. Follow Official Documentation: Use this guide in conjunction with Atlassian's Cloud Migration Assistant.
Available Cloud types	Available on Commercial Cloud

What Metadata for Confluence does

Metadata for Confluence adds structured, customizable metadata fields to Confluence pages so teams can standardize documentation, enforce key information, and report across content with visibility and control.

It allows admins to:

Create custom metadata fields (e.g., Owner, Review Date, Status, Compliance Level)
Group them into Content Categories
Link them to templates
Mark certain fields as required
Control the structure centrally

It allows users to:

Fill in structured information when creating or editing pages
See metadata clearly on the page
Use report macros to get live overviews across spaces
Integrate metadata with workflow tools for approvals and lifecycle management

This section explains how your app data and configuration move from Data Center to Cloud.

🔄 How to migrate

For detailed step-by-step instructions, including pre-migration checklists and technical requirements, please refer to our Metadata for Confluence Data Center to Cloud Migration Guide.

🤝 Support & resources

Documentation for Metadata for Confluence
- Link to official docs
Marketplace listing
- Link to app on Atlassian Marketplace
Cloud Security Standards
- Link to Communardo Cloud Security Standards page
Feature parity & known limitations
- Link to parity/limitations page
Need help with planning or running your migration?
- Link to Communardo support

❓ FAQ for Metadata for Confluence migration

Can users work while the migration is running?
Read-only mode for affected spaces is recommended to avoid inconsistencies.

What is not migrated automatically?

Metadata definitions: Metadata definitions are migrated automatically if using Metadata DC 3.16.0 or newer. For older versions, manual recreation is still necessary.
Space Metadata values: Space Metadata is not supported in Cloud. We offer a solution to transfer Space metadata into global metadata. You can then automatically migrate them as global metadata in Cloud. To get the solution, please contact us.
Display Metadata macro: Display Metadata macros are migrated automatically (DC 3.15.0+). Not all configurations are supported in Cloud; unsupported options (e.g., author/date display) will be ignored.
Overview macro: (report macro in the Cloud app) will require some manual work.
Metadata History is not supported in Cloud.

What happens to hidden fields and blog posts?

Hidden Metadata fields become visible in Cloud. Metadata on blog posts is migrated, but you must manually add a Display Metadata macro to the blog post in Cloud to view the values.

What are the biggest changes compared to Data Center?

In Data Center/server, space-level metadata is a standard feature. In the cloud, direct migration is not supported automatically.
Absence of Metadata History: The ability to track changes to Metadata values, which is available in the Data Center/server version, is not yet present in the cloud app.

Are you a solution partner and have questions about licensing during migration?