Yes, we recommend migrating to Bitbucket Cloud before March 28, 2029, unless compliance, data sovereignty, or an air-gapped environment means your code has to stay self-managed. The date matters because Bitbucket Data Center is sold only through the Bitbucket Hybrid License after it, and Atlassian says an instance that has not moved to that license switches to read-only, so your developers can no longer push code.
That is a licensing deadline, not an end of life. Your decision is between two real paths, and both take planning.
What happens to Bitbucket Data Center on March 28, 2029
Bitbucket Data Center is not on Atlassian's end of life list. That list covers Jira, Jira Service Management, Confluence, and Crowd Data Center. Atlassian says Bitbucket Data Center continues past 2029. What changes is how you can license it.
- Early 2027: existing customers can upgrade to the Bitbucket Hybrid License. Atlassian has not published the exact date; its Hybrid License page has a form for notice.
- Until March 28, 2029: existing Bitbucket Data Center licenses remain available.
- After March 28, 2029 at 23:59 PST: Bitbucket Data Center is sold only through the Hybrid License. Without it, the application switches to read-only and users can no longer push code.
Your own renewal date can arrive first. Bitbucket Data Center is an annual subscription, and when a license expires users can't push code and access to support ends. Check that date before you build a timeline.
Bamboo Data Center is on the same licensing path. We cover it in our Bamboo Data Center guide. If you also run Jira or Confluence Data Center, those do reach end of life on March 28, 2029, and they have no Hybrid License path, so decide the two moves together.
What the Bitbucket Hybrid License is
- What it covers: Bitbucket Data Center, Bamboo Data Center, and Bitbucket Cloud with Pipelines, under one subscription.
- Who can get it: only existing Bitbucket Data Center, Bitbucket Server, Bamboo Data Center, and Bamboo Server customers.
- How you get it: you can renew to it when your current subscription ends. Your environments stay where they are, and no data transfer is required.
- What it is not: one merged product. Atlassian says Data Center and Cloud remain separate product experiences. It plans tighter integration and says more details will come, so don't build a plan on features it hasn't described yet.
As of this update, the Hybrid License page does not say which Bitbucket Cloud plan is included, or how support and Marketplace apps work on the license after 2029. Ask your Atlassian account team and get the answers in writing.
When staying self-managed is reasonable
Atlassian names three reasons to keep Bitbucket and Bamboo Data Center: compliance, data sovereignty, and air-gapped requirements. Staying also means you keep running the servers, upgrades, and backups yourself. Use this table as a first pass.
| Your situation | Likely path | Why |
| Code must stay in your own environment for compliance, data sovereignty, or air-gapped reasons | Hybrid License | These are the cases Atlassian names for it. |
| You need data residency in Bitbucket Cloud | Confirm first | Atlassian's comparison page still lists it as coming in 2026. Check the Bitbucket Cloud roadmap before you commit. |
| Critical builds can't be recreated or moved without downtime | Phase the move | Atlassian recommends a phased or hybrid approach for these builds. |
| You have no self-hosting requirement | Bitbucket Cloud | You stop running the application, and you get the Cloud features below. |
| You are not an existing Bitbucket or Bamboo customer | Bitbucket Cloud | The Hybrid License isn't offered to you. |
What changes in Bitbucket Cloud
Atlassian lists these as Cloud capabilities that Data Center does not have: Bitbucket Pipelines built in, Atlassian cloud runners, a built-in Jira UI, commits sent to Jira Service Management for change review, and AI code review and pull request summaries. Rovo Dev has separate pricing and packaging, so scope it separately. Atlassian also performs upgrades for you.
Some things work differently, and Atlassian's administration guide lists them:
- The workspace administrator role replaces System administrator.
- Repository names must be unique within a workspace or project.
- You can't change the 10 MB upload limit. Git Large File Storage (LFS) is available, with storage limits by plan.
- Backups are for disaster recovery. They can't restore a repository a user deleted.
- IP allowlisting, required two-step verification for private repositories, and enforced merge checks need a Premium plan.
What the Bitbucket Cloud Migration Assistant moves
The Bitbucket Cloud Migration Assistant is Atlassian's recommended tool. It is free, and it needs Bitbucket Server 7.0 or later. According to Atlassian's list, it moves:
- Git data: branches, tags, and commits.
- Pull requests: title, description, status, code diff, comments, tasks, authors, and reviewers. Nested comments and tasks get flattened.
- The users you select.
It does not move:
- Git LFS content, which you migrate manually afterward.
- Fork links. A fork becomes a normal repository, so merge open pull requests from forks first.
- Submodule links, which you update yourself.
- Pull request attachments and the activity feed.
- Personal repositories, or repositories with duplicate names, until you fix them.
- Default reviewers, webhooks, merge checks, and build statuses.
- User passwords, SSH keys, app passwords, avatars, and settings.
- Marketplace apps and their data. Check with each app developer.
Atlassian's pages differ on some of this. The list above and the migration methods page give different maximum repository sizes, and they disagree on whether permissions, group memberships, and branch permissions move. Don't plan around either version. The assistant has a pre-migration report under Review and Migrate; run it against your own data in a test migration.
The assistant lets you choose projects and repositories, so you can migrate in phases. We weigh that choice in phased versus single cutover; that guide is written for Jira, but the tradeoffs are worth reading for code too. For the step-by-step work, use our Bitbucket migration playbook.
What you rebuild for CI
Treat CI as a rebuild, not a copy. Bitbucket Pipelines requires your repositories to be in Bitbucket Cloud, and the assistant moves code, history, and pull request data, not build plans. The separate tool is the Bitbucket Pipelines Importer, which translates Bamboo YAML specs and Jenkins configuration files into Pipelines YAML. Think of its output as a baseline.
- Bamboo: the importer reads only exported YAML specs, so Java Specs don't convert. Unrecognized third-party apps, secrets, and self-hosted runners need manual work. Atlassian says to plan manual follow-up on every migrated plan, even when the importer reports success.
- Jenkins: the automated tool supports declarative pipelines only, not scripted ones, and it marks plugins it can't convert. Atlassian also describes Jenkins as a tool you can connect to Bitbucket Cloud, so Pipelines doesn't have to be a day one change.
- Builds behind a firewall: Pipelines supports self-hosted runners for restricted environments.
- Critical Bamboo builds: the atlassian/bamboo-trigger-build pipe can keep those steps in Bamboo for a while as you move simpler steps first.
Webhooks and build statuses don't migrate, so reconnect anything that depends on them. See our Bamboo guide for the plan-by-plan detail, and our Bitbucket page for how we approach branch and access models.
Decide who holds access before the move
Atlassian recommends setting up user provisioning and single sign-on before you migrate users. It also says you can do this afterward and reach the same result. We would still decide first, because these choices shape the workspace you migrate into. Our position: Okta is the source of truth for identity, and Atlassian Guard supplements the controls on the Atlassian side.
- Workspace: Atlassian recommends creating it in Atlassian Administration, and says groups can only migrate to workspaces there. Wikis and the issue tracker are disabled in those workspaces, so export what you need. Personal workspaces can't be linked to Atlassian Guard.
- Email addresses: Cloud identifies each user by email, and every address must be valid and unique. Fix these first.
- SSO: Atlassian's checklist names Atlassian Guard Standard, and its administration guide also names an Enterprise plan. SSO credentials aren't valid for Git operations, and SSH keys and app passwords don't migrate, so every developer needs new Git credentials. Atlassian's pre-migration checklist still names app passwords, while its notice said they would stop working on June 9, 2026. Check the API tokens page before you write instructions.
- SCIM: it needs Atlassian Guard Standard, with a limited Google Workspace exception. Provisioning can create, update, and deactivate accounts, but group sync is not yet available for Bitbucket. Groups are managed in the Bitbucket UI or through APIs, so name who owns them.
- Who holds access: clean up inactive users before you migrate. Their permissions don't move. Choose your workspace administrators deliberately, since that role has the highest level of permissions.
- What holds access: list the scripts and CI tools that hold credentials today. They need new credentials, and each one needs an owner. We cover this in identity debt in a migration.
Next step
Talk to an architect about the move. Bring your renewal date, your list of CI plans, and your identity provider. We will work through which path fits you and what has to be rebuilt.