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.
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.
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.
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.
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. |
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 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:
It does not move:
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.
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.
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.
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.
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.