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 you’ll immediately lose features that are exclusive to Data Center.
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 Bitbucket instance:
| Feature | Description |
|---|---|
| SAML single sign-on Use a SAML identity provider for authentication and single-sign on. |
|
| 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. |
|
| Smart mirroring Improve Git clone speeds for distributed teams working with large repositories. |
|
Before you begin
This guide assumes that you’re using a standalone Bitbucket 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 Bitbucket Server
You can purchase a Server license or create an evaluation license at my.atlassian.com.
2. Apply the license
Go to Administration > Licensing.
Update the license.
After updating the license, your Bitbucket instance will become a Server one.