What happanes to user macros during Could Migration?

Question

This page (https://support.atlassian.com/migration/docs/what-migrates-with-the-confluence-cloud-migration-assistant/) makes the statement regarding user macros:

User Macros: User macros are not migrated currently.

What does that mean in detail? What happens to the macro instance? Deleted? Placeholder? What happens to the macro data/parameters?

Can we develop a Forge App that replaces the user macro, with the result being a somewhat seamless migration? Or is enough data preserved that would could later run a script against the Cloud instance to migrate from a user macro to a Forge App?

We have 1000s of instances of user macros, that will be a royal PITA to manually migrate. I need to understand the scope of the issue.

Bill Bailey_h6wbjj · Answer

After doing a lot of research, there was no easy solution -- you need to try to write replacement macros using forge, but that may not always be possible. And then maybe replace your existing macros with an special character stream to try to replace later in the Cloud.

Bottom line, both products carry the Confluence name, but they are vastly different products. After our analysis, it is basically impossible for us to move to the Cloud version as it has so many missing features, and forced workarounds. You can't even have a custom domain name (unless you like having to use three levels of names) or custom CSS, just basics of any web presence.

Pirkka Palmumäki · Answer

Hi @Bill Bailey !

We are currently in a similar situation. Did you find out yet if you can simply use Forge to "hijack" the user macros?

Bill Bailey_h6wbjj · Answer

Yes, I saw that. But what is not clear to me is whether:

* Macro name is preserved
* Settings and parameters are preserved
* If I create a new macro using Forge with the same name/parameters, will it automatically be substituted for the existing reference

I am trying to figure out how much of a disaster is there around user macros. Our instance has 20+ macros with 5000+ instances -- not a trivial task to replace.