Want to move away from on demand to local server

[Nicolaas]

Hi we want to buy JIRA and install it on our local server. Is there an easy way to do this? and is there any issues doing it?

Want to transfer all tickets (with all custom fields) and all workflows.

[Nic Brough -Adaptavist- · Accepted solution]

It's not as painful as you might think. Atlassian will give you an export when you're ready to move, and that will include everything, fields, issues, workflows, users and so-on.

The only things that I've run into that cause significant problems are

1. If you're changing user management during the move (OnDemand will give you a user list and you'll be able to import it into Jira as part of the data automatically. But if you want to move to LDAP...). Consider a two-step approach - move off OnDemand, people retain their existing accounts, then hook up to the new user system later.
2. OnDemand is often of a higher version than the target system. Check the version matrix in the doc I'm about to link to though. (This has improved as OnDemand has matured)

Have a look at https://confluence.atlassian.com/display/JIRA/Migrating+from+JIRA+OnDemand+to+a+JIRA+Installed+Site

[Dave]

Any administrator can actually go ahead and create that system export whenever they're ready - no need to wait on Support to provide that anymore.

[Susan Hazlett]

I'm in the process of doing this right now, and I'd recommend a staged approach. Nic Brough indicated that in his first item.

A few things to note:

-Migrating from OnDemand to installed is almost trivial if you are doing a 1 to 1 migration.
-Do set up a staging server at the very least, separate from your production server. This will help you to work around any problems that might arise in a safe environment. Your installed instance license allows for a staging server.
-Make major changes one at a time. Migrate first and let your users get used to the new URL/location for accessing JIRA. Then change your authentication method if that's desired.
-Make sure you have a good process for taking your system down for maintenance and informing your users.
-Communicate the timelines to your users regularly, and let them know what to expect.
-Make sure you lock out your users from using the OnDemand instance just before the final migration so that no new issues are created *after* migration. Then you can do your final system export for migration.

There's quite a bit to do to prep for it, but mostly to ensure it all goes smoothly. Atlassian has made the technical bits of the migration pretty darn straight-forward. It's the non-technical bits that usually end up getting in the way.

Good luck!