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 Step Container 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 bodied 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:

1. In Confluence, go to General Configuration.

2. In the left-hand menu, find the Administration heading and click Macro usage.

3. In the overview, look for the app Refined Toolkit for Confluence.

4. Click these macros to see on which pages they are located:

   • Expand Container (contains Expand macros, which contain bodied content)

   • Tab Container (contains Tab macros, which contain bodied content)

   • Step Container (contains Step macros, which contain bodied content)

5. 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:

1. On the published page, copy the content from the macros.

2. Go into editing mode and convert the page to the new editor.

3. 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.

When you’re ready, get started with our migration guide.