Migrating to Jira Cloud
Most of the key functionalities of the Server / Data Center app are implemented, however, due to functional differences between the Cloud and Server platforms, we changed and improved the operating logic so our Cloud app is easier to use.
The Elements team is working hard to ensure our Elements Copy & Sync Server users find similar functionality in Cloud and enjoy an excellent experience with our Cloud app.
Migration path
Manual migration
Steps to follow to migrate from Jira Server or 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.
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 | Copy & Sync recipes |
| Synchronizations | will become | Synchronization recipes |
| Fields Mapping | will be configured | in each Copy & Sync or Synchronization recipe |
| Data Panels | are not supported | Data Panels are available on Cloud as a stand-alone app: Elements Overview (see our dedicated migration path) |
| Copy to Confluence | is not supported | This feature is available on Cloud as a stand-alone app: Elements Publish |
| Copy to remote instance | is not supported | Your remote Operations and Synchronizations will not be migrated |
| 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 Server / Data Center
This section lists the implementation status of Elements Copy & Sync main features in Jira Cloud.
Cloud features
Here, we listed the Server/Data Center features that are available or not in the Cloud version.
The Cloud version has also some additional features that are not available on Server/Data Center that we didn't list here. You can discover all possibilities reading our Cloud documentation.
Copy
| Feature | Implementation status | Comment |
|---|---|---|
| Copy issues manually from issue view |  Available | |
| Copy issue during post-function | Available | |
| Copy Jira native fields | Available | |
| Copy custom fields | Available | Check the list of supported Custom Fields. |
| Copy comments | Available | |
| Display comment origin | Available | |
| Copy comments in parent issue |  Unavailable | |
| Copy comments in child issue issue | Unavailable | |
| Copy attachments | Available | |
| Copy to remote Jira instances | Unavailable | |
| Automatic linking | Available | |
| Copy linked issues | Available | |
| Copy external links | Available | |
| Copy subtasks | Available | |
| Create multiple issues at once | Available | |
| Copy to Confluence | Available | This feature is available on Cloud as a stand-alone app: Elements Publish |
| Copy restricted to specific users | Available |
Synchronization
| Feature | Implementation status | Comment |
|---|---|---|
| Synchronization of fields updates | Available | |
| Synchronization of new comments | Available | You can't exclude users, only groups and comment types |
| Synchronization of comments edits | Available | |
| Synchronization of comments deletions | Available | |
| Display comment origin | Available | |
| Post as original comment's author | Available | |
| Post comment as a specific user | Available | |
| Synchronization author (Sync on behalf of) | Unavailable | |
| Synchronization of new attachments | Available | |
| Synchronization of attachments deletions | Available | |
| Synchronize issues created by Copy & Sync | Available | |
| Synchronize issues created manually | Available | |
| Synchronization chaining (Propagation and reindex) | Unavailable | |
| Trigger synchronization on link | Unavailable | |
| Mapping issue type | Unavailable |
Other features
| Feature | Implementation status | Comment |
|---|---|---|
| Map fields to other fields | Available | Mapping has to be done individually for each recipe |
| Set static default values to fields | Available | |
| Advanced values in Fields Mapping | Available | Copy & Sync Cloud doesn't handle Velocity. Your code will be copied as a dynamic value but will not be functional. |
| Data Panels | Available | 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.