Issue Summary:

When converting legacy Confluence pages containing a Forge macro (Numbered Heading macro, for example) which is nested inside another macro (Expand, for example) to the cloud editor, any content wrapped within the macro may be deleted.

This issue disproportionately impacts migrated customers because pages haven't been converted yet and the cloud macro has been updated to Forge.

Steps to Reproduce:

1. Open a legacy Confluence page that contains the Numbered Heading macro nested inside another macro (ca be the native Expand macro, for example)
2. Attempt to convert the page to the cloud editor.
3. Observe that after conversion, the content previously wrapped by the macro is missing (deleted).

Expected Results:

All content inside the Forge macro should be preserved after converting the page to the cloud editor.

Actual Results:

Content that was wrapped within the Forge macro is deleted during the conversion process.

Workaround:

There is no known workaround at the moment.