Page Comparison

This article contains information about migrating HTML macro content from server to cloud. For existing customers, migrating the HTML macro content to cloud was not available due to certain Atlassian Confluence cloud limitations on the HTML macro name. Due to these restrictions  Due to restrictions in Confluence cloud, the HTML macro name was changed to HTML-bobswift, and Migration to Confluence Cloud  in HTML for Confluence Configuration allows you to initiate a process that automatically updates the macro name to prepare your content for migration. Once this process is completed, administrators must can then run the Confluence Cloud Migration Assistant to migrate all your content to Confluence cloud.

Issues about mismatching HTML macro names are thus resolved, and administrators can complete their migration process from server to cloud without any HTML content display issues. This article contains the relevant information required to make a seamless transition of HTML content from server to cloud.

...

The instructions are divided into two parts: understand how many pages and/or templates need updates, and run the actual updation processupdate process. The first part merely allows administrators to keep a check on any errors or mismatches in the number of updates made in the second part.

...

1. Select  > Manage apps.

2. Either search for HTML for Confluence or scroll to Bob Swift Configuration, and click HTML to view app configuration. 

   Tip
   title Try this for older Confluence versions!
   Navigate to CONFLUENCE ADMINISTRATION > Settings > ATLASSIAN MARKETPLACE > HTML.

   This opens the HTML for Confluence Configuration page.
   
   

3. Select Migration Migrate to Confluence Cloud. This tab displays some information about the macro name update process.
   Image Added
   
4. Click Macro upgrade status to know more about the HTML macro usage in your instance similar to the following screenshot:
   Image Removed. Until the previous release, these statistics were shown directly before the next step.                                                                                                                           Image Added

5. Click Update pages to start the updation process. 

   Note
   Leaving this page does not disrupt the update process as it runs in the background. This process can be run as required needed to migrate macro name in the pages and templates. Every page or template that is processed shows up as an update in Page history.

   Image Added

   
   

6. After the update process is completed, the macro usage information on the page is updated and these updates can be verified through the Macro usage page as mentioned in the previous section.