---
title: "Migration"
canonical: "https://support.appfire.com/space/HTML/70617038/Migration"
format: markdown
---
> Macro (aura-html)

This page contains details to learn more about the migration process from Data Center (DC) to Cloud versions of the app. Before migrating your *HTML for Confluence* app content from the server to the cloud, we recommend reading [this Atlassian article](https://confluence.atlassian.com/cloud/plan-your-cloud-migration-972349846.html) to plan your migration.

<span style="color: #000000">The following sections explain:</span>

- <span style="color: #000000">Migration process</span>
- <span style="color: #000000">[Differences between the server and cloud versions of the app](https://appfire.atlassian.net/wiki/spaces/HTML/pages/2485911588)</span>

## <span style="color: #000000">Migration process</span>

- <u><span style="color: #000000">Confluence instance migration</span></u><span style="color: #000000"> - Use the </span><span style="color: #000000">[Confluence Cloud Migration Assistant](https://marketplace.atlassian.com/apps/1219672/confluence-cloud-migration-assistant?_ga=2.79281814.385750282.1572431071-748161253.1533556773&_gac=1.40698390.1571216476.EAIaIQobChMIsKTIr7Wg5QIVjA4rCh3XxAOtEAAYASAAEgKDgPD_BwE)</span><span style="color: #000000"> app to migrate everything you need from the Confluence server to the Atlassian cloud. </span><span style="color: #000000">[Confluence Cloud Migration Assistant](https://confluence.atlassian.com/cloud/cloud-migration-assistant-for-confluence-973486571.html)</span><span style="color: #000000"> explains in detail the step-by-step procedure to migrate the required content.</span>
- <u><span style="color: #000000">App installation</span></u><span style="color: #000000"> - Install the app from the Marketplace.</span>

> ⚠️ ### On completion of migration from version 5.8.0:
> ⚠️ 
> ⚠️ - <span style="color: #000000">All global configuration and profile data in the Configuration page are transferred from the server instance to the cloud instance as specified in the Cloud Migration Assistant wizard.</span>
> ⚠️ - <span style="color: #000000">If multiple migrations are performed on the same cloud instance, the latest migration takes precedence.</span>
> ⚠️ - <span style="color: #000000">Any subsequent migrations performed on the same cloud instance only add or merge the data, but do not delete any existing data.</span>
> ⚠️ - <span style="color: #000000">Points to note about profile data migration:</span>
> ⚠️   - <span style="color: #000000">For profiles with distinct names on the server/DC and cloud instances, the profiles from both server/DC and cloud instances are combined and listed under </span><span style="color: #000000">***Configuration > Profiles***</span><span style="color: #000000"> as-is.</span>
> ⚠️   - <span style="color: #000000">For profiles with the same name in both server/DC and cloud instances, the profile configurations available on the server/DC overwrites the profile configuration on the cloud instance. Thus, only one copy of the profile configuration, taken from the server/DC, is available on the cloud, and the original configuration details on the cloud are overwritten. </span>
> ⚠️ 
> ⚠️ Consider an example if:
> ⚠️ 
> ⚠️ - Profiles in DC: A, B, and D
> ⚠️ - Profiles in the cloud: A (profile with the same name as in server, and has the same or different configuration), and X
> ⚠️ 
> ⚠️ After the migration is completed, the Configuration page of the cloud instance now contains the A (with configuration details as in server/DC), B, D, and X profiles.

<span style="color: #000000">Administrators, installing the </span><span style="color: #000000">*HTML for Confluence *</span><span style="color: #000000">cloud app for the first time, can begin the installation and configuration process for both macros as given in the </span><span style="color: #000000">[Installation](https://appfire.atlassian.net/wiki/x/_4g1B)</span><span style="color: #000000"> and </span><span style="color: #000000">[Configuration](https://appfire.atlassian.net/wiki/x/iIc1B)</span><span style="color: #000000"> guides.</span>

> ℹ️ <span style="color: #000000">Data migration from server to cloud is independent of app installation or configuration in your cloud instance. We recommend that administrators verify that all data is displayed properly after all processes are completed successfully. Please </span><span style="color: #000000">[report any issues](https://appfire.atlassian.net/wiki/pages/createpage.action?spaceKey=html&title=Help%20and%20support%20-%20Cloud&linkCreation=true&fromPageId=70617038)</span><span style="color: #000000"> immediately after looking through the known problem list.</span>

### <span style="color: #000000">For existing </span><span style="color: #000000">*HTML*</span><span style="color: #000000"> macro content</span>

<span style="color: #000000">Due to restrictions in the Confluence cloud, the </span><span style="color: #000000">*HTML*</span><span style="color: #000000"> macro name was changed to </span><span style="color: #000000">*HTML-bobswift,*</span><span style="color: #000000"> causing HTML content display issues in pages and templates using the </span><span style="color: #000000">*HTML*</span><span style="color: #000000"> macro of the </span><span style="color: #000000">*HTML for Confluence*</span><span style="color: #000000"> app in earlier versions. Since </span><span style="color: #000000">[version 6.0.2](https://appfire.atlassian.net/wiki/spaces/HTML/pages/3470427303)</span><span style="color: #000000">, this macro name update is applied automatically as part of migration, using Forge macro mapping. Administrators no longer need to run a separate pre-migration step before migrating content with the </span><span style="color: #000000">[Confluence Cloud Migration Assistant](https://marketplace.atlassian.com/apps/1219672/confluence-cloud-migration-assistant?hosting=server&tab=overview)</span><span style="color: #000000">.</span>

### <span style="color: #000000">For </span><span style="color: #000000">*XSLT*</span><span style="color: #000000"> macro</span>

<span style="color: #000000">The migration process for this macro is quite straightforward. Administrators must use the Migration Assistant in the Confluence instance to start the migration.</span>

<span style="color: #000000">Use the</span> [Confluence Cloud Migration Assistant](https://marketplace.atlassian.com/apps/1219672/confluence-cloud-migration-assistant?_ga=2.79281814.385750282.1572431071-748161253.1533556773&_gac=1.40698390.1571216476.EAIaIQobChMIsKTIr7Wg5QIVjA4rCh3XxAOtEAAYASAAEgKDgPD_BwE) <span style="color: #000000">app to migrate everything you need from the Confluence server to the Atlassian cloud.</span> [Confluence Cloud Migration Assistant](https://confluence.atlassian.com/cloud/cloud-migration-assistant-for-confluence-973486571.html) <span style="color: #000000">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.</span>

## Known issues and troubleshooting

<span style="color: #000000">There are certain issues that can occur after the migration process is completed. These are listed along with the possible solution for each in the following table:</span>

| **Possible issue** | **Possible solution** |
| --- | --- |
| <span style="color: #000000">Issue rendering Vimeo videos from the </span><span style="color: #000000">*HTML*</span><span style="color: #000000"> macro</span> | <span style="color: #000000">It is recommended to set the </span><span style="color: #000000">*referrerpolicy*</span><span style="color: #000000"> attribute to render the Vimeo video which has the following privacy settings: </span><br><span style="color: #000000">Example video: </span><span style="color: #000000">[https://vimeo.com/manage/679057197/advanced#](https://vimeo.com/manage/679057197/advanced)</span><br><span style="color: #000000">Who can watch it? - Unlisted Specific domains - </span>`appfire.app <iframe src="`<span style="color: #000000">[https://player.vimeo.com/video/679057197?h=d081c826e5%22](https://player.vimeo.com/video/679057197?h=d081c826e5%22)</span>` width="640" height="360" frameborder="0" allow="autoplay; fullscreen; picture-in-picture" referrerpolicy="origin-when-cross-origin" allowfullscreen></iframe> ` |
| <span style="color: #000000">Issue rendering SVG image</span> | <span style="color: #000000">Modify the function call from </span>`makeInteractive()`<span style="color: #000000"> to </span>`window.addEventListener('load', makeInteractive)`<span style="color: #000000">.</span> |

## Open issues

| **Issue** | **Comment** |
| --- | --- |
| HTML content is not shown as-is, or, does not work as expected after migration to cloud.<br>- Unable to apply styles that worked with the server/DC version
- Unable to access content across multiple macros on the same page (worked in server/DC version) | This is a known issue with the Confluence cloud. Due to the cloud architecture, all content is rendered as iframes, thus limiting the macro capabilities after the migration is completed. Refer to this [Atlassian article](https://developer.atlassian.com/cloud/confluence/modules/dynamic-content-macro/#:~:text=A%20Confluence%20macro%20that%20loads,specific%20to%20the%20authenticated%20user) to learn more.<br>Note that the *HTML* macro is a dynamic content macro, and all dynamic content macros render their content in iframes with Confluence cloud. Hence, the macros have little to no ability to interact with any parent controls. |
| <span style="color: #000000">Support template variables in the </span><span style="color: #000000">*HTML*</span><span style="color: #000000"> macro</span> | <span style="color: #000000">This feature is not supported at this point.</span> |
| <span style="color: #000000">*Export Space*</span><span style="color: #000000"> as HTML does not work, limitations from the Atlassian cloud</span> | <span style="color: #000000">Refer to </span>[https://support.atlassian.com/requests/PCS-92505/](#)<span style="color: #000000">[ for details.](#)</span> |
| <span style="color: #000000">HTML contents with </span>`target="_blank"`<span style="color: #000000"> redirection work, but with </span>`target="_top"`<span style="color: #000000"> redirection are failing.</span> | <span style="color: #000000">This is an open issue. Click </span><span style="color: #000000">[https://bobswift.atlassian.net/browse/HTML-697](https://bobswift.atlassian.net/browse/HTML-697)</span><span style="color: #000000"> to know more.</span> |
| Unable to nest a bodied macro (like the *Expand* Macro) into another bodied macro. | <span style="color: #000000">This is an open issue. Click</span><span style="color: #1155cc"> </span><span style="color: #1155cc">[https://jira.atlassian.com/browse/CONFCLOUD-68323](https://jira.atlassian.com/browse/CONFCLOUD-68323)</span><span style="color: #1155cc"> </span><span style="color: #000000">to know more.</span> |
| <span style="color: #221f1f">Macro does not work properly when nested within a </span><span style="color: #000000">*Tab*</span><span style="color: #221f1f">[ or ](https://docs.servicerocket.com/composition/knowledge-base/incompatible-macros-when-nested-within-composition-cloud-s-tab-and-tab-group-macros)</span><span style="color: #000000">*Tab Group*</span><span style="color: #221f1f"> macro.</span> | <span style="color: #000000">Refer to</span><span style="color: #1155cc"> </span><span style="color: #1155cc">[https://docs.servicerocket.com/composition/knowledge-base/incompatible-macros-when-nested-within-composition-cloud-s-tab-and-tab-group-macros](https://docs.servicerocket.com/composition/knowledge-base/incompatible-macros-when-nested-within-composition-cloud-s-tab-and-tab-group-macros)</span><span style="color: #000000"> to learn more.</span> |

## <span style="color: #000000">Problem reporting</span>

<span style="color: #000000">If you experience any problems or behavior changes that are unexpected, refer to</span><span style="color: #091e42"> </span>[Help](https://appfire.atlassian.net/servicedesk/customer/portal/11) <span style="color: #000000">and open a ticket with us. This helps us identify and prioritize fixes and improvements.</span>