Migrating from JIRA OnDemand to a JIRA Installed Site
This page is for people who are currently using a JIRA OnDemand site and wish to move to a JIRA site that is hosted on their own servers.
Summary
You will need to download and install the latest production release of JIRA (for example, 'JIRA 6.0.2') and then move your data from your hosted JIRA OnDemand site into your newly installed site.
On this page:
Before you begin
JIRA OnDemand is regularly updated with the absolute latest features and improvements — it is essentially running on a later version of JIRA than the latest downloadable version of JIRA. If you want to migrate from JIRA OnDemand to a site installed from the standard JIRA download, please be aware of the following information before you begin:
Feature loss
If you migrate from JIRA OnDemand to a site installed from the standard JIRA download, you will likely find a few features missing. This is because we have introduced features from the upcoming JIRA downloadable version into JIRA OnDemand. For example, the latest JIRA production release for download is JIRA 6.0.x. JIRA 6.1 is currently under development. Some of the JIRA 6.1 features have been made available in JIRA OnDemand, but will not become available for downloadable JIRA until the final JIRA 6.1 version is released.
JIRA license
Your Atlassian OnDemand license cannot be used in a site installed from the standard JIRA download. You will need to generate a new "JIRA" license from https://my.atlassian.com for your site installed from the standard JIRA download.
You can reuse your licenses for plugins in your site installed from the standard JIRA download. The licenses for Atlassian plugins and Gliffy for JIRA can be viewed on https://my.atlassian.com. You will need to contact your vendor for the licenses for all other third-party plugins.
Migrating other OnDemand applications
The instructions on this page only apply to JIRA. If you are migrating other OnDemand applications (e.g. Confluence OnDemand to a site installed from the standard Confluence download), please see this page: Backing up and exporting data.
Note, if you are migrating JIRA OnDemand and other applications (e.g. Confluence OnDemand) to a site hosted on your own servers, you will also lose a number of integration features that are native to OnDemand (e.g. Creating Links). These can be re-enabled by configuration application links between your applications. See Configuring Application Links for instructions.
Instructions
1. Generate a backup of your JIRA OnDemand data
- Log in to your JIRA OnDemand site as an administrator.
- Generate an XML export from your JIRA OnDemand data by following the instructions in Exporting issues. This includes instructions on how to back up your attachments.
Note, the export process will strip out your Atlassian OnDemand license and your plugin licenses. - Download the backup file from your OnDemand WebDAV directory (also described in Exporting issues).
2. Install JIRA from a standard download
We strongly recommend that you use the latest version of downloadable JIRA.
- Download the latest version of JIRA here: http://www.atlassian.com/software/jira/download.
- Follow the instructions in Installing JIRA until you are instructed to run the setup wizard, then see step 4 below.
3. Import your JIRA OnDemand data into your JIRA installation
Complete the instructions in Running the Setup Wizard until you have configured a database (described in step 1 of Running the Setup Wizard). We recommend that you use PostgreSQL for your database, although you can use any of the supported databases. If you already have some data in your JIRA installation, this step will overwrite it.
In step 2 of the Setup Wizard (Application Properties), you will be asked whether you have existing data. Click import your existing data and follow the instructions to import the JIRA OnDemand backup that you generated earlier.
See Restoring Data for more information.
For instances with large backups (2Gigabyte and up), we recommend importing the attachments separate from the Issue and user data.
4. Change the system administrator password
- Log in to your new JIRA site, using the following credentials:
- Username:
sysadmin - Password:
sysadmin
- Username:
- Change the password immediately after logging in.
5. Check which plugins are installed on your JIRA OnDemand site
Any plugins that you are currently using with JIRA OnDemand will need to be installed in your JIRA installation. For example, JIRA Agile, Tempo, etc.
Choose the cog icon 
at top right of the screen, then choose Add-ons. The Manage Add-ons screen shows the plugins currently installed on your JIRA site. Choose Manage Add-ons and note the plugins listed under the User-installed Plugins section. You will need to note the plugin names and versions.
6. Install plugins (add-ons)
For each plugin that you noted in the previous step, install it in your JIRA installation. You must install a version of the plugin that is equal to or later than the plugin version that was installed JIRA OnDemand. Atlassian does not provide support for data that is downgraded as a result of installing an older version of a plugin.
See Managing Add-ons for instructions on how to install a plugin. You will need to manually add the plugin license keys.
Version matrix for imports
The following table tells you which version of downloadable JIRA to use, when migrating from JIRA OnDemand. The version number is dependent on when you exported your data from JIRA OnDemand.
We recommend that you use the latest JIRA version unless otherwise specified below. Only use the versions listed below if you cannot use the latest JIRA version.
| Date when export was made | Version of downloadable JIRA to use |
|---|---|
| Prior to 3 Dec 2012 | Contact support for assistance |
| 3 Dec 2012 — 16 Dec 2012 | 5.2.1 |
| 17 Dec 2012 — 20 Jan 2013 | 5.2.2 |
| 21 Jan 2013 — 6 Feb 2013 | 5.2.5 |
| 7 Feb 2013 — current | Use the latest version available |