Can you describe the challenges you experienced during the DC to cloud migration?
Hi @Suresh Chadalawada ,
1. Apps or plugin comparability, if there are any internally developed plugins then you will have to find the replacement and add the configurations manually.
2. user adaptation- not everybody wants to move so need lot more training.
3. macros in Confluence, there are many use cases that all the macros don’t work in Confluence cloud so need to find alternative.
4. user import: as per the Atlassian community I see lot of issues during the users and groups migration like duplicate users.
5. Scripting issues in JMWE and JSU: Scripting will be varied in Jira datacenter(Groovy) and Jira cloud(Nunjucks and Jira expressions) for workflow extensions.
Hi @Suresh Chadalawada ,
Thanks for posting your question here on the community.
I am Dhiren, one of the Solutions Engineers working at Exalate.
In addition to the challenges mentioned by @Sanam Malleswari , I would like to add a few more things here.
Data Volume and Complexity: Migrating large datasets—especially with complex custom fields, workflows, and issue hierarchies—posess risks around performance, data integrity, and downtime.
Customization Gaps: Some on-prem scripts and customizations will not be directly portable to Cloud, necessitating rework or deprecation.
Downtime Planning: Minimizing disruption during the cutover requires precise coordination, communication with stakeholders, and often multiple dry runs.
To streamline collaboration during and after migration, you can leverage the power of Exalate.
It enables real-time, bidirectional synchronization between Jira DC and Jira Cloud, allowing teams to continue working without disruption—even across different environments.
Exalate’s decentralized architecture and flexible configuration ensures data stays aligned and secure, making it a valuable asset throughout the transition.
Thanks, Dhiren
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, @Suresh Chadalawada ! Welcome to the Atlassian Community!
In addition to @Sanam Malleswari 's comment, when using the migration assistants (JCMA and CCMA) not all data can be migrated yet with the latest version, so it is always important to map the effort you will have refactoring some of the data.
Here are some links listing what gets migrated with the assistants:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.