Migrate JIRA data from OnDemand to a local instance

[Heinz Roth]

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

[Septa Cahyadiputra · Accepted solution]

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:

• JIRA OnDemand export does not import into standalone JIRA

Hope it helps.

Cheers,
Septa Cahyadiputra

[Rene Rath]

link is dead.

[Felipevsw]

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

[Dave]

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).

[Jakub Kierszka]

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

[Dave]

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 -

• Shutdown JIRA
• Edit JIRA_INSTALL /atlassian-jira/WEB-INF/classes/jira-build.properties
• Change property to downgrade.allowed.build.number = 806
• Create a new completely clean database
• Edit JIRA_HOME /dbconfig.xml file to point to the new database
• Start JRIA
• Go to the import existing data link
• Fill in the backup name and JIRA license
• You'll get one warning, continue anyway and attempt import again