Migrating from Bitbucket Data Center to Bitbucket Cloud marks a significant shift in how organizations manage their development operations. Bitbucket Cloud Migration Assistant (BCMA) plays a pivotal role in facilitating this transition, automating many aspects of the migration process. However, it’s crucial to recognize the limitations of BCMA and understand that certain components require manual migration or alternative strategies to ensure a successful migration.
This blog post series delves into some elements not covered by BCMA and how this comprehensive guide series provides solutions to ensure that more parts of the development environment are transferred during the migration process.
Understanding BCMA Limitations
While BCMA automates the migration of many aspects of your Bitbucket Data Center environment, including repositories, users, and projects, there are several critical areas it does not cover.
These limitations could lead to significant hurdles if not addressed, potentially disrupting your team’s workflow or even resulting in data loss. Recognizing these gaps, I have put in place a series of scripts designed to fill some parts where BCMA leaves off.
Repository Git information
- Migrating the link or association of forked repositories
- Content stored in Git LFS – ⭐️ Covered in this post series.
- Git submodules
- Pull request attachments
- Repos with duplicate names
- Open changes on local machines
- Extra large repos (max is currently 10GB)
- Personal repos – ⭐️Covered in this post series.
Repo settings
- Add default reviewers – ⭐️ Covered in this post series.
- Branch permissions
- Managing webhooks
- Merge checks
- Build statuses
Project data
- Settings
- Permissions – ⭐️Covered in this post series.
Users
- Groups – ⭐️ Covered in this post series.
- Permissions – ⭐️ Covered in this post series.
- Settings
- Avatars
- Passwords
- Timezones
- SSH keys
- App passwords
Source: What gets migrated with Bitbucket Cloud Migration Assistant | Atlassian Support
How This Series Helps
This Bitbucket Migration Series: From Data Center to to Cloud is tailored to address each of the aforementioned gaps, providing step-by-step instructions and scripts to ensure a seamless transition.
- Post 1/6 – Migrating Git Large File Storage (LFS) to Bitbucket Cloud: Discover how to migrate large files efficiently, ensuring your repositories maintain their integrity in the cloud.
- Post 2/6 – Updating Repository References to Bitbucket Cloud: Guide you through updating repository references to point to your new cloud environment
- Post 3/6 – Migrating Reviewer to Bitbucket Cloud: Explore the process of migrating reviewer settings, preserving critical aspects of your code review and approval workflows.
- Post 4/6 – Migrating Groups and Memberships to Bitbucket Cloud: The fourth post details the process of transferring group data and memberships, maintaining your organizational structure and access controls in the cloud.
- Post 5/6 – Migrating Repository Permissions to Bitbucket Cloud: Ensure your repository permissions are accurately replicated in the cloud, safeguarding your project’s security and collaboration policies.
- Post 6/6 – Migrating Personal Repositories to Bitbucket Cloud: The final post in this series ensures that individual work and custom projects are not left behind, detailing how to transfer personal repositories to the cloud.
I also wrote the post Bitbucket Data Center vs Cloud – Detailed Comparison, this post can help you understand the differences between Bitbucket Server/Data Center and Cloud. Some functionalities, despite being similar, may have specific differences in operation, and this can affect the way the team works.
For the scripts mentioned in this series, you can find the repository here.
I hope these posts will be invaluable to your migration efforts!
Atlassian Expert Tips 