This article contains information about the process and checks to be performed before migrating the HTML macro content from server to cloud. 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 can then run the Confluence Cloud Migration Assistant to migrate all your content to Confluence cloud.

This article contains the relevant information required to make a seamless transition of HTML content from server to cloud.

Instructions

The instructions are divided into two parts: understand how many comments, pages and/or templates need updates, and run the actual update 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.

See how many comments, pages and/or templates in your instance require the HTML macro name update

1. Select  > Administration > Macro usage, or search for Macro usage.
2. Scroll down to Bob Swift Atlassian Apps - HTML and see the number of pages mentioned for the html entry.

This is the number of comments, pages and/or templates that require the HTML macro name change.

Before migration:

After migration:

Update the macro name from HTML to HTML-bobswift on all relevant comments, pages and templates in your instance

1. Select  > Manage apps.

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

   Try this for older Confluence versions!

   Navigate to CONFLUENCE ADMINISTRATION > Settings > ATLASSIAN MARKETPLACE > HTML.

   This opens the HTML for Confluence Configuration page.
   
   

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

5. Click Update pages to start the update process. 

   • Leaving this page does not disrupt the update process as it runs in the background.

   • This process can be run as needed to migrate macro name in the comments, pages and templates.

   • Every page or template that is processed shows up as an update in Page history.

   

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. 

Troubleshoot issue

There is a known issue where the pre-migration process stalls when migrating huge loads. If an issue occurs with the migration tool, you can update the database directly as a workaround. Try executing the following queries:

-- This is to pull all the records with given macro it could be html or html-bobswift

SELECT  distinct s.spaceid,s.spacekey 
FROM CONTENT c
JOIN BODYCONTENT bc
	ON c.contentid = bc.contentid
JOIN SPACES s
	ON c.spaceid = s.spaceid
WHERE 
	c.contenttype IN ('PAGE', 'BLOGPOST', 'COMMENT')
	AND bc.body LIKE '%ac:name="html"%';



-- Update html with html-bobswift 

UPDATE bodycontent
SET body = replace(body,'ac:name="html"','ac:name="html-bobswift"') 
WHERE bodycontentid in (
  SELECT bc.bodycontentid
  FROM CONTENT c
  JOIN BODYCONTENT bc
      ON c.contentid = bc.contentid
  WHERE c.contenttype IN ('PAGE', 'BLOGPOST', 'COMMENT')
    AND bc.body LIKE '%ac:name="html"%'
)
;

Refer to this article about updating macros.