[rsp1984]

Great. I need to push some stuff real soon now. In the last 12 months Bitbucket had an uncomfortably high number of issues. But whenever I think about moving our company code to GitLab or GitHub I envision going into a world of pain with my eng. team.

Has anyone got some advice for pain-free migration to GitLab or GitHub?

[zmb_]

Git isn't centralized so there is no need to "move" the code. You can use Bitbucket, GitLab and GitHub all at the same time -- just add multiple remotes, I do this as a part of my normal setup. You can even pull directly between developer machines without the need for any centralized repository. The tricky part is all the tooling around the code (issues, wikis, CI, etc.), but no matter which provider you use for it, they will have downtime.

[sevensor]

We moved over to GitLab a couple of weeks ago. We're small, so the calculus is a lot different for us. The migration basically consisted of clicking the import button and making sure everybody's remotes were changed over. We switched because we got tired of Atlassian trying to sell us all of their services all the time. The systems that make a big organization run more smoothly are a drag on a small team, and the more we saw of Atlassian's offerings the less we wanted them.

[jazoom]

GitLab is way better than Bitbucket IMO but also has way too much downtime.

[fapjacks]

Why not both?