You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We migrated successfully beginning of this year from jira server to jira cloud. Due to some internal reasons, we have a bunch (around five) projects that still needed to use our old internal jira server for their work.
Unfortunately, some of those projects made changes on both ends (the server instance and the cloud instance), so the question is how to migrate the server data to the cloud, without loosing changes in the cloud there.
Normally, I would assume that I delete the project in the cloud and import from the server with the jira cloud migration app.
But, how does this app behave, if a project of the same name already exists? Does it fail? Does it just add new issues, does it overwrite?
If it can't handle this situation, what is the best way to proceed?
If I remember correctly, the Migration Assistant will tell you when a project with the same key already exists at your Cloud site, and will not allow you to select that project for migration unless you first delete it from the destination. You can still migrate other projects.
If you need to merge issues for projects that have been worked on in parallel, CSV import seems to be the only option: https://confluence.atlassian.com/cloud/compare-cloud-migration-methods-981151113.html