Streamlined Transition from Bitbucket Server and Bamboo to GitHub

Technical assistance, security upgrades, and vulnerability patches from Atlassian will no longer be provided for their server solutions, such as Bitbucket Server and Bamboo Server.

SMEStreet Edit Desk
Updated On
New Update

GitHub, the world’s leading AI-powered developer platform has launched  support for migrations from Bitbucket Server and Bitbucket Data Center, allowing one to seamlessly bring code, pull requests, reviews and comments on the platform. GitHub Enterprise Importer now supports migrations from Bitbucket Server and Bitbucket Data Center, and GitHub Actions Importer allows you to move from any of Atlassian’s CI/CD products–Bitbucket, Bamboo Server, and Bamboo Data Center–to GitHub Actions.

From February 15, 2024, Atlassian will no longer offer technical support, security updates or vulnerability fixes for their Server products like Bitbucket Server and Bamboo Server. Switching from these tools to GitHub Enterprise Cloud and GitHub Actions has become easier, safer, and even more seamless.

Companies across the globe rely on DevOps to fuel growth and drive innovation. However, DevOps is a complex landscape with an even more complicated developer tech stack. There are countless tools that don’t always integrate easily or work together, resulting in a disjointed experience and operational overhead. And despite industry-wide investments in DevOps, developers report that the most time-consuming thing they’re doing at work besides writing code is waiting on builds and tests. Concerns regarding data security and the risks associated with coordinating workflows across numerous tools are often raised. Navigating this intricate landscape has become increasingly challenging. Investing in the developer experience can not only result in four to five times more revenue growth, but having a single, integrated platform allows for developers to spend their time doing what they do best - building great software and making an impact.

GitHub is a platform used by over 100 million developers. With built-in integrations and APIs, GitHub Enterprise Cloud features enterprise-ready, scalable CI/CD deployment automation with GitHub Actions, collaboration tools, natively-embedded application security testing, and the industry’s first AI-pair programmer, Copilot.

GitHub Enterprise Importer is a tried and tested migration tool, used by thousands of GitHub customers to migrate more than 700,000 repositories to the GitHub platform.

“With GitHub Enterprise Importer, we were able to migrate hundreds of repos from BitBucket Server to GitHub Enterprise up to 70% faster than we could have otherwise.” said Chris Grassi at PG&E for BBS.

To migrate a repository, one needs to install extension for the GitHub CLI and then run the gh bbs2gh migrate-repo command. For more details, and to learn about GitHub tools for planning the migration and moving large numbers of repositories, one can visit “Migrating repositories from Bitbucket Server to GitHub Enterprise Cloud” in the GitHub Docs.

In addition to moving the repositories to GitHub with GitHub Enterprise Importer, one can also move their CI/CD pipelines to GitHub Actions with GitHub Actions Importer - a migration tool that helps to plan, forecast, and automate CI migrations. In addition to BitBucket and Bamboo, GitHub Actions Importer already supports migrations from Azure DevOps, CircleCI, GitLab, Jenkins, and Travis CI.

GitHub Actions Importer is especially designed to help organizations when manual migration is not feasible. For organizations with large and sophisticated infrastructure, CI migrations are often a manual and time-intensive endeavor. GitHub Actions Importer speeds up this process while minimizing cost and the potential for error. In fact, since its inception, GitHub Actions Importer has helped thousands of users evaluate and test the migration of nearly a quarter million pipelines.

GitHub Actions Importer uses a phased approach to simplify the migration process:

  1. Planning: In this phase, one can analyze the existing CI/CD usage to build a roadmap for the migration.
  2. Testing: Here, one can conduct dry-run migrations to validate that the converted workflows function the same as existing pipelines. GitHub Actions Importer supports unlimited iterations in this step to ensure any custom behavior is accurately encapsulated in the new GitHub Actions workflows.
  3. Migration: In this last phase, GitHub Actions Importer generates validated workflows and opens pull requests to add them to the GitHub repository. To finalize the migration, one should plan to review these workflows and migrate those constructs that could not be migrated automatically.
Artificial Intelligence GitHub DevOps Bamboo Top News Bitbucket Server