Hello,
after evaluating JIRA OnDemand for a month we decided to buy it but move it to a local server.
I exported the data using the backup manager https://sitename.atlassian.net/plugins/servlet/ondemandbackupmanager/admin and imported it using the Restore System feature (/secure/admin/XmlRestore!default.jspa).
Unfortunately, I receive the following error message: The xml data you are trying to import seems to be from a newer version of JIRA. This will not work.
I installed the newest available version of JIRA (5.1.2). The entities.xml file which is part of the backup zip reveals that our OnDemand evaluation instance is already using 5.2:
JIRA Build : 5.2-m01#801-sha1:64b2711279bea95f4bef1d3c6b6c5edda6c8d086
Build Date : Sun Jul 22 00:00:00 CEST 2012
Is there another way to migrate data from our OnDemand evaluation instance to our local installation?
Kind regards,
Heinz
Hi Heinz,
Since OnDemand instance is a bit different than the standalone, OnDemand use a different set of build number which may cause standalone version to think that the XML export comes from a higher version. Please refer to uor knowldge base article here for detailed information on how to solve this issue:
Hope it helps.
Cheers,
Septa Cahyadiputra
Just to give an updated answer that the whole migration process is documented here: https://confluence.atlassian.com/display/JIRA/Migrating+from+JIRA+Cloud+to+JIRA+Server
Cheers,
Felipe
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the update, Jakub - this should just need the license for your new stand alone instance to move forward (as I mentioned in the related ticket).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just installed a new 5.1.8 instance of JIRA and getting the same error on System Restore Import from OnDemand.
@Dave Nicholson This is related to my blocker at JST-49720
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
UPDATE
This was related to a bug which incorrectly reported the build number in the properties (https://jira.atlassian.com/browse/JRA-29841), which has been fixed. For 5.1.5 versions, the workaround is -
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.