Moving back to Server
If you no longer need Data Center, you can go back to a Server installation. This will be as easy as updating your license, but be aware that losing the Data Center-only features might affect your Jira instance.
How will the Data Center-only features be affected?
After moving from Data Center to Server, you will lose features exclusive to Data Center. Here’s the summary of how this will affect your current Jira instance:
| Feature (non-clustered) | Result |
|---|---|
Project and issue archiving Archive projects and issues once they're no longer needed. |
|
SAML single sign-on Use a SAML identity provider for authentication and single-sign on. |
|
Custom fields optimizer Scan and manage custom fields easily to optimize your Jira Software instance's performance. |
|
Content Delivery network (CDN) support Improve geo-performance for distributed teams. |
|
Rate limiting Control how many external REST API requests users and automations can make and how often they can make them. |
|
Before you begin
This guide assumes that you’re using a non-clustered (single node) Jira Data Center. If you have a cluster of nodes, go to Moving to a non-clustered Data Center first.
We recommend completing this process in a staging environment, and running a set of functional tests, integration tests, and performance tests, before making these changes in production.
Moving back to Server
1. Get a license for Jira Server
You can purchase a Server license or create an evaluation license at my.atlassian.com.
2. Apply the license
- Go to Administration (
) > Applications > Versions and licenses. - Update the license for each of your applications.
After updating the license, your Jira instance will become a Server one, and you’ll immediately lose access to Data Center-only features.