At Elements, we're fully committed to making your path from Server / Data Center to Cloud as seamless as possible.

We're working hard to ensure that in the coming months the value you can get from the Cloud version of Elements Connect matches and even exceeds the one you currently get with our Server / Data Center app.
While this is our long term goal, we know that today there's a gap in functionality between our Server / Data Center product and our Cloud app.
Most of the key functionalities of the Server / Data Center app will be implemented, however, due to functional differences between the Cloud and Server/Data Center platforms (listed as "not possible" on the tables below), we are not able to deliver 1:1 feature parity between the environments.

Rest assured, the Elements team is working hard to ensure our Elements Connect Server/Data Center users find similar functionality in Cloud and enjoy an excellent experience with our Cloud app.

Migration path

Here are the key steps to follow to successfully migrate your Elements Connect configuration from Jira Server/Data Center to Jira Cloud: 

  1. First, verify that all the features you need exist on Jira Cloud  (see the table below)
    It is important for to be aware of the feature parity between the hosting environments. Some of your configuration may not yet be available, or you need to implement another solution to achieve the same that you have done in your Jira Server / Data Center environment.
  2. Install Elements Connect on your Jira Cloud instance.
    We recommend you take some time to evaluate the Cloud app to get a better understanding of how it works. 

  3. Manually create your configuration (datasources and connected items) in Elements Connect for Jira Cloud

  4. Export connected fields values from Jira Server/Data Center to CSV
    • On your Server / Data Center instance, create as many Jira Text Custom fields as you have Elements Connect fields
      (lightbulb) For multiple fields, create Jira Text Area Custom fields.
    • For each workflow linked to an issue associated with an Elements Connect Custom Field, add a global transition with our post-function "Copy field display to another field"
    • Configure as many post-functions as needed in order to have a 1-to-1 mapping between Elements Connect Custom Fields and Jira Text Custom fields
    • Use a Bulk operation to execute the previous transition on all the relevant issues 
      We recommend that you verify that all Elements Connect Custom Fields have their display value copied in their dedicated Jira Text Custom Field.
    • Export your Jira tickets using the CSV exporter - the CSV file generated will be used to import your data in the next step.

      Some specificities to take into account

      HTML in display template

      For every Elements Connect custom fields using HTML/CSS in the display template, make sure there are no reference to HTML/CSS in the CSV document:

      • Edit the display template for each Elements Connect custom fields and remove HTML/CSS references
      • Make sure there are no HTML/CSS references directly in the CSV file

      User type fields

      For Elements Connect User type custom fields, use the "Copy field key to another field" post-function. You will copy the user's username in the text field.

  5. Finally, import the previously generated CSV file in Jira Cloud
    • On your Jira Cloud instance, create as many Jira Text Custom fields as previously created on Server/Data Center
    • Import the CSV file 

Current limitations

After this migration, Server/Data Center data will be available on Cloud. However, it will not be updated by newly configured Connected Items but it can be used for reporting.

We're here to help

We’re committed to making your migration to Elements Connect for Jira Cloud as smooth as possible, don’t hesitate to contact our support team should you have any question or concern. We recommend that you attach your support dump file to your support request, it'll help our team provide more accurate answers about your specific case.

Implementation status

This section lists the implementation status in Jira Cloud of Elements Connect main features.


Need a datasource not listed below? Tell us more about it.

FeaturesImplementation statusComment
SQL Databases

(warning) Partial availability

Databases supported (tick)

  • Microsoft Azure SQL Database
  • Microsoft SQL Server
  • MySQL
  • Oracle Database (Service identification)
  • PostgreSQL

Related change requests (info)

ECJC-38 - Getting issue details... STATUS

ECJC-10 - Getting issue details... STATUS  (for other Oracle Database identification types)

Jira JQL(error) Unavailable

ECJC-41 - Getting issue details... STATUS

Jira REST(error) Unavailable

ECJC-34 - Getting issue details... STATUS

LDAP(error) Unavailable

ECJC-39 - Getting issue details... STATUS

ECJC-3 - Getting issue details... STATUS

REST APIs (URL)(error) Unavailable

ECJC-30 - Getting issue details... STATUS


(error) Unavailable

ECJC-2 - Getting issue details... STATUS

Zendesk(error) Unavailable
Files(error) Unavailable
Jira SQL(minus) Not possibleAtlassian does not give access to Jira database on Cloud.

Field types

Field typeImplementation status
Live text(error) Unavailable
Live user(error) Unavailable
Snapshot text(tick) Available
Snapshot date(error) Unavailable
Snapshot date time(error) Unavailable

Field editors


(tick) Available

Read only(tick) Available
Select list(error) Unavailable
Cascading select list(error) Unavailable
Table(error) Unavailable
Checklist(error) Unavailable
Radio button(error) Unavailable


DependencyIntegration StatusComment
Project(error) Unavailable

ECJC-18 - Getting issue details... STATUS

User field(error) Unavailable

ECJC-5 - Getting issue details... STATUS

Issue type(error) Unavailable

ECJC-19 - Getting issue details... STATUS

Text custom field(error) Unavailable

ECJC-56 - Getting issue details... STATUS

Current User object(warning) Partial availability

ECJC-54 - Getting issue details... STATUS

Some dependencies with the current user exist

Current issue key(error) Unavailable

ECJC-49 - Getting issue details... STATUS

Reporter's organization(error) Unavailable

ECJC-33 - Getting issue details... STATUS

Jira integration

Set value from Jira Service Management portal(tick) Available
Set value from Jira create/edit issue screens(minus) Not possibleJira does not allow apps to extend the Create / Edit issue screens
Edit from issue view

(tick) Available

Edition is done in the issue view

JQL search

(warning) Partial availability

Search is done on the mirror field
Use Connected items in Jira Dashboards(warning) Partial availability
The mirror field can be displayed in some dashboard charts
Post function: Set value(error) Unavailable

ECJC-46 - Getting issue details... STATUS

Post function: Copy value(error) Unavailable

Advanced field options

Dynamic query(warning) Partial availabilityDynamic queries can be configured
Edit queries & template(error) Unavailable
Search query & template(error) Unavailable
Cache(error) Unavailable
Sort results(error) Unavailable
Filter results(error) Unavailable


REST API(error) Unavailable
Java API(minus) Not possibleElements Connect code is running outside of your Jira instance, in our own servers. Therefore, you can't access Elements Connect Java API from your own scripts.
The recommended way will be to use Elements Connect REST API when it will be available.

More resources to help you plan your migration 

Atlassian has published a dedicated Migration Resource Center with step-by-step guides, free tools, and dedicated support to assist you on your journey to Cloud.

Have specific questions about our app? Please reach out to our support team - they're here to help and advise.