Last updated Jan 20, 2022

Migration to Cloud

While considering migration from Jira Server to Cloud, it is recommended to consider differences in features offered by apps for these hosting types.

When it comes to IssueSYNC features, their offer differs slightly between hosting types:

Feature	Issue Sync Server/Data Center	Issue Sync Cloud
Synchronization of issue fields
Synchronization of comments
Synchronization of attachments
Synchronization of workflows
Synchronization of subtasks
Synchronization of worklogs
Issue Sync dedicated comments tab
Mapping issue types and fields
Configuring display of the remote issue panel
Creating a remote issue manually
Bulk issue creation
JQL to filter out issues to synchronize
JQL for synchronization triggers
One-way and two-way communication	Server-Cloud and Server-Server	Cloud-Server and Cloud-Cloud
Synchronization of internal Jira issues
Broadcast to multiple Jira instances
No admin credential exchange for increased security
Synchronization of only configured elements
Configuring display of original field and workflow names
DMZ, Firewall, Proxy, and SSL support		Additional level of network security, such as VPN, SSL, Proxy, as part of Atlassian Cloud solution.
Compatibility between major versions to improve maintenance
Changes made on behalf of dedicated Technical User	consumes license	doesn’t consume license
Sophisticated Diagnostics with Alerts and Log Browser		although less extensive than on Server/Data Center

When it comes to configuration, it differs significantly between Issue Sync Jira Server/Data Center and Jira Cloud.

For details on Issue Sync Jira Server/Data Center configuration, see Server Documentation.

For details on Issue Sync Jira Cloud configuration, see Cloud documentation.

An important benefit of Issue Sync is synchronisation between hosting types, helpful in swift migration from Server to Cloud.

You can synchronize the following elements between Jira Server and Cloud with Issue Sync: