I try to move data from OnDemand to standalone JIRA. It turns out that even latest EAP JIRA release version appears to be older than OnDemand JIRA installation. Therefore, following message appears: This data appears to be from an older version of JIRA. Please upgrade the data and try again. The current version of JIRA is at build number '764', but the supplied backup file was for build number '767'.
Are there alternative ways to export/import data between OnDemand and standalone JIRA installations? Is it possible to request database backup in MySQL format for the data stored in OnDemand JIRA? Or maybe there release dates are already known and I just need to wait for the latest release to be published?
The problem you are facing here is that the you are trying to import data from OnDemand, currently running JIRA v5.1, and import it into an older instance of JIRA. Generally this isn't possible, although one thing you can try is to search/replace the build number in the XML data so that you change the build number from 767 to 764 and attempt the import again. Depending on how much the schema has changed between the versions, this sometimes works and sometimes doesn't. We don't recommend doing this, but sometimes it can work.
It isn't possible to get an database backup of your OnDemand data in MySQL format because OnDemand instances run on Postgres databases, although it also isn't possible to get a database dump of your OnDemand data in any format because the data has to be sanitised before being exported because it contains lots of platform specific customisations that don't translate over to downloadable versions of our products. Therefore the only export route for OnDemand instances are the supplied XML backup tools.
However, it sounds like you are actually downloading and installing the latest downloadable version so you may have discovered that sometimes a version is released to OnDemand a few days before it is available for download, so this is most likely the cause of your issue. But, if there is still a disparity between the build numbers in this case then I would suggest using the method I mentioned in the first paragraph of this comment to import your data because there shouldn't be any differences in the schemas.
All the best,
Hi Theodore, The link you have posted is a dead one.. Please update the link. Also, it is strange that such a great tool from Atlassian do not have any utility to migrate the content. Though Project Configurator is available developed by a third party vendor, It would be great if you (atlassian) makes it easy for the people in migrating the content.
Hi Raja, We have a detailled migration guide here: https://confluence.atlassian.com/display/JIRA/Migrating+from+JIRA+Cloud+to+JIRA+Server This guide does not cover importing into older versions of JIRA as this is not supported by the product itself. In order to make this possible you can follow the explanation provided by John (changing the build number) but please be aware that we do not recommend this as this might cause data inconsistencies / corruption.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG