tldr: Is there a list / table of which Atlassian Legacy macros are converted into Atlassian Cloud macros / elements, during a Legacy editor to Cloud editor conversion.
eg. Panel macro >>> Panel element
And what happens to incompatible data.
-------------
We are preparing our migration from Server to Cloud, and have done a test run. In that run, we tested some pages being converted from the Legacy editor to the Cloud editor.
The conversion was... erratic, with some macros being converted, and some left with a Legacy wrapper. Understandable. In our case we extensively use nested Panel macros for formatting.
But, SOME elements DID get converted to Cloud macros. For instance, a few items got converted to a Cloud panel element.
But we couldn't quite work out which panels got chosen to convert.
Currently we are considering un-nesting all the Panels using the Server API, replacing them with an element before the body of the panel, and an element after the body of the panel.
In order to keep nicer formating, we are using a Panel macro as a section header, with the contents being the title of the Legacy panel.
Now, when we come to convert from Legacy to Cloud editor, what is that Panel going to be converted into?
And indeed all the other Atlassian macros.
If we are preparing the server pages for transfer, it would make all the sense in the world to convert to macros / elements that can be easily converted to the Cloud Editor.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.