Bamboo migration guide: dates, official tools, and a plan
Atlassian Bamboo Server is end-of-life, standalone Data Center is closed to new customers and expires in 2029, and after that Bamboo survives only inside a Bitbucket bundle, with no cloud edition to fall back on. This is a vendor-neutral guide to the timeline, every official migration guide and converter, how to choose a target, and how to move without breaking your builds.
Bamboo Server lost support in Feb 2024. Standalone Data Center closed to new customers on March 30, 2026 and expires on March 28, 2029; after that Bamboo continues only inside the Bitbucket Hybrid License for existing customers. There's no cloud Bamboo. GitHub and Atlassian ship automated converters, TeamCity, GitLab and Buildkite publish written guides. Inventory your pipelines, pick a target that matches your hosting and Git setup, rebuild your busiest pipeline first, validate in parallel, then port the rest. Need the full options comparison? See the Bamboo alternatives page.
The timeline
The dates that matter
The key Bamboo life-cycle milestones, from Atlassian's own licensing pages and the Bamboo release schedule.
Sources: Ascend announcement · Atlassian Data Center EOL FAQ · Bamboo licensing FAQ · Bitbucket Hybrid License · Bamboo release EOS policy · Bamboo pricing
Official paths
Every official "migrate from Bamboo" guide and converter
Checked vendor by vendor in October 2026, primary sources only. Five vendors publish something; three of those ship a tool. Both shipped converters take the YAML Specs you export from the Bamboo UI, not Java Specs, and every one of them leaves triggers, permissions and third-party plugin tasks for a manual pass.
| Target | What they publish | Automated converter | Input | Covers and gaps |
|---|---|---|---|---|
| GitHub Actions | Migrating from Bamboo with GitHub Actions Importer (docs; public beta since May 2023) | ✓ gh actions-importer: audit, dry-run, migrate | Bamboo YAML Specs (Bamboo 7.1.1+) | Build plans and deployment projects; opens a PR with the workflow. Triggers become comments, permissions and custom artifact storage are not converted. |
| Bitbucket Pipelines | How to migrate from Bamboo to Bitbucket Pipelines (docs; tool GA June 29, 2026) | ✓ Bitbucket Pipelines Importer (open source, Docker image) | Bamboo YAML Specs | audit, forecast (minutes and runner size) and migrate; build plans, deployment projects, full-instance mode, custom transformers for third-party plugins. Atlassian stresses a manual follow-up on every plan. |
| TeamCity | Bamboo to TeamCity migration guidelines (docs, updated July 2026) and the JetBrains EOL post | in development (teamcity migrate command) | YAML and Java Specs, side-by-side Kotlin DSL examples | Concept map (plan to build chain, stage to composite build, job to build configuration, task to step), variables, artifacts, deployments, secrets, verification. |
| GitLab CI/CD | Migrating from Bamboo (docs) and a 2023 blog post | ✗ | YAML or Java Specs exported from the UI, hand-translated | Variables, plans, stages, jobs, images, artifacts, deployments and triggers mapped to .gitlab-ci.yml. |
| Buildkite | Migrate from Bamboo (docs) | ✗ (Buildkite's converter covers other CIs, not Bamboo) | Manual | Projects, plans and deployments to pipelines; tasks to command steps; agent capabilities to agent tags. |
| Buddy | None yet | ✗ | Manual, visual editor | Plans are rebuilt in the pipeline editor; the concept map below applies. Build scripts, test commands and artifacts port as they are. |
| CircleCI, Jenkins, Harness, Azure DevOps, AWS, Semaphore, Codefresh, Octopus, Google Cloud Build | None | ✗ | Manual | No Bamboo-specific guide as of October 2026. Harness and CloudBees document running Bamboo plans from their products, which is an integration, not a migration. Octopus retired its Bamboo add-on in December 2025. |
If your plans live as Java Specs, export YAML Specs from the Bamboo UI first; that is the only input the GitHub and Atlassian converters accept. Run the converter's audit step before deciding anything: it lists the plugin tasks and triggers that will not port.
Step 0: pick a direction
How to choose your target
The biggest decision is hosting model. Match it to your constraints first, then the details get easier.
Want off the server entirely
A managed cloud CI/CD removes patching and upgrades. Buddy is a low-friction, visual option with a free tier; Bitbucket Pipelines fits Atlassian shops; GitHub Actions and GitLab CI fit teams already on those hosts.
Must stay self-hosted
If on-prem is mandatory (regulatory, air-gapped), TeamCity is the closest like-for-like server (free for 3 agents) and Jenkins is the free open-source route.
Tied to a Git ecosystem
If your code already lives on GitHub or GitLab, their native CI is the path of least resistance. If you're committed to Jira and Bitbucket, Bitbucket Pipelines keeps you in one vendor.
Watch the pricing model
Bamboo bills by build agent (concurrency). Tools price differently (per seat, per minute, or credit-based), so model your real build volume before committing, not just the sticker price.
The migration
A five-step plan that doesn't break your builds
Migrating off Bamboo is a rebuild, not a lift-and-shift. Do it incrementally and keep Bamboo running until the new setup is proven.
Inventory your pipelines
List every plan, stage, job, deployment project, agent, integration and variable. Rank pipelines by how often they run; that's your migration order.
Pick a target tool
Decide cloud vs self-hosted first, then factor in your Git host and pricing model. The alternatives comparison lays out the trade-offs side by side.
Rebuild your busiest pipeline first
Recreate one high-traffic pipeline in the target tool: run the official converter first where one exists (GitHub, Bitbucket Pipelines), otherwise YAML for most tools or the visual editor in Buddy. Proving the hardest real case first de-risks the rest.
Validate in parallel
Run the new pipeline alongside Bamboo and compare artifacts, test results and deploy outcomes. Only cut over once the new build is trusted.
Migrate the rest, then decommission
Port the remaining pipelines in priority order, move secrets and integrations, update your runbooks, then retire the Bamboo server.
Translation table
Mapping Bamboo concepts to a modern pipeline
Names differ between tools, but the building blocks line up. A rough mental model for what becomes what.
| Bamboo | Typical equivalent |
|---|---|
| Plan | Pipeline / workflow |
| Stage | Stage / job group |
| Job & tasks | Job / step / action |
| Deployment project | Deployment pipeline / environment |
| Remote/elastic agent | Runner / cloud-hosted executor |
| Plan variables | Pipeline variables / secrets |
| Linked repository & triggers | Git connection + push/PR triggers |
Exact mapping depends on the target tool, so treat this as a starting point, not a guarantee.
Common questions
Bamboo migration: common questions
When does Bamboo reach end of life?
Bamboo Server reached end of support on February 15, 2024. Standalone Bamboo Data Center closed to new customers on March 30, 2026; existing customers can buy or expand until March 30, 2028, and standalone subscriptions expire on March 28, 2029 (Atlassian Data Center EOL FAQ). Atlassian has since stated Bamboo Data Center itself will not end of life: beyond 2029 it is available only inside the Bitbucket Hybrid License, offered to existing customers from early 2027 (Bamboo licensing FAQ). There is no cloud edition of Bamboo.
What should Bamboo users migrate to?
If you want to stop running a CI/CD server, a managed cloud tool like Buddy is the lowest-friction move. If you must stay self-hosted, TeamCity or Jenkins are the closest fit. If you are committed to Atlassian, Bitbucket Pipelines is the natural path, and if your code is on GitHub or GitLab, their native CI is easiest. See the full comparison.
Can I automatically convert Bamboo plans to another tool?
Partly. GitHub Actions Importer (public beta since May 2023) and Atlassian's Bitbucket Pipelines Importer (GA June 2026) are official converters; JetBrains has a TeamCity migrate command in development. Both shipped tools take Bamboo YAML Specs exported from the UI, not Java Specs, and produce a baseline config that still needs review: triggers, permissions and third-party plugin tasks are the usual gaps. GitLab, TeamCity and Buildkite publish written mapping guides without a tool. Everything else, including Buddy, CircleCI and Jenkins, means rebuilding pipelines by hand; your build scripts, test commands and artifacts port as they are.
How long does a Bamboo migration take?
It depends on pipeline count and complexity, but most teams plan in weeks rather than days. A practical approach is to migrate the busiest pipeline first to prove the model, run it in parallel with Bamboo for validation, then port the remaining pipelines in priority order before decommissioning the server.