...
| Rw ui tabs macro |
|---|
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. |
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. 
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.  Layout modules Some modules aren’t available on Cloud. They can be replaced with similar modules: 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. |
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.  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. | Themes | Themes can’t be migrated to Cloud, and need to be re-created manually. See step 7 down on this page for instructions. 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 | 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 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. |
Click the Download button to export the site. See step 5 below for instructions on importing and setting up the site on Cloud.  |
Step 5. Import
...
the site
...
| Excerpt |
|---|
| name | Import and set up the site on Cloud |
|---|
|
Go to your Atlassian instance. Click Apps > Refined in the navigation menu. Click the Open Refined button. Click the Import Server or Data Center site button.  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. 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. Let us know what kind of site you’re importing. Upload the file you exported from your Server or Data Center instance. Keep the tab open while the file is uploading.  Click the Continue button. It may take up to 2 hours to create your site. You can close the tab and check back later.  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.
|
...
Make sure you have the following installed:
Refined Sites 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.
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.
Click the Import/Export button > Download latest published version for use on Cloud.
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.
When you're ready, click Download.
Go to the landing page on your Refined Cloud site where you want to use the layout.
Click the … (three dots) > Edit page to open the Page Builder.
Click the Three lines in the top-left > Export/Import page layout.
Upload the layout.
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.
...
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.
Step 6.
...
Themes aren’t migrated and need to be re-created manually using the Theme Editor.
...
Migration completed – 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 Sites for Cloud subscription:
...
Set up the site in Refined Sites 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 Videos, demos & other resources page.
And of course don’t hesitate to contact us:
...
Migration assistance. Our support team is always there to help you with questions before, during or after migration.
...
Read the post-migration guide which includes best practices and tips for user onboarding.