Page Comparison

We’re here to help you make your migration as smooth as possible.

...

Because Refined works parallel to Confluence Cloud, your sites don’t have to be ready directly after migrating. Users can access native Confluence while you build your Refined sites. This gives you ample time to get feedback and fine-tune the sites before introducing them to your user base.

Migration guide

...

Step 1. Migrate Confluence to Cloud

Use Atlassian’s Confluence Cloud Migration Assistant to migrate your Confluence Server/DC instance to Cloud.

Step 2. Install Refined apps on Cloud

Install these apps on your Atlassian Cloud instance:

...

...

...

...

...

Step

...

3.

...

Upgrade Refined for Confluence Server/DC

Upgrade Refined for Confluence Server/DC to the latest available version. Then, use Atlassian’s Confluence Cloud Migration Assistant to migrate your Confluence Server/DC instance to the Cloud.

Step 3. Create Refined sites and add content

Check out our Get Started guide to learn how to create sites and to move between Confluence and Refined. Then, use the Site Builder to add content and arrange it into a structure that is reflected in the site’s navigation menu. To get help from colleagues, delegate administrator permissions. You can give out permissions for your entire Refined instance or for individuals sites.

Step 4. Manage site settings

Manage the site settings for each of your Refined sites. Some good settings to start with:

• Set up a custom domain for each site.

• Control which kinds of users can access the sites with Site Access Permissions.

• Create a cookie dialog.

• Use space settings to customize the layout and interaction settings of Confluence pages and blog posts.

Step 5. Create and apply themes

Create and apply themes. Note that Refined for Confluence Cloud doesn’t support advanced theming or third party themes.

Step 6. Migrate layouts (landing pages)

To migrate space and category layouts (called landing pages on Cloud)How to upgrade depends on which version you currently use. To check your current version, go to the Confluence Administration > Manage apps.

Step 4. Export a site with the migration assistant

1. Go to the Refined Administration.

2. Go to the Site Builder tab.

3. Toggle on Cloud migration mode and click a site’s Cloud button.

4. Follow the steps in the dialog that opens.

...

Rw ui tabs macro

Rw tab title Start While you follow these steps to migrate the site, don’t make changes to the site and its settings. Info We’ll notify you in the last step of the migration process if someone made changes to the site or settings since you started the migration. If this happens, we recommend closing the dialog and starting the migration process again, to ensure all choices you make are based on the latest version of the site and its settings. Image Added Rw tab title Set up links If elements on your site such as modules contain links to pages, you can update them in this step. Create rules to update multiple links at a time, or enter new links manually. Image Added Rw tab title Configure Configure how you’d like these features to be handled on Cloud. The migration assistant will only show the features that apply to your site. Image Added Layout modules Some modules aren’t available on Cloud. They can be replaced with similar modules: The My Work module will be replaced with an Activity Stream module. It’ll have CQL set up to show Confluence pages the user has worked on. The Search module will be replaced with a Search Highlight module. User Details, Users in Category, and Users modules will be removed. You can create similar user overviews manually with Image and Text modules. The Confluence Content module will be removed. Option Description Replace unavailable modules when possible Unsupported modules that don’t have a viable alternative on Cloud will still be removed. Exclude all unavailable modules The unavailable modules will be removed and left empty in the Cloud layout on Cloud. Info To get more granular control over the modules, you can always migrate layouts individually. Read how to do this under “Migrate single layouts” further down on this page. View permissions on categories and links If your site includes categories or links with manual view permissions, you’ll see a list. You can download the list as .CSV file, to keep it for future reference. Option Description Keep manual view permissions The same users or user groups needs to exist on Cloud. If they don’t, those specific permissions won’t be included in the export: standard Atlassian permissions apply to the category or link. Remove manual view permissions Standard Atlassian permissions will apply. Uncategorized spaces If your site contains uncategorized spaces, you’ll see a list. You can download the list as .CSV file, to keep it for future reference. Option Description Include uncategorized spaces in menu folder Menu folders function similarly to a category. The menu folder will be hidden from the site's navigation menu, but users can still access the spaces through search functionalities and with a direct URL. Exclude uncategorized spaces The uncategorized spaces will still be available in your Confluence instance, but they aren’t included in this Refined site. Archived spaces If your site contains uncategorized spaces, you’ll see a list. You can download the list as .CSV file, to keep it for future reference. Option Description Exclude archived spaces The archived spaces will still be available in your Confluence instance, but not included in this Refined site. Include archived spaces The archived spaces are still included in the navigation menu, but users can’t find them through search functionalities. Rw tab title Assess These settings aren’t available on Cloud or need to be set up manually. Read this information carefully to assess your next steps after migration. Image Added Feature Differences between Server/DC and Cloud Single space sites On Cloud, single space sites don’t exist. All sites are full sites: you’ll see your space in the site navigation menu instead of in the Site Switcher. Site administrators For security reasons, site administrators aren’t included in the export. Reconfigure the site administrator rights on Cloud. The migration assistant will show a list of the current site administrators, which you can download as a .CSV file. Site access permissions By default, migrated sites aren’t available to anonymous users. You can change the site access permission manually on Cloud. Layout module filters The Activity Stream module’s Filter for contributor setting and News module’s Filter for author setting aren’t migrated. These filters need to be set up again on Cloud. Layout section permissions The permission settings Anonymous, Anyone, and Logged in users only (without user groups specified) are migrated. The setting Logged in users only (with user groups specified) isn’t migrated and needs to be set up manually on Cloud. Themes Themes can’t be migrated to Cloud, and need to be re-created manually. Cloud doesn’t support advanced theming or themes made with third party apps. Site switcher Site Switcher settings aren’t migrated. You’ll need to enable and configure it on Cloud after migration. You’ll have same site list for all sites you create. Logos Structure logos, link logos, space logos, and category logos aren’t supported on Cloud sites. The site logo in the navigation menu won’t be migrated and needs to be set up manually in the theme on Cloud. Blog spaces Blog spaces become regular spaces on Cloud. Point users to blog posts with News modules or direct links instead. Users connected to spaces On Server/DC, it’s possible to connect users to spaces. Certain macros can automatically display these users and their roles on pages, user dashboards, and space layouts. On Cloud, it’s not possible to connect users. You can still manually highlight users on landing pages instead, for example by creating an Image module per user. Category administrators Category administrators don’t exist on Cloud. If your site has category administrators, you’ll see a list which you can download as a .CSV file. Custom category modules Blog modules, HTML modules, and Confluence Questions modules don’t exist on Cloud and are therefore not migrated. Users connected to categories On Server and Data Center, it’s possible to connect users to spaces. The Users in Category module can automatically display these users and their roles on on a site or category home. On Cloud, it’s not possible to connect users. You can still manually highlight users on landing pages instead, for example by creating an Image module per user. Categories with custom URL A category with a custom URL is essentially a link with child items. On Cloud, links can’t have child items. How the category with custom URL is migrated to Cloud depends on whether it has child items: If it has child items, it will become a menu folder. The link-on-click is removed, but the child items remain grouped together. If it doesn’t have child items, it will be migrated as a link. Footer The footer won’t be migrated, your site will get the default Cloud footer instead. Rw tab title Export and import Click the Download button to export the site. See step 5 below for instructions on importing and setting up the site on Cloud. Image Added

Step 5. Import and set up the site on Cloud

1. Go to your Atlassian instance.

2. Click Apps > Refined in the navigation menu.

3. Click the Open Refined button.

4. Click the Import Server or Data Center site button.
   

   Image Added

5. Decide what we should call your site in the Refined Administration. This name also shows up in the browser tab for your site’s visitors. 

6. Choose your site’s URL by picking a subdomain: (subdomain).refined.site. While you are welcome to keep this URL, you can also set up a custom domain later.

7. Let us know what kind of site you’re importing.

8. Upload the file you exported from your Server or Data Center instance. Keep the tab open while the file is uploading.
   

   Image Added

   
   

9. Click the Continue button. It may take up to 2 hours to create your site. You can close the tab and check back later.
   

   Image Added

   
   

10. Review your site once it’s ready. You may need to make changes in your setup, depending on your configurations and assessments you made on Server/DC.

Possibility to migrate only single layouts

To get more granular control over the modules, you can always migrate layouts individually, outside of the migration assistant. You can then import these layouts on Cloud, where they are called landing pages.

To migrate a single layout:

1. Make sure you have the following installed:

   • Refined for Confluence Server/DC version 7.4 or newer (if you need to upgrade, see the version 7.4 upgrade instructions).

   • Confluence Server/DC version 7.15 or newer.

2. On your Refined site, go to a site or category home and click the … Three dots in the top right corner > Edit site/category home.

3. Click the Import/Export button > Download latest published version for use on Cloud.
   

   

4. If the layout contains modules that are unavailable on Cloud, a popup will appear. Select if you want to exclude or replace these modules in the Cloud layout. Scroll down for a module comparison.

5. When you're ready, click Download.
   

   

6. Go to the landing page on your Refined Cloud site where you want to use the layout.

7. Click the … (three dots) > Edit page to open the Page Builder.

8. Click the Three lines in the top-left > Export/Import page layout.

9. Upload the layout.

10. Make adjustments if necessary and hit Publish.

Module comparison

Because of technical differences between Cloud and Server/DC, there are some differences between the modules in the Layout Editor (on Server/DC) and the Page Builder (on Cloud). If the layout you export contains modules that are unavailable on Cloud, you can configure how they should be handled in the export.

...

• Button

• Divider

• Page Tree

• Site Navigation

• Spacer

• Text

• Links

• Issue Types (if you also have Refined for Jira Service Management Cloud)

• Jira Issues (if you also have Refined for Jira Service Management Cloud)

• My Requests (if you also have Refined for Jira Service Management Cloud)

• Request Types (if you also have Refined for Jira Service Management Cloud)

Section permissions limitation

What’s next?

Why not transform your Confluence instance into even more sites users love — you can create an unlimited amount of sites with your Refined for Cloud subscription:

• Get started with Refined for Confluence Cloud

• Build an intranet

• Build a help & support site

• Build a documentation site/knowledge base

Need more help?

Have a look at the FAQ and the demos & other resources page.

...