Versions Compared

Version Old Version 5 New Version Current
Changes made by

Madzy Soetman

Madzy Soetman

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Before starting your actual migration, we recommend prepare using the following resources:

Table of Contents
stylenone

...

  • You can create as many sites as you want. What content can you split out into multiple sites?

  • You can add a space to as many sites as you want. What content can be relevant to include on multiple sites?

  • It’s easy to combine both JSM portals and Confluence spaces into one Refined site, if you get both Refined Sites for Confluence Cloud and Refined Sites for Jira Service Management Cloud. Could this improve your workflow and your site’s user experience? It opens up many new ways of using Refined Sites, including:

    • Building an intranet that features Confluence pages and blogs, as well as JSM portals. For example, this makes it easy for users to explore the company’s employee handbook and directly contact HR if they have any questions.

    • Creating an external-facing help site that features not just Confluence spaces, but also help desks. This way, users can create support requests if they can’t find what they are looking for.

...

Step 3. Prepare your base Confluence spaces (and JSM projects)

...

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
Confluence Cloud

UI Button

Button

  • Supported settings: Title, URL, Tooltip, Size, and Color.

  • Unsupported settings: Icon, Display, Open in a new window

  • It’s not possible to set custom color profiles on Cloud.

  • URLs are static. If they link to local pages and blog posts in Server/DC, you need to manually change the link to the new URL in Cloud.

UI Children

Child Pages

  • Supported setting: Page

  • Unsupported settings: Display, Columns, Sort children by, Reverse sort

UI Children Cards

Turns into a Child Pages macro with the cards display mode.

UI Expand(s)

Expand (Container)

  • Supports the same settings as on Server/DC

UI Image

  • Images are migrated if you have Refined Toolkit Cloud, but they are not editable. To add images in Cloud, simply insert them in the Confluence Editor.

UI Step(s)

Step (Container)

  • Unsupported setting: Size

UI Tab(s)

Tab (Container)

  • Supports the same settings as on Server/DC

UI Text Box

Panel

  • Supported setting: Type

  • Unsupported settings: Text size, Show icon

  • It’s not possible to set custom color profiles on Cloud.

...

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.

...