HTML macro (Confluence Server) to iFrame macro (Confluence Cloud) - migration plan

Question

Our organization has been using the HTML macro in Confluence Server for many years as a way of embedding <iframe> content. When we migrate to Confluence Cloud next year, users will be able to use the iFrame macro for this use case.

In preparation for this migration, is there a way to ready the content so it will not break when it migrates? The iFrame macro doesn't exist in Confluence Server, so we can't ask users to update their pages in advance. It seems that they will need to wait until content is migrated, find all the places that display "uknown macro: html", and then change this to the iFrame macro.

Any ideas/suggestions are welcome!

unknown · Answer

Hi,

We have documented HTML Macro migration to Cloud, specifically for our app HTML Macro for Confluence here:

Migrate Confluence HTML Macro from Server or DC to Cloud

Feel free to reach out to our support if you have further questions.

Clark Everson · Answer

Hi Joe,

if you click the article I attacked it specifies

Platform Notice: Server and Data Center Only - This article only applies to Atlassian products on the server and data center platforms

So the article I sent was for data center. If it’s not working for your instance then it maybe not turned on and I’d recommend you look at your plugins to see why.

looking at cloud documentation they have now added it but the one I sent was for data center specifically.

clark

Joe Doherty_4iz6b0 · Answer

@Clark Everson - I only see the iFrame macro available in Cloud, not in Server/DC.

What I'm trying to do is replace the HMTL macro that users have been using to embed iFrames in Server (users have been following the steps you shared in the KB article).

We eventually want users to use the native iFrame macro in Cloud, but I'm looking for a way that we can update pages in advance of the migration so that all the HTML macros don't just show up as "unknown macro".

Short of finding/buying a 3rd party app that supports both Server/Cloud (and will migrate smoothly), it just doesn't seem there are any Atlassian-based solutions for this problem (unless I'm missing something).