Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Upgrading Bitbucket



I am in the process of upgrading to a new set of Bitbucket (all Centos7) servers. I am starting off by recreating the old server setup in the new one and then upgrading the version (4.13 > 5.9 or higher). I am using Postgres 9.2.23 right now and the plan is to move to 10+.

I have already moved the data from the old server to the new one and it starts up just fine.

I am trying to move the db into the new server with a .sql backup file and I am having no luck in completing this effort. 

Since this isn't working I'm considering the following:

  • Getting a .dump backup file created and trying to restore that into the new db instead of the .sql file.
  • Doing a db migration on the new server from the old db to the new db. I have concerns about this though. Will the old server have an interruption of service (how much)? Will the old server continue to operate after this migration?

I am really liking the migration option but I cannot simply change the service over permenantly until i have upgraded and tested everything on the new set up.


Shankar Asam {Appfire}
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jun 15, 2018 • edited

If you want to migrate the databases for bitbucket, you need to do the following;


  • shutdown the bitbucket instance
  • take the db (.sql) backup / dump from current db server
  • go to the new db server and restore .sql / dump file
  • go to bitbucket application server and file and change the database related info (DB host name, db name , user / password etc)
  • start the bitbucket instance - it will start with new db
Caterina _or Kate_ Curti
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 17, 2018

Hi @devittward,

What @Shankar Asam {Appfire} suggested is a valid starting point (Thanks!).

However, we always recommend to restore both the home directory and the database from a backup taken at the same time. This is to make sure that the data are 100% consistent.

The change of the jdbc url in the is still required and you want to always double check that this is done to avoid to upgrade the database of the current server by mistake.


We also have a guide that covers How to Migrate Bitbucket Server to another server, this contains various links to the necessary checks and prerequisites (e.g. Supported Platforms).


An alternative could be to backup the data from the current instance and restore them in the target one (see Data recovery and backups for options).



Caterina - Atlassian

This issue has been resolved. 

I installed Postgresql-9.5, then moved a restored a .dump version to the new server.

The bitbucket upgrades of a higher version did not workon start up. The error was that the table names were wrong, or that the configured database was not compatible. My solution was to incrementally upgrade starting with 5.0.5> 5.3.6 >5.5.5 > 5.8.3> 5.10.1 and 5.11.1. Sure this might be overkill but it was tired of the database errors.

The root cause was that the table names were not the same in the pre 5.x.x versions and threw an error each time I attempted to upgrade.

Perhaps once I upgraded to 5.0.5 I could have made a bigger jump but oh well. It is finished.

Caterina _or Kate_ Curti
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 29, 2018

Hey @devittward,

An upgrade directly to the latest version is, in general, always possible. I'm not sure what happened exactly, but I'm glad it's all working now!



Thanks, I am getting ready to upgrade our version from V4.13 to V5.10.1 and was wondering if there would be any issues.  This answered my questions.

Caterina _or Kate_ Curti
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 17, 2018

Sure, no problem @Joe Harvey [Wolfpack95N]!


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events