Status: Open (View Workflow)
Affects Version/s: None
Fix Version/s: None
BSERV-3555 addressed some of the Git repository import issues, customer could benefit from the ability of importing in bulk from another Bitbucket Server instance in case a customer is migrating instances.
Currently the feature allows to import in bulk from Bitbucket Cloud and GitHub:
Include an option to import in bulk from another Bitbucket Server instance.
What we do have is a small experimental (and, please note, unsupported) command line tool that will take a collection of repositories on disk, create the project/repositories and then push them to Stash*.
It can do this iteratively so you can refine the project/repo names for each on-disk repository. This, of course, means you will need to clone your repositories from your other Bitbucket Server instance to a local disk first before you can run the command line tool.
I realize it's not ideal for you but it does at least limit the grunt work you'd have to do on the Stash* end (creating the project, repositories and pushing).
You can find the source to the project here https://bitbucket.org/atlassianlabs/stash-importer and the binary here https://bitbucket.org/atlassianlabs/stash-importer/downloads/stash-importer-0.1-distribution.zip
There is a readme file in the binary distribution which explains how to use it.
* this tool is an experimental one and was developed for Stash. Since then there were many new releases and the tool hasn't been maintained.
Whilst there is no way to
BSERV-4586 - As an admin, I want to be able to export and restore projects or repositories individually, so that the metainformation (e.g. pull requests details) are preserved, providing this ability would help address at least part of the problem.