nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Migration from JIRA OnDemand to JIRA configured on the server

kenorb

Hi,

Is there any way to migrate JIRA OnDemand to JIRA configured on the server?

Thanks.

Accepted answers

Nic Brough -Adaptavist-

Contact support at OnDemand for an export of your data, it'll be importable on download. I'd recommend you do it early on in your migration cycle - you'll want to test it before planning a move.

All comments

Nic Brough -Adaptavist-

Contact support at OnDemand for an export of your data, it'll be importable on download. I'd recommend you do it early on in your migration cycle - you'll want to test it before planning a move.

Thameem Ansari

Great.. I have another question. We have on-demand JIRA and self hosted confluence. I want to use JIRA user management in confluence. Is this possible? If yes what shoud i need to do?

Thameem Ansari

Does the export also include the users and their data?

Wojciech Seliga

This dump will include all user data which is stored in JIRA DB (usernames, e-mails, display names, user properties, group membership, etc.)

Felipe Cuozzo

Note that this answer was true at the time of writing, but now customers can download their own exports at any time. See https://confluence.atlassian.com/display/AOD/Backing+up+and+exporting+data for more information.

Felipe Cuozzo

Unfortunetly that is not possible as Crowd OnDemand (and that is what JIRA OnDemand uses for its own user management) is a restricted component.

Please if possible try to keep unrelated questions on different threads so everyone can benefit from the answers/karma points easily.

Felipevsw

Just to give an updated answer on this subject: the whole migration process is well documented here: https://confluence.atlassian.com/display/JIRA/Migrating+from+JIRA+Cloud+to+JIRA+Server

Cheers,
Felipe

Cullen Philipps1

Migrating from onDemand to Jira server ran in to an issue with DB versions. Imported the backup as instructed but upon restarting the Jira service got this error:

****************************************************************************************************

Failed to start JIRA due to a build number inconsistency.

The data present in your database is newer than the version of JIRA you are trying to startup.

Database version is: 64000

JIRA app version is: 6331

Please use the correct version of JIRA. You are running: 6.3.3#6331-sha1:d919e5c6aac4bdb845e5512db42aa18387f6a299

****************************************************************************************************

Since the onDemand version is upgraded first, how is one to migrate away from it?

Any advice?

Thanks,

Cullen

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

migration

jira-cloud

download

backup

move