Issues faced during the macro naming conversion of HTML for Confluence App during the pre-migration process

Overview

As part of the migration to the Confluence Cloud, you may need to perform a macro naming conversion for the HTML for Confluence app, as outlined in this document.

This article addresses the concerns regarding macro conversion during the pre-migration process for the HTML for Confluence add-on.

Description

The naming conversion of macros ensures compatibility and consistency between the macros in both the on-premises and cloud environments. Below are a few common questions and answers related to this conversion:

Can I safely run the macro naming conversion for HTML for Confluence during migration? Will the macros still work on my on-premise server after renaming?

Yes, you can safely run the macro naming conversion at any time. The macros will function as expected on the on-premises site even after renaming them.

What happens if new macros are added after conversion? (If I convert pages and someone adds a new macro after conversion, will it be included in the subsequent conversions?)

If new macros are added after the initial conversion, you must rerun the macro naming conversion before the migration process to update their names. This ensures consistency across all macros in the migration process.