...
Because Refined Sites Cloud works as a site builder parallel to native Confluence, the app doesn’t change native Confluence. Therefore, Refined Sites doesn’t impact third party apps that provide functionalities in native Confluence such as apps for document management.
If a macro you use on Server/DC is not supported on Cloud, remove it from your pages and find a workaround. If you use a critical third party macro that we don’t support on Cloud, please reach out to us: migration assistance.
Team Calendars are not supported due to Atlassian API limitations. Click here to view the issue and vote on it.
If a third-party macro isn’t supported on Cloud, watch this video for a workaround:
...
Step 5. Set up a rollout plan
...
Refined Toolkit for Confluence Server/DC | Refined Toolkit for |
---|---|
| |
| |
Turns into a Child Pages macro with the cards display mode. | |
| |
| |
| |
| |
|
...
When you migrate to Cloud, you edit your pages in Confluence Cloud’s legacy editor. This editor is similar to the one you're used to from Server/DC. While Atlassian recommends you to convert your pages to the new editor, and Refined sites don’t offer full support for pages in the old editor either.
However, this may pose problems with some of your migrated macros. On Server/DC it is possible to nest macros which contain content within one another. These are called bodied macros. This is essential to the functioning of some macros: for example, you place content in a Step macro within a Step Container macro.
...