Versions Compared

Old Version 5

changes.mady.by.user Madzy Soetman

Saved on

compared with

New Version Current

changes.mady.by.user Madzy Soetman

Saved on

Key

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

Migration guide

Make sure to read the differences between our
Info
Note

Before starting your migration, it’s essential to understand key differences between Cloud and Server/Data Center. Please make sure you’ve read these pages and prepared your instance:

apps and our preparation guide to get ready for your migration.

Migrating Refined for Jira Service Management (JSM) to Cloud involves the following steps:

Table of Contents
stylenone

Step 1. Migrate JSM to Cloud

Use Atlassian’s Jira Cloud Migration Assistant to migrate your JSM Server/Data Center (DC) instance to Cloud.

Step 2. Install Refined Sites apps on Cloud

Install these apps on your Atlassian Cloud instance:

App

Description

Refined Sites for Jira Service Management Cloud

Required

Required app.

Refined Sites for Confluence Cloud
Optional

Install if you want to integrate Confluence spaces in your Cloud sites, for example to create a help center.

Step 3. Upgrade Refined for Jira Service Management Server/DC

Upgrade Refined for JSM Server/DC to the latest available version. How to upgrade depends on which version you currently use. To check your current version, go to the Confluence Administration > Manage apps.

...

Rw ui tabs macro
Rw tab
titleStart

Don’t make changes to the site and its settings while you follow these steps.

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-20240626-145447.png

Rw tab
titleSet up links

If elements on your site such as modules contain links to pages, you can update them in this step. Most links should work as long as you ran the Atlassian migration assistant before using the Refined migration assistant, and didn’t delete or modify the content afterwards.

We recommend verifying that all links are valid in their cloud instance. If needed, create rules to update multiple links at a time or enter new links manually. For instance, check the URL of /plugins/servlet/desk/portal/11 in Atlassian Cloud and update the path info if needed. This way, you can replace URLs with their cloud equivalents.

image-20240626-145455.png

Rw tab
titleConfigure

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-20240626-145502.png

Layout modules

The Popular Service Projects module, Recent Request Types module, and Knowledge Base module aren’t available on Cloud. Choose how to handle these modules in the export.

Option

Description

Replace unavailable modules when possible

The Popular Service Projects modules and Knowledge Base modules will be migrated as text modules. You can add links to projects or knowledge base articles manually in the Cloud layout. Recent Request Types modules don’t have a viable alternative on Cloud and will be excluded in the export.

Exclude all unavailable modules

The unavailable modules will be excluded 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.

If your site includes categories or links with special view permissions, you’ll see a list. You can download the list as .CSV file, to keep it for future reference.

Option

Description

Keep view permissions

The users or user groups need to exist on Cloud. Otherwise, the export won’t include specific permissions related to them and the category, link, and layout will follow standard Atlassian permissions.

Remove manual view permissions

Standard Atlassian permissions will apply.

Rw tab
titleAssess

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-20240626-145509.png

Feature

Differences between Server/DC and Cloud

Languages

Refined for Cloud doesn’t support fully multilingual sites. However, the language of hard-coded items reflects the setting of the user’s browser language.

It’s not possible to translate text added into modules. You can use section view permissions to show modules in different languages to different user groups.

It’s not possible to translate the names of items in the navigation menu.

Request Types and their descriptions can be translated, based on the project settings in native JSM. The translation is based on the user’s language setting in their Atlassian profile.


To manually build a multilingual site on Cloud, read this guide.

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.

Themes

Themes can’t be migrated to Cloud, and need to be re-created manually. See step 6 further down on this page. Note that 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 and icons

The site logo in the navigation menu won’t be migrated and needs to be set up manually on Cloud.

Project icons, link icons, and category icons aren’t supported on Cloud sites.

Request view

The settings Layout Mode (request activity on top, request detail on top) and List Attachment don’t exist on Cloud.

On Cloud, the request details are always shown at the top of the request view and attachments are always visible to the side.

Service Level Agreements (SLAs)

Cloud sites don’t display Service Level Agreements (SLAs) in the request view.

Default request type

Cloud sites don’t support showing a default request type. Server/Data Center sites show a default request type when users:

  • Search on your site but there are no search results to show.

  • Aren’t permitted to view a page.

  • End up on a “Content not found” page.

Knowledge base

The Display Articles in Wide Mode settings and Display Article Link settings will be migrated to Cloud. 

The Access to Confluence setting, Display Page Tree setting, and Global Search Settings don’t exist in Cloud.

Read this guide to learn more about setting up a knowledge base on Cloud.

Footer

The footer won’t be migrated, your site will get the default Cloud footer instead.

Rw tab
titleExport 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-20240626-145518.png

...

  1. Make sure you have the following installed:

    • Refined Sites for Jira Service Management Server/DC version 3.6 or newer

    • Jira Server/DC version 8.20 or newer or Jira Service Management Server/DC version 4.20

  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.

    image-20240626-145524.png

     

  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. See the module comparison below.

  5. When you're ready, click Download.

    image-20240626-145529.png

     

  6. Go to the landing page on your 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.

...

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.

Layout Editor modules
Server/DC

Page Builder modules
Cloud

HTML

HTML

Issue Types

Issue Types

Jira Issues

Jira Issues

Knowledge Base

Replace the module with a Text module in the layout that you download, or exclude it altogether. In the Text module, you can manually add links to your Confluence Cloud knowledge base.

My Requests

My Requests

Navigation Cards

Card

Navigation Image

Image

Navigation Icon

Icon

Navigation Content

This module is automatically replaced with an Image module with the Navigation Content style.

Navigation Highlight

This module is automatically replaced with an Image module with the Navigation Highlight style.

Request Types

Request Types

Rich Text

Text

Search Highlight

Search Highlight

Site Navigation

Site Navigation

Popular Service Projects

Replace the module with a Text module in the layout that you download, or exclude it altogether. In the Text module, you can manually add links to projects that you know are most popular.

Recent Request Types

There is no alternative for this module on Cloud, so it won’t be included in the downloaded layout. If you plan to add another module in its place on Cloud, a placeholder can help you see where the module used to be.

...

Step 5: Import and set up the site on Cloud

Insert excerpt
MIGRATECONFCLOUD:Migration guide
MIGRATECONFCLOUD:Migration guide
nameImport and set up the site on Cloud
nopaneltrue

Step 6. Re-create and apply themes

...