Migration from Github Enterprise to BitBucket Data Center (both on-prem)

[Chris Marsh]

I am looking to do a feasibility study and a migration plan on moving from Github Enterprise on-prem to BitBucket Data Center on-prem. We have multiple organizations with multiple repos under each organization in Github, and I am wondering how easy it will be to migrate from Github to BitBucket. 

Has anyone done this before that can point to any How-To's for this procedure?

We have 140 users currently in our on-prem GitHub system. 

The biggest pieces I am concerned about are the following:

• Migrating Orgs + Repos
• Users + ssh keys
• Repo History
• Branch History
• Active Pull Requests

Any help would be greatly appreciated. 

[Aaron]

 Hello Chris,

Thank you for reaching out to the Atlassian Community!

I wasn't able to locate on how-tos but it would be possible to migrate most of this information. It may not be the smoothest process, but it's definitely possible.

Repositories are going to be the easiest thing to move. Since it's all just Git, you can clone and pull down any repositories, and push them to a new clone URL (in this case Bitbucket Data Center). It seems that GitHub has an export process, so you can get all of the repository URLs and then parse them with some script. 

I'm not sure what else is created or gathered with that tool, but to be on the safe side to ensure Bitbucket Data Center is running as expected without any wonky data, we should just have the repository URLs.

Because we are working with Git, repository history will naturally be carried over. Fetching and pushing all branches is also something that is possible to do natively in Git. The branch history will also exist.

Assuming orgs work just as regular groups, you can use the REST API to do this. Grabbing the list of groups and their users from GitHub and then using the API to create and add users to groups will be the most efficient way to do this.

There isn't a REST API for SSH keys in Bitbucket Data Center so unfortunately, your users will have to add them back themselves.

Lastly, pull requests aren't something that can be migrated. You can use the REST API to create new pull requests to remake the active PRs, but if you are going to migrate, I would get all of your PRs merged, and then move the code since the merge commits will still exist, you just won't be able to see the pull request history.

I hope that answers all of your questions, and if you have any others, don't hesitate to ask!

Regards,
Aaron Levinson
Dev Tools Support Engineer