Smarter DC-to-Cloud Migration: Metadata for Confluence Now Flags Unmigrated Macros

[#1]

Hello there!

I'm Elena from Elevatic.

Ever finished a Confluence migration only to find pages full of broken macros and zero record of what they used to do?

You're not alone. It's one of the most frustrating parts of moving from Data Center to Cloud, and it's been a gap in Metadata for Confluence, until now.

---

TL;DR Block

Metadata for Confluence Cloud now detects unmigrated Display Metadata and Report macros left over from Data Center and shows an inline migration message directly on the page. Users can see their original DC configuration as static data, making it easy to recreate macros in Cloud without losing any setup details.

---

Migrating from Confluence Data Center to Cloud is a major step, but until now, one frustrating gap remained: pages containing Report and Display Metadata macros from your DC environment would silently lose their configuration, leaving teams to guess what was there before. That changes today.

What Is New in This Release

When a Confluence page contains a Display Metadata macro or a Metadata Overview macro that has not yet been migrated from Data Center, Metadata for Confluence Cloud now displays a clear, inline migration message directly on that page. Instead of a broken or blank macro, users see an informative notice that tells them exactly which macro is missing and, critically, shows their original Data Center configuration as static reference data.

This applies to two macro types covered in this release:

• The Display Metadata macro now surfaces a migration message wherever an unmigrated instance is detected on a page, giving users immediate visibility into what needs to be recreated.
• The Metadata Overview macro receives the same treatment. An inline message appears on any page still carrying an unmigrated version of this macro from your DC environment.

Why This Matters for Your Migration

Anyone who has managed a large-scale Confluence migration knows that metadata and structured content configurations are among the hardest things to carry over. Without visibility into what existed before, teams either had to rely on tribal knowledge, dig through old documentation, or simply start from scratch. None of which are acceptable options when metadata structures underpin governance, compliance, or content workflows.

With this update, the old DC configuration is preserved and surfaced as static data right on the page. That means your team has a reliable reference point to work from when recreating macros in the Cloud environment. No guesswork. No lost configurations. No need to cross-reference spreadsheets or chase down the admin who originally set things up.

This is especially valuable for organizations in the middle of phased migrations, where some users are already on Cloud while pages and content are still being moved over incrementally.

Who Benefits From This Update

This release is directly relevant to any Confluence administrator, space owner, or content manager working through a Data Center to Cloud migration. It is also valuable for end users who notice something looks off on a page and now get an actionable message rather than a silent failure.

If your organization uses Metadata for Confluence to manage structured content, custom fields, or reporting across your Confluence instance, this update ensures that migration does not mean information loss.

Getting Started

This update is available now for Metadata for Confluence Cloud. No additional configuration is required. Migration messages will appear automatically on any page where an unmigrated macro is detected. From there, you can use the static configuration data shown in the message to guide your macro recreation in the Cloud environment.

We continue to invest in making the DC-to-Cloud path as smooth as possible for Metadata for Confluence users. If you have feedback on this feature or run into anything unexpected during your migration, reach out through our support portal.

---

How is this feature working for you?

Your experience shapes what we build next. Share your thoughts — it takes less than one minute.

Give feedback