...
Note that this page covers how to migrate only Refined Toolkit from Server/Data Center to Cloud.
...
Make sure that you have Refined Toolkit for Confluence Cloud installed on your Confluence Cloud instance.
Follow Atlassian's recommendations on how to move your spaces to Cloud.
After your migration of spaces from Server or Data Center, your Refined Toolkit macros will function on Confluence Cloud based on the below feature comparison table:
| Ui button | ||
|---|---|---|
|
Feature comparison
...
Click here if you are also migrating Refined for Confluence.
We’re here to help you make your Refined Toolkit for Confluence migration as smooth as possible.
| Table of Contents |
|---|
Macro comparison
| Info |
|---|
Macros on Cloud might look and work a bit differently - click the links to read the documentation. |
Server and Data Center | Cloud |
|---|
Notes
News
UI Activity Stream
|
|
|
|
|
|
Turns into a UI Children macro with the cards display mode |
Full support in Cloud.
UI Image
| |
Images are migrated if you have Refined Toolkit Cloud, but they are not editable. To add images in Cloud, |
UI Page Tree
UI Steps
The size parameter is not supported in Cloud
UI Tabs
UI Text Box
Supported parameters in Cloud: type.
Known limitations
...
simply insert them in the Confluence Editor. | |
| |
| |
| |
N/A | |
N/A | |
N/A | |
N/A |
Preparation guide
When you migrate to Cloud, you edit your pages in Confluence Cloud’s legacy editor. This editor is similar to the one you are used to from Server/DC. While Atlassian recommends you to convert your pages to the new editor, 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 Refined Toolkit macros: for example, you place content in a Step macro within a Steps macro.
Due to a Confluence Cloud limitation, it is not possible to nest bodied macros in the new editor on Cloud. So when you convert a page with a nested body macro from the legacy editor to the new editor, the macro becomes uneditable.
To prevent this, we recommend un-nesting bodied macro content before migrating:
In Confluence, go to General Configuration.
In the left-hand menu, find the Administration heading and click Macro usage.
In the overview, look for the app Refined Toolkit for Confluence.
Click these macros to see on which pages they are located:
UI Expands (contain UI Expand macros, which contain bodied content)
UI Tabs (contain UI Tab macros, which contain bodied content)
UI Steps (contain UI Step macros, which contain bodied content)
Take out the content out of each macro and paste it directly on the page. You can re-create the setup after migration, using the Cloud equivalents of these macros.
If you have many nested macros, it’s understandable that you might not have the time to un-nest them all before your migration. In that case, a temporary solution is to migrate as-is, stay in the legacy editor at first, and gradually convert pages to the new editor as needed:
On the published page, copy the content from the macros.
Go into editing mode and convert the page to the new editor.
In the new editor, paste the content back in where the macro used to be.
We are aware that neither option is ideal, and we are in contact with Atlassian to solve this. Note that we do recommend you to move to the new editor over time, despite the hassle of manual updates. Although migrated macros usually show on the legacy editor pages at first (if you have Refined Toolkit installed), they may still break eventually if Atlassian makes changes to the legacy editor.
If this issues affects you, please vote or comment on this ticket.
Migration guide
Install Refined Toolkit on your Confluence Cloud instance.
Use Atlassian’s Confluence Cloud Migration Assistant to migrate your Confluence Server/DC instance to the Cloud.