Confluence has been updated to version 6.15.9

JIRA SERVER JIRA CLOUD JIRA DATACENTER

After the Atlassian announcement about discontinuing support of Jira Server in the future, we received multiple questions on transferring Exalate to Jira Cloud or Jira Data Center. In this article, we describe the possibility of transferring your Exalate to other Jira solutions.

In this Section

Levels of Complexity

Exalate is highly flexible and can be configured in multiple ways. You need to consider how complex your configuration is before deciding where to migrate: to Jira Data Center or to Jira Cloud.

Let's break down the complexity of integrations into three levels:

Level 1Level 2Level 3

There are almost no customizations, except for small adaptations:

  • some standard custom fields
  • statuses
  • comment visibility.
More advanced configuration that is customized to your specific business logic.

Exalate syncs specific fields and is integrated with various add-ons that require access to the services from the add-ons.

Examples of such add-ons:

  • Tempo
  • Insight
  • Big Picture
  • Structure


Where should I transfer?

Jira Data Center

Exalate API is similar both in Jira Server and Jira Data Center because their codebase is also similar.

In general, migrating from Jira Server to Jira Data Center is straightforward, especially for Level 1 and Level 2 configurations. API of external add-ons could be slightly different, which could impact Level 3 configurations.

Jira Cloud

Jira Cloud has a different codebase from Jira Server, which also affects the integration:

  • Exalate API is different in various areas (such as NodeHelper).
  • Exalate interacts with Jira Cloud through a REST API. This limits the capability to retrieve and set information. For example, it is required that all fields are available on the Create and Edit forms.

So, transferring from Jira Server to Jira Cloud requires a thorough review of your Exalate integration. Based on the complexity levels:

  • Level 1 integrations should need a slight adaptation.
  • Level 2 integrations would need detailed testing of all use cases.
  • Level 3 integrations could be impossible, because some add-ons might not be available, or not have an API to integrate with.

Also, Exalate for Jira Cloud is an Atlassian Connect application that runs on its own environment in Exalate Cloud. This means that there could be differences in information security between Exalate for Jira Server and for Jira Cloud.

Migration of existing connections

Next to the transfer of the configuration, rebuilding the existing twins is required.
The Bulk Connect feature can be used in this case.

So assume a Jira Server to Zendesk connection, and the Jira Server is migrated to Jira Cloud.
One of the steps in the migration of the Jira Server data, is to create a csv file which lists for each twin, the zendesk ticket id and the Jira cloud issue key.
Using the bulk connect facility, the relation between the zendesk ticket and the Jira cloud based issue can be recorded,

Professional Services

We also have partners with experience in such projects. This can help you make a decision about where to transfer. Check out the full list of partners here:

https://exalate.com/partners/