Before migrating your HTML for Confluence app content from server to cloud, we recommend reading this Atlassian article to plan your migration.
This page explains:
- Migration process
- Differences between the server and cloud version of the app
Administrators, installing the HTML for Confluence cloud app for the first time, can begin the installation and configuration process for both macros as given in the Installation and Configuration guides.
For existing HTML macro content
Due to restrictions in the Confluence cloud, the HTML macro name was changed to HTML-bobswift causing HTML content display issues in pages and templates using the HTML macro of the HTML for Confluence app. For this purpose, an update process is now available in Migrate to Confluence Cloud on the HTML for Confluence Configuration page. This option allows you to initiate a process that automatically updates the macro name to prepare your HTML content for migration. Refer to this article for the HTML macro name update process instructions.
For XSLT macro
The migration process for this macro is quite straightforward. Administrators must use the Migration Assistant in the Confluence instance to start the migration.
Use the Confluence Cloud Migration Assistant app to migrate everything you need from Confluence server to Atlassian cloud. Confluence Cloud Migration Assistant explains in detail the step-by-step procedure to migrate the required content. As mentioned in the previous section, Atlassian does this job for you in most cases.
Differences between server and cloud versions
All the macros available in the server are supported in the cloud version as well. The following table lists the macros' parameters and features that work differently in server and cloud:
Please note that all the other parameters function the same in both the versions of the app.
If you experience any problems or behavior changes that are unexpected, refer to Help and open a ticket with us. This helps us identify and prioritize fixes and improvements.