Migration FAQ
This FAQ covers the most frequently asked questions about your migration of Elements Copy & Sync from Data Center to Cloud, helping you understand what to expect and how to successfully complete each step.
Migrating Elements Copy & Sync from Data Center to Cloud
Is the migration fully automated or do I have to migrate things manually?
Elements Copy & Sync is compatible with Atlassian’s Jira Cloud Migration Assistant (JCMA). With JCMA you can:
Automatically migrate most of your Operations, Synchronizations, and Fields Mapping.
Cloud-side, these become Elements Copy & Sync recipes with mappings embedded in each recipe.
Key points:
JCMA will adapt your configuration “as close as possible” to Cloud concepts.
After migration, you should review and adjust recipes in Cloud to match your exact needs.
Certain features (Data Panels, Copy to Confluence, Copy to remote instance with old link model, Velocity) are not or not fully migrated and need manual handling.
What parts of my Data Center configuration won’t be migrated?
Data Panels (Data Center) → not supported by Elements Copy & Sync Cloud.
You must use Elements Overview instead. However note that Confluence data panels aren’t available on Cloud.
Copy to Confluence (Data Center) → not supported in Elements Copy & Sync Cloud
You must use Elements Publish instead.
Copy to remote instance (Data Center) → will not be migrated automatically
Cloud does support partially remote instance creation/sync, but the way instances are linked changed and is not backward-compatible. These configs must be recreated manually in Cloud.
Velocity:
Not supported on Cloud. During migration, your Velocity code is copied as a dynamic value but is not functional; you must replace it using the Cloud configuration options (smart values, fields, etc.).
When I’m about to migrate with JCMA, I have a warning message about unsupported features, what should I do?
Don’t worry, this message is designed to remind you that some features are not supported (Data Panels, Copy to Confluence and Copy to remote instances).
This is just for information, you can ‘Continue without resolving warnings’ in the next step and complete your migration if the warnings only concern Elements Copy & Sync.
Once you finished the JCMA migration, you can manually implement the unsupported feature with Elements Publish and Elements Overview.
How does licensing/pricing work during and after migration?
Data Center: You continue using your existing Elements Copy & Sync DC license until you stop using that platform, there’s no automatic renewal or conversion.
Cloud: Elements Copy & Sync Cloud is a separate Atlassian Marketplace subscription tied to your Jira Cloud site and priced per user tier. Apps are licensed to match the maximum user tier of the Jira product.
During migration: Many customers run DC and Cloud in parallel. Atlassian provides Cloud migration trials, and in some cases dual licensing: if you purchase an annual Cloud subscription, your Data Center license can be extended to the same period at no extra cost, so you can use both environments while migrating in phases.
After migration: Once you fully switch to Cloud, you continue with the Cloud subscription. There is no automatic day-for-day conversion of DC license time into Cloud, but migration programs (trials or dual licensing) help bridge the transition.
Will my fields still be synchronized after I migrate my issues from DC to Cloud?
No. Your synchronizations will be transformed into Synchronization recipes in Elements Copy & Sync Cloud but you will have to perform a manual action to activate all the synchronizations.
Can I still automatically create Confluence pages from a Jira ticket during the transition?
Yes, but you’ll need to install the app Elements Publish. With Elements Publish on Cloud, you can still automatically generate Confluence pages from Jira issues during workflow transitions.
Is there a native and integrated way in Jira Cloud to perform cloning and syncing?
Jira Automation is a powerful tool for straightforward scenarios. However, for more advanced workflows, it may require multiple rules, be subject to execution limits, and become harder to maintain over time.
Elements Copy & Sync offers a complementary approach for more complex scenarios, supporting full issue cloning, continuous bidirectional synchronization, and scalable usage across projects or Jira instances, making it well suited for advanced rules and long-term synchronization needs.
Is there any support available to help me migrate?
Yes. We can actively support you during your migration.
You can open a dedicated support ticket and use it as your main thread for all migration questions (planning, UAT, go‑live, troubleshooting).
If you attach a Support dump from your Data Center instance, we’ll:
Review your current configuration (Operations, Synchronizations, mappings, Data Panels),
Explain what will be migrated with JCMA and what must be recreated on Cloud (e.g. Data Panels → Elements Overview, Copy to Confluence → Elements Publish, remote instance configs, Velocity).