FAQ

You can still use our Server apps after February 16, 2024. However, we’ll not publish any new versions and we don’t offer support or maintenance. We encourage our Server customers to migrate to Data Center or to Cloud instead, where we will continue to release updates and offer support.

There are pros and cons to each migration path, and which route you take depends on your unique organizational needs. Companies with a large user base, a complex, multi-instance deployment, and rigorous security or data-protection requirements may find a natural home in Data Center. Cloud may appeal to those seeking a low-maintenance, automatically updating option that emphasizes flexibility.

Refined for Confluence Cloud combines key features from Server/DC with the convenience of the cloud, but there are also some notable differences between the two products.

On Server/DC, Refined is added on top of Confluence: when enabled globally, Refined acts as a skin applied to native Confluence. This means that users view, create and edit Confluence spaces, pages, and blogs all through Refined sites.

On Cloud, Refined is a site builder that runs parallel to Confluence. The Refined sites that you build show Confluence pages and blogs, but live outside native Confluence. This means that you create and manage the sites with Refined, and you create and edit Confluence spaces and pages in Confluence. Because we dynamically pull and expose Atlassian content onto a parallel Refined site, all the updates you make in Confluence are instantly reflected on your Refined sites. Note that Confluence space and page permissions are always respected on Refined sites as well.

Because Refined works as a parallel SaaS to native Confluence Cloud:

• Content creators edit in native Confluence. It’s easy to move between Refined and Confluence.

• Native Confluence isn’t changed by Refined, so Refined doesn’t impact third party apps that add Confluence functionalities such as those for document management.

• We don't have control over the (YourCompany).atlassian.net URL, meaning we can't redirect users from a (YourCompany).atlassian.net site to a Refined site.

• It’s easy to combine Confluence and Jira into one Refined site, if you get both the app Refined for Confluence Cloud and the app Refined for Jira Service Management Cloud. For example, this enables you to build an intranet that features team spaces and an HR service desk, or a help site that sports a knowledge base and a support service desk.

See a full feature comparison between Refined for Confluence on Server/DC and on Cloud.

Refined for JSM Cloud combines key features from Server/DC with the convenience of the cloud, but there are also some notable differences between the two products.

On Server/DC, Refined is added on top of Jira: when enabled globally, Refined acts as a skin applied to the JSM help center.

On Cloud, Refined is a site builder that runs parallel to Jira. This means that:

• The Refined sites dynamically pull and expose JSM portals onto a parallel Refined site, so all the changes you make in Jira are instantly reflected on your Refined sites. Users create and view JSM requests on your site. Admins still create and set up the project and request types in native Jira, and if they make a change to a project it is instantly reflected on the Refined site.

• We don't have control over the (YourCompany).atlassian.net URL. This means that we can't redirect users from a (YourCompany).atlassian.net site to a Refined site.

It’s easy to combine Jira and Confluence into one Refined site if you get both the app Refined for Jira Service Management Cloud and the app Refined for Confluence Cloud. This opens up many new ways of using Confluence and Jira – some examples:

• It enables you to build an intranet that features Confluence spaces and JSM service desks, for example to contact HR and IT.

• Similarly, you can create an outside-facing help site that features not only a service desk but also a full-blown knowledge base.

See a full feature comparison between Refined for Jira Service Management on Server/DC and on Cloud.

Due to the differences in infrastructure between Server/DC and Cloud, it’s not possible to do a 1:1 migration from Server/DC to Cloud with the click of a button. It will require some preparation to make sure the migration goes smoothly, and you will need to recreate your Refined sites manually. How long this takes depends on your specific setup.

Of course, we’re here to help you with every step of the way. A good place to start is to read our in-depth preparation guides and migration guides here:

• Refined for Confluence

• Refined for Jira Service Management

We don’t offer migration paths for other apps. This means that you’d need to carry out the Confluence migration from server to cloud as per Atlassian’s migration guide, and then manually set up Refined sites on Cloud.

Themes will not migrate automatically from Server/DC to Cloud. However, it's easy to recreate themes on cloud and apply them to Refined sites, as our Theme Editor works the same on Cloud as it does on Server/DC.

Site structures and layouts will not migrate from Server/DC to Cloud. However, it's easy to build sites on Cloud in our drag-and-drop Site Builder. Our what-you-see-is-what-you-get Page Builder lets you get new layouts up and running in no-time.

Generally, our Cloud apps offer the same or similar features as their Server/DC counterparts. There are, however, some differences. See full feature comparisons here:

• Refined for Confluence

• Refined for Jira Service Management

• Refined Toolkit for Confluence

We support a number of third party apps. However, some macros created by third party apps may not show on Refined sites. Because Refined Cloud works as a site builder parallel to native Confluence/Jira, native Confluence/Jira is not changed by Refined. Therefore:

• Refined doesn’t impact third party apps that provide functionalities in native Confluence such as apps for document management. However, it might impact apps that provide functionalities on Confluence pages such as macros. If you use any critical third party macros on Server/DC and need help transitioning to Cloud, please reach out to us. Request migration assistance

• Refined doesn’t impact third party apps that provide functionalities in native Jira. However, it might impact apps that provide functionalities in the customer-facing portal.

The links on your Confluence pages that direct the reader to another Confluence page will still work. Keep in mind though that the relevant spaces need to be added to your Refined site. If you don’t add the spaces to the site, the links will point to native Confluence instead. If you experience issues please contact our support team.

Just as with Refined for Server/DC, Refined for Cloud allows you to add a custom domain. You can reuse the domain you had for your Server/DC site on your Cloud site. The server URL format is automatically converted to the new Cloud URL format.

It’s currently not possible to choose data residency for apps in the Atlassian Marketplace. Learn more about this in Atlassian's data residency policy.

We are an Atlassian Cloud Security Participant and adhere to Atlassian's security requirements for Cloud applications. Note that we don’t store login credentials or any sensitive user data for Confluence or Jira on our servers.

For more information, read our our Cloud data storage practices documentation. For security-related inquiries, please reach out to our support team. Ask us about privacy and security

Your Atlassian content, such as Confluence pages or JSM requests, is still stored only in Atlassian. Refined fetches this information but does not store or cache it.

The Refined data, such as your theme or the navigation structure, is stored within Refined. Read more about what we store and don’t store in the data storage documentation.

For detailed pricing information, see our listings on the Atlassian Marketplace:

• Refined for Confluence Cloud

• Refined for Jira Service Management

• Refined Toolkit for Confluence Cloud

And the Refined for Confluence and Refined for JSM FAQ.

This is not possible, because the Server/DC and Cloud licenses (both for the base Atlassian apps, and for Marketplace apps such as Refined) are two separate licenses. Therefore, they are paid for separately. You can read more about this in Atlassian’s documentation.

We have opted in for Atlassian’s dual licensing and loyalty discount programs for all our eligible Server/DC apps. Atlassian applies these discounts during the quoting process for migrating customers who meet the eligibility criteria.

In general, Cloud apps have a 30 days trial period. You can evaluate Refined apps from the Marketplace for a longer time, if needed. Atlassian manages licenses and trial extensions of Marketplace apps: raise a ticket with Atlassian support to request an extension.