Introducing: Repo Transfers

By on June 13, 2012

A couple weeks ago, we launched our new Teams feature to make it easier for our users to collaborate on Bitbucket. Today, we’re happy to introduce Repo Transfers to make it easier to share repositories amongst your team.

Repo Transfers allow you to change the ownership of a repository to another team or user account. Transfer any group repositories from your account to your team’s account and share it with your fellow team members. The account holder you are sending the repository to must accept the transferred repository to complete the transfer. Transferring a repository moves the commit history, issue tracker, and wiki associated with that repository along with the source.

Get Started

In order to transfer a repository, you must be an admin of that particular repo. Click the Admin tab, and select Transfer Repository from the left side of the menu.

Enter the username of the user or team account you want to transfer your repository to. Bitbucket will send a transfer request to that particular user or team account.

If you receive a transfer request, Bitbucket will send you a transfer request message in your inbox. If you have administrative rights to multiple accounts, you can choose the account that should own the repository through a drop down menu. This can be an account other than the account listed on the transfer request message.

After a repository changes owners, any configuration files that contain the old URLs must be updated, as the repository’s URL will change to reflect the repository’s change in ownership. To find out more on how to do this along with other specific details about repository transfers, check out our documentation on repository transfers.

Innovation Week

Repository Transfers were built as a part of Bitbucket’s new Innovation Week. At the end of each dev cycle, the Bitbucket team will now spend a week to develop new features that they want to work on. Stay tuned to the blog for more information on Innovation Week features in the future.


  • Posted June 13, 2012 at 11:07 am | Permalink

    Awesome new feature! But I would love if a redirect was created similarly to deleting a repository. See also

  • sundy
    Posted June 14, 2012 at 11:14 pm | Permalink

     I quite agree with the views of the author, at the same time, welcome to our website, we will provide the high quality product, still at etc. What, to pick their own one.Authentic football jerseys for all the fans expectations. However, these authentic jerseys are manufactured from high quality nike nfl jerseys, and contains many changes in design, in fact, be too expensive to buy an ordinary fan shirt does not pay. Compromise, repetitive cheap Authentic NFL Jerseys,  You really can. Professional football jersey, non-Hodgkin’s lymphoma, NBA, and replica nfl jerseys, football jerseys, excellent quality and competitive prices, no minimum order ship within 24 hours! Saved many forms.

  • Joshua Holmes
    Posted August 9, 2012 at 3:21 am | Permalink

    This is a great feature however for those migrating from individual developer accounts to a team account a REST API interface for this method is greatly desired.

  • Kristof Coomans
    Posted November 14, 2012 at 2:14 am | Permalink

    I also miss an implementation of this in Bitbucket’s REST API. Created an issue here:

  • Posted December 27, 2012 at 5:32 pm | Permalink

    Do forks of the transferred repository get updated to point to the new repository URL as their upstream?

    • Posted February 1, 2013 at 2:34 pm | Permalink

      To answer this question, we created a bunch of related test repositories and performed a transfer. In short, it worked perfectly: forks were updated, and pull requests did not break.

  • dan
    Posted April 10, 2015 at 6:27 am | Permalink

    why can’t I glance at this write and know what to do?

  • Posted August 26, 2015 at 8:03 am | Permalink

    Nice feature, saved me!