Atlassian is winding down its Bamboo Data Center. New license sales end this year; full end-of-life is March 28, 2029. Plenty of runway, but if you've run Bamboo for 5-10 years, the migration is bigger than picking a new tool.
The common mistake is recreating every build plan exactly as it was. Feels safe. What you're really doing is dragging a decade of dead steps and workarounds into a clean system.
Audit first, compare tools second. Write down:
Build plans and jobs (flag anything nobody's run in a year)
Agent configs
Deployment projects
Artifact storage and retention rules
Shared credentials and variables
Repo integrations
Custom scripts and plugins
Jira/Bitbucket hooks
Compliance and security requirements
Most teams find a big chunk of that is obsolete.
Real example from the writeup: a Dutch company with 15+ years on Bamboo, ~1,000 devs, ~200 agents, and one of the biggest Bamboo deployments out there. They moved to TeamCity and deliberately did not migrate the old config. Rebuilt from scratch in Kotlin DSL, product line by product line, cutting legacy steps as they went. Their largest app (27M LOC) went from a 1h+ full rebuild to about 6 minutes. Roughly 90% off, most of it from cutting cruft rather than any single feature.
Why Bamboo folks tend to look at TeamCity:
Agent-based build architecture (familiar model)
Self-hosted, cloud, or hybrid
Config-as-code via Kotlin DSL, covering the ground Bamboo Specs used to
Strong integrations across source control, issue tracking, and deployment
Practical tip: run both systems in parallel for a while. Migrate one pilot pipeline, compare outputs, and move the critical stuff once you trust it. Big-bang cutovers are where migrations go to die.
Full guide with the audit steps and phased approach: https://blog.jetbrains.com/teamcity/2026/06/bamboo-end-of-life/
Migration guidelines: https://www.jetbrains.com/help/teamcity/cloud/bamboo-to-teamcity-migration-guidelines.html
Happy to answer questions if anyone's mid-migration or scoping one.