Migrating to Jira Cloud
Looking to migrate to Jira Cloud? Check out our complete migration guide, or try our suite of Cloud apps directly!
At Elements, we’re fully committed to making your move from Data Center to Cloud as smooth and successful as possible.
Most of the key capabilities available in Elements Copy & Sync for Data Center are also available in our Cloud app. And because Jira Cloud works differently from Jira Data Center, we’ve redesigned and improved parts of the experience, making the Cloud version simpler to set up and easier to use day to day.
We want to make sure your migration goes smoothly and to help you get the most out of Elements Copy & Sync in Jira Cloud.
A Cloud app for each of your needs
Depending on how you use Copy & Sync on Data Center, you may want to explore where your favorite features are available in Jira Cloud.
Elements Copy & Sync
The Cloud version of Copy & Sync will let you clone and synchronize fields, comments, attachments, and statuses between issues. Rediscover your operations and fields mapping through powerful new recipes.
Elements Overview
Copy & Sync data panels are the best way to get a glimpse of relevant information from related issues. In Jira Cloud, you will discover many new ways to display that data thanks to Elements Overview, our dedicated solution.
Elements Publish
If you are currently using Confluence operations to create pages from Jira issues to streamline your information flow, you will love all the new options available to you in Elements Publish, our dedicated Cloud app.
Migration path
Manual migration
Steps to follow to migrate from Jira Data Center to Jira Cloud:
Verify that all the needed features exist on Jira Cloud (see the tables below)
Install Elements Copy & Sync on your Jira Cloud instance
Manually create the recipes
If you have any doubt or question, contact our support team. We'll assist you in your migration.
Attaching your Support dump file to your request will reduce the support time.
To extract your dump file:
Go to your Data Center instance and on Elements Copy & Sync
Click on Administration and Backup

Migration with JCMA
Copy & Sync is compatible with Atlassian’s Jira Cloud Migration Assistant (JCMA) for performing app-migrations. This means that you’ll be able to automatically migrate most of your Copy & Sync Operations and Synchronizations from your Server instance to your Cloud instance.
You can find more information about to perform an app migration with JCMA here.
Difference between Server/Data Center and Cloud
Note that, as we redesigned our Copy & Sync application when we developed it for the Cloud to make it easier to use, the operating logic is different compared to the Server/Data Center version.
We will adapt your configuration during migration to keep as much consistency as possible, but we encourage you to verify your newly migrated recipes and readjust them according to your needs.
Again, if you have any doubt or question, contact our support team. We'll assist you in your migration.
When performing a migration with JCMA, your Operations, Synchronizations, Fields Mapping and Data Panels will be modified, here are the main differences between the Server/Data Center and Cloud versions:
Server/Data Center | Cloud | |
|---|---|---|
Operations | will become | |
Synchronizations | will become | |
Fields Mapping | will be configured | in each Copy & Sync or Synchronization recipe |
Data Panels | available as separate app | Data Panels are available on Cloud as a stand-alone app: Elements Overview (see our dedicated migration path) |
Copy to Confluence | available as separate app | This feature is available on Cloud as a stand-alone app: Elements Publish |
Copy to remote instance | will not be automatically migrated | While creating and synchronizing issues on remote instances is indeed supported in the Cloud version of Copy & Sync, the way instances are linked to one another has been reworked and is not compatible with how it is done on Data Center. Thus, such operations cannot be automatically migrated to Cloud and will need to be recreated manually. |
Velocity | is not supported | Your code will be copied but will not be functional |
During the migration, you will see warnings about Data Panels, Copy to Confluence and Copy to remote instances as below.

This is just for information, you can "Continue without resolving warnings" in the next step and complete your migration if the warnings only concern Copy & Sync.

Features comparison with Jira Data Center
This section lists the implementation status of Elements Copy & Sync main features in Jira Cloud.
Cloud features
Below, you’ll find an overview of Server/Data Center features and their availability in the Cloud version. Beyond feature parity, our Cloud app also unlocks additional capabilities designed to give you more flexibility, visibility, and control, including:
These enhancements make it even easier to manage complex operations and scale your processes in Jira Cloud. To discover everything you can achieve with Elements Copy & Sync on Cloud, explore our Cloud documentation.
Copy
Feature | Cloud availability | Comments |
|---|---|---|
Copy issues manually from issue view |
| |
Copy issue during post-function |
| |
Copy Jira native fields |
| |
Copy custom fields |
| Check the list of supported Custom Fields. |
Copy comments |
| |
Display comment origin |
| |
Copy comments in parent issue |
| |
Copy comments in child issue issue |
| |
Copy attachments |
| |
Copy to remote Jira instances |
| |
Automatic linking |
| |
Copy linked issues |
| |
Copy external links |
| |
Copy subtasks |
| |
Create multiple issues at once |
| |
Copy to Confluence |
| This feature is available on Cloud as a stand-alone app: Elements Publish |
Copy restricted to specific users |
|
Synchronization
Feature | Cloud availability | Comments |
|---|---|---|
Synchronization of fields updates |
| |
Synchronization of new comments |
| You can't exclude users, only groups and comment types |
Synchronization of comments edits |
| |
Synchronization of comments deletions |
| |
Display comment origin |
| |
Post as original comment's author |
| |
Post comment as a specific user |
| |
Synchronization author (Sync on behalf of) |
| |
Synchronization of new attachments |
| |
Synchronization of attachments deletions |
| |
Synchronize issues created by Copy & Sync |
| |
Synchronize issues created manually |
| |
Synchronization chaining |
| |
Trigger synchronization on link creation |
| |
Mapping issue type |
| |
Synchronize between remote Jira instances |
| Available if the target work item has been created with Copy & Sync app |
Other features
Feature | Implementation status | Comment |
|---|---|---|
Map fields to other fields |
| Mapping to be done individually for each recipe |
Set static default values to fields |
| |
Advanced values in Fields Mapping |
| Copy & Sync Cloud doesn't handle Velocity. Your code will be copied as a dynamic value but will not be functional. |
Data Panels |
| This feature is available on Cloud as a stand-alone app: Elements Overview (see our dedicated migration path) |
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.