Upgrade methods
Choosing the upgrade method depends on the specifics of your environment. Below you can find information that will help you choose the right one for you. If you don’t have any particular requirements and just want to upgrade Jira, pick one of the regular methods.
Regular methods
These are the regular methods of upgrading Jira. Make sure you also check additional options below them.
Installer
Server | Data Center
This method includes the use of a typical installation wizard that will guide you through all the stages of upgrading Jira. On each of the panels, you’ll need to provide necessary information, such as your user credentials, or details needed to connect to the database.
What you'll download: .bin or .exe file
Manual
Server | Data Center
This method includes downloading Jira files compressed into a .zip or .tar.gz package, and extracting them into the chosen location. It doesn’t include a typical installation (as you'll extract an almost-ready Jira instance), and so is much faster. You’ll provide all details needed to connect Jira to your database by manually editing the right files.
What you'll download: .tar.gz or .zip archive
Additional options
These options reuse the installer or manual, but contain extra pre- and post-upgrade steps.
Zero downtime
Data Center
Upgrade with zero downtime is a special method available for Jira Data Center. It introduces the upgrade mode that allows your nodes to work on different Jira versions while you upgrade them one by one. During the upgrade, Jira remains fully functional and open to your users. It’s performed by using either the installer or manual - it’s a classical upgrade, just with extra pre-upgrade and post-upgrade steps.
What you'll download: installer or manual (see above)
Unavailable for Jira 7.x to Jira 8.x upgrades
This method is not available when upgrading from Jira 7.x to Jira 8.x. Once you're on Jira 8.x, you can use it to upgrade to any later version.
Fallback
Server | Data Center
This method allows you to safely roll back to your previous Jira version if the upgrade takes longer than expected, or if you encounter any issues. It requires that you set up a proxy server to have a quick way of redirecting your users either to the existing or to the new instance of Jira, depending on whether you're happy with the upgrade or not. It’s a good fit for environments where Jira is mission-critical, and you can’t allow prolonged downtime.
What you'll download: installer or manual (see above)
Migrating Jira
Use the following methods to migrate your Jira instance to a different server, or to migrate between Jira Cloud and Jira Server.
Migrating Jira to another server
Server | Data Center
This method lets you migrate your Jira applications to a different server, which includes new operating system, new locations for storing your index or attachments, or new database or database system. To migrate Jira, you’ll need to install a new Jira instance, and then migrate your existing data between the databases, finally also copying your home directory and any existing customizations.
What you'll download: installer or manual (see above)
Migrating from Jira Cloud to Jira Server
Server | Data Center
This method is for people who are currently using Jira Cloud, and wish to move to Jira Server (a Jira installation hosted on your own servers). Jira Cloud might be ahead of Jira Server, or focusing on slightly different areas, which means that some features may not be available after you’ve moved to Jira Server. The migration will include installing Jira Server from scratch, and then moving your data from Jira Cloud to your new database.
What you'll download: installer or manual (see above)
Migrating from Jira Server to Jira Cloud
Server | Data Center
This method is for people who are using Jira Server and wish to move to Jira Cloud. Currently, you can migrate in two ways:
- Use the Jira import site (Server and Data Center)
- Use the Cloud Migration Assistant that allows you to migrate your projects, users, and groups (Server)