Connector for Salesforce & Jira feature differences for Jira DC and Cloud

Connector for Salesforce & Jira feature differences for Jira DC and Cloud

Last updated onOct 27, 2026.

Migration Focus Area

Feature

Platform

Server/Data Center

Cloud

Versioning/License

Version Support

Min Upgradable Jira version - click the link to determine if your Jira version is still supported

Migrate to NextGen Cloud using steps at Migration Path.

License

Available through Atlassian Marketplace.

Available through Atlassian Marketplace only. Monthly subscriptions are the default option. However, discounted annual subscriptions are available upon request to our Atlassian Sales team.

Jira Differences

Jira data

All related features from Server/Data Center migrating to the cloud will depend on the JCMA and Atlassian Jira migration support.

Please review 

Jira integration user

In a migration scenario, an integration user must first be set up on the Jira Server or Data Center. This is a prerequisite for the migration process. Refer to Set up an integration user - Connector for Salesforce & Jira for steps on how to set up this user.

There is no need to set up an integration user on Cloud.

Feature parity

Features

DC

Cloud

Notes

Features

DC

Cloud

Notes

Connectors configuration in Jira

  • Binding projects to a connection

:check_mark:

:check_mark:

 

  • Setting connection to Salesforce

:check_mark:

:check_mark:

In Jira DC you need to set up an integration user before setting up a connection.

Connectors configuration in Salesforce

:check_mark:

:check_mark:

 

  • Setting connection to Jira

:check_mark:

:check_mark:

Based on your Jira environment, you need to add different Remote Sites:

Jira Data Center: Add a Remote Site for your Jira instance URL

Jira Cloud: Add Remote Sites for:

Synchronization

Mapping templates

:cross_mark:

:check_mark:

Mapping templates reference

Entity mapping

:check_mark:

:check_mark:

 

Field mapping

:check_mark:

:check_mark:

 

Value mapping

:check_mark:

:check_mark:

 

Default value mapping

:cross_mark:

:check_mark:

Default value mapping is available only on Jira Cloud.

Sync direction: Manual & auto bi-directional

:check_mark:

:check_mark:

 

Support for custom Salesforce objects

:check_mark:

:check_mark:

 

Create Jira work items

:check_mark:

:check_mark:

Creating Jira work items from Salesforce for the Jira Service Management (JSM) projects is supported only for Jira Cloud.

Create Salesforce records

:check_mark:

:check_mark:

 

Get updates from Salesforce

:check_mark:

:check_mark:

 

Get updates from Jira

:check_mark:

:check_mark:

 

Send updates to Salesforce

:check_mark:

:check_mark:

 

Send updates to Jira

:check_mark:

:check_mark:

 

View Jira comments in Salesforce

:check_mark:

:check_mark:

 

View Salesforce comments in Jira

:check_mark:

:check_mark:

 

Push and pull attachments

:check_mark:

:check_mark:

 

Chatter Support

:check_mark:

:check_mark:

 

JQL functions

:check_mark:

:check_mark:

 

Reporting

:check_mark:

:check_mark:

 

Search page

:check_mark:

:check_mark:

 

Post functions

Push to Salesforce post function

:check_mark:

:check_mark:

 

Create Salesforce object post function

:check_mark:

:check_mark:

 

Automate your integration

Automatic Jira work item creation and push updates with Salesforce Flow Builder

:cross_mark:

:check_mark:

Triggers for Cloud and Jira DC differ Automate Jira actions with Salesforce Flow Builder

Automatic Jira work item creation and push updates

:check_mark:

:check_mark:

Triggers for Cloud and Jira DC differ Automatic Jira Issue Creation and Push Updates in the same trigger

Configure automatic pull from Salesforce

:check_mark:

:check_mark:

Triggers for Cloud and Jira DC differ Configure Automatic Pull from Salesforce

Associate Jira work item with Salesforce records and trigger post actions

:check_mark:

:check_mark:

Triggers for Cloud and Jira DC differ Associate Jira work item with Salesforce records and trigger post actions automatically

Trigger code when an association is unlinked

:check_mark:

:check_mark:

Triggers for Cloud and Jira DC differ Trigger code when an association is unlinked

Associating

Associate Jira issues

:check_mark:

:check_mark:

 

Associate Salesforce records

:check_mark:

:check_mark:

 

Bulk association

:cross_mark:

:check_mark:

Bulk associate available in Cloud.

Run the association report

:check_mark:

:check_mark:

 

REST API

:check_mark:

:check_mark:

Cloud version and DC version APIs are different. Check the documentation for details:

Notifications

Email notifications to Salesforce users

 

:check_mark:

:check_mark:

 

Email notifications to Jira users

:check_mark:

:check_mark:

 

Salesforce features support

Visualforce

:check_mark:

:check_mark:

 

Lightning UI

:check_mark:

:check_mark:

 

NextGen

:check_mark:

:check_mark:

 

Integration

Time to SLA integration

:cross_mark:

:check_mark:

Set up Time to SLA integration