Currently, when exporting legacy pages and their eligibility status for migration to the new Confluence editor, the report only indicates whether an entire page is supported or unsupported. There is no way to identify which specific content elements on a page are unsupported. This makes it difficult to efficiently target and correct only the problematic content before migration.

It would be extremely helpful to have a feature that allows admins or users to:

• Identify and highlight unsupported content elements within legacy pages.
• Export a report or view that details which specific macros, formatting, or content blocks are not supported by the new editor.
• Use this information to focus remediation efforts and streamline the migration process.

This enhancement would significantly improve the migration workflow by narrowing down what needs correction, saving time and reducing manual review.