Error migrating the JIRA server to the cloud

Ronald Diquélou

Hello

I want to migrate my JIRA Software server to JIRA cloud.
But you can not import my data.

I have an error message stating to update JIRA Help Desk 3.0.
I did not use JIRA Help Desk. To test, I activated the demo of JIRA Help Desk 3.0.
So I have the latest version on JIRA Software, JIRA Help Desk (in trial).

How to migrate my JIRA server to the cloud?

Thank you

Andy Heinzer

Hi Ronald,

What version is your Jira Server right now?  

If you are running Jira version before 7.0.0, then you will need to upgrade both Jira and Jira Service Desk to these versions (7.0.x for Jira and 3.0.x for Service Desk) before you can go any further.  With migrations from Jira Server to Jira Cloud, there is an expectation that your Jira Server version will have to be on the latest version before you can migrate.   I believe the current version of server today is 7.8.2.

There is a scenario where if you ever trialed, or previously used Jira Service Desk (in any version before 3.0), where you would have to upgrade that data in your database first before you could then migrate that to Cloud.

The problem can be many times that if you do not use Service Desk now, you could possibly have to revert to a previous version of Jira to be able to install a compatible plugin version of Jira Service Desk 3.0.0 -> 3.1.x first (which would be Jira Server 7.0.0 -> 7.1.10).   This is a feasible solution, but only if your version of Jira Server is before 7.2.0. 

Otherwise, if you are already on a newer version of Jira, and you do not want to maintain any older legacy Service Desk information that might still exist in your database, then I would recommend taking a look at this ticket https://jira.atlassian.com/browse/JSDSERVER-4732

It's a request to add a method to remove old legacy data from Service Desk.   While there is not an official way to do this, there are comments in that thread that explain which AO tables in the Jira database are responsible for that JSD data.  You could try to delete those specific tables to try to get around this, but I would strongly recommend you create a backup before you attempt something like this and only if you are sure you don't want any of the existing Service Desk data that might still reside in your Jira Server instance.