Maren here from Atlassian. I wanted to give a quick update to help point people in a similar situation towards the right resources.
To answer some of the questions asked:
1) The documentation states “This import procedure overwrites all the existing data and configuration in JIRA cloud applications and cross-application settings”. Does this mean that if we import the on-prem projects that the existing 20-30 projects in the cloud will be lost?
Answer: Yes, the current site import functionality overwrites the existing data on your cloud site. A possible workaround is to migrate to a new, clean cloud site, delete any data you don't want, and then merge the two cloud sites together.
2) Is there any way to migrate a single project to cloud or is this an all or nothing migrations per the documentation?
Answer: As Boris mentioned, Jira Cloud doesn't currently support project-by-project migration, only full site import - although we are working on resolving that. You can find the documentation for that here. However, since this is a popular request, we do have an article outlining a potential workaround, however, it's important to note this is not officially supported by Atlassian.
3) What would happen if we migrated the issues, but did not migrate attachments/avatars/logos? Would the projects and issues be available, but the avatars/logos would not appear and the attachment links would not work?
Answer: Yes, you would still have the projects and issues but anything not imported will not be available in your new site.
4) Our client has a server app, how does this affect migration?
Answer: App data is not typically included in the backup when migrating from Jira Server to Jira Cloud. Some apps do have the capability to export and import their data but you'll need to check with the app developers or their documentation to confirm if this is possible.
Zephyr is available as both a cloud and server app, however, you will need to work with the app developer to plan your migration strategy or understand what options are available.
Keep in mind that while Atlassian’s cloud and server products provide the same benefits – planning, tracking, collaboration, code repository management, and more – they can differ in features and functionality. In some cases, you may discover that the cloud version of a product includes functionality that is fulfilled through an app on server. Learn more about Atlassian cloud and server apps.
For more info to help you decide if moving from server to cloud is a good option for you, check out our Atlassian Cloud Migration Center. For Jira-specific advice, check out:
Hope this helps, and please don't hesitate to reach out with questions.
JIRA Cloud supports only full system import and does not support single project import.
So in short what you need to do is:
There are more things to consider like (but not limitted to)
What Boris said.
One other thing is that during this process, you don't want users coming in to the Cloud system and changing data, because they will lose edits after you import back at step 5.
If you have a small team, maybe you can just communicate this, but with a bigger team I would do something else ... eg Lock down all the project permissions to give no-one any editing permission (read-only) or even give them no permission at all.
Our client has JIRA + JIRA Agile and Zephyr for JIRA – test management for JIRA (Server) 100 users, and their licenses expired two years ago.
They want to migrate from their server to the cloud solution and before they can do that they need to upgrade to the latest version of Jira Software first, before they can migrate to the cloud solution.
I’m wondering how this impacts the Zephyr for JIRA add-on? Do they need to upgrade the add-on first before migration or?
Posting the Answer for this post I know its too late to reply but maybe it will be useful for someone
1-download Cloud Migration assistant on your Jira server.
2- make a migration from server.
3- chose your migration name, cloud destination
4- chose the list of the projects you want to migrate them to cloud
5- chose users and groups related to the projects, and check the migrate users and groups saperately.
6- continue to error check, if any user or project key or email show in error list remove them from your server.
7-continue to migrate
this process will take approximately 4-5 hours. nothing will be override.
...ustomers receive an estimated 155% ROI and total benefits/savings of $1.8M over three years! Check out the report and the rest of our newest resources below, as well as our tried and true that m...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events