Issue Summary

After migrating from Confluence Server/Data Center to Confluence Cloud, some pages contain XML-like or structured text that was originally stored inside rich-text macros, such as the Info macro.

This content may include:

• indentation / tab-style spacing

• XML-like structured text

• bold, italic, strikethrough, colors

• links

• embedded Jira macros or inline references

In Confluence Cloud, there does not appear to be a native macro that supports both:

1. preserving tab stops / indentation for structured text, and

1. allowing rich-text formatting inside the same block.

The closest native option is the Code Block / Code Snippet macro, but it treats the content as code/plain text and does not support rich-text formatting inside the snippet

Steps to Reproduce

1. In Confluence Server/Data Center, create a page.

1. Add an Info macro or similar rich-text macro.

1. Inside the macro, add XML-like structured content with indentation/tab-style spacing.

1. Apply rich-text formatting to parts of the content, such as bold, italic, strikethrough, or color.

1. Add Jira issue macros or inline links within the same content block.

1. Migrate the page to Confluence Cloud.

1. Open the migrated page in Confluence Cloud.

1. Try to recreate or remediate the same layout using native Confluence Cloud macros.

Expected Results

Confluence Cloud should provide a native macro or editor capability that allows users to:

• preserve tab stops / indentation / structured spacing for XML-like or code-like content

• apply rich-text formatting such as bold, italic, strikethrough, colors, and links

• optionally reference Jira issues or other inline elements

• render the content consistently after Server/Data Center to Cloud migration

Actual Results

Confluence Cloud does not provide a native macro that fully supports this content model.

Available options only partially meet the requirement:

• Code Block / Code Snippet macro preserves structured text and indentation better, but does not support rich-text formatting or embedded macros inside the code content.

• Info/Panel-style macros support rich text, but are not designed to reliably preserve XML/code-like indentation or tab-stop formatting.

As a result, migrated content may need to be manually restructured, and customers lose the ability to represent structured text with both indentation and rich formatting in a single native macro.

Workaround

Option 1: Restructure the content using Code Block / Code Snippet

Use a Code Block / Code Snippet macro for the XML or structured text section, and move rich-text comments, Jira issue links/macros, and explanatory notes outside the code block.

Recommended structure:

• Use the Info macro for descriptive or explanatory text.

• Use the Code Block / Code Snippet macro for the XML content.

• Place Jira references and formatted notes before or after the code block rather than inline within the XML.

This preserves the XML structure, but it does not provide full parity with the original Server/Data Center rich-text layout.

Option 2: Revert to a legacy-editor version, where available

If the page was previously converted from the legacy editor and the option is still available on the customer’s site, the customer may be able to restore the version before conversion:

1. Open the affected page.

1. Select More actions (…).

1. Select Version history.

1. Find the version before the page was converted to the new/cloud editor.

• • The conversion version may have a comment similar to:
    “Version published after converting to the new editor”

1. Select Restore on the version before conversion.

1. Review the page and validate the formatting.

Important notes:

• This is only a temporary workaround where legacy-editor restore is still supported.

• Any changes made after the restored version may be lost and should be reviewed before restoring.

• Pages created directly in the Cloud editor cannot be reverted to the legacy editor.

• This does not replace the need for a long-term Cloud-native solution.