Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Server to Cloud migration not consistent



I have tried to migrate a Jira Service Desk Project from a Server to the Cloud site multiple times without success. It is not consistent: the issues do not appear, sometimes neither the users and even the project itself does not create after the migration.

If I check the post-migration logs the require attention log does not show anything (good thing as I understand) but the post migration log sometimes shows that all data was migrated correctly but sometimes shows that 0 users, issues, etc. were migrated.


I need a solution ASAP as we are closing the server in which the project is migrating from. I have tested to perform a prod migration type but with no success as well.


Thank you.



2 answers

Hi @Admin 

Migration projects are typically complex and require careful planning and strategy. The following factors might be causing issues while you are trying to migrate from Jira Service Desk on-premise to Jira Cloud.

1) Project key restrictions: Jira on-premise allows underscore (_) and a few other characters in project key, whereas on-cloud allows only letters in project key. Any migration needs to factor in strategy to address these differences.

2) Plugin entity context and handling: If you are using plugins, those may require additional/special handling. Any such activities should be planned as part of the migration plan.

3) Duplicate or empty user emails: Jira on-cloud requires all users to have a unique email address. This may be one of the reasons for the migration issue.

Additionally, for most of the migration solutions, you also need to worry about the following:

Impact on user productivity due to down time: Various migration approaches can drive different levels of disruptions and impact on productivity. Some may require the project or the Jira instance to be in read only mode for an extended period. This impacts team productivity as they are not able to use Jira till migration is going on.

OpsHub has extensive experience in undertaking complex migration projects ensuring zero downtime, no data loss, systematic cut-over and factory approach. We are happy to help in your migration planning process. Please reach out to our solutions architects for a quick initial migration planning.



0 votes
Dan Breyen
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Apr 17, 2023

I would recommend opening a ticket with Support to address your concerns with the migration.  They helped me out with similar issues during migration.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events