Quick answers
- When does Atlassian Data Center reach end of life?
- 28 March 2029 at 23:59 Pacific Time, which is 29 March 2029 in Australia. Data Center licences and their associated app licences then expire and the products become read-only.
- Which products are affected?
- Jira Software, Jira Service Management, Confluence and Crowd Data Center, plus Data Center mobile apps, Atlassian Data Center apps and Marketplace Data Center apps. Bitbucket and Bamboo continue under a new licence. Jira Align Data Center is not included.
- Do we have to migrate by March 2028?
- No. After 30 March 2028 you can't buy new subscriptions, expansions, upgrades or Data Center apps, but you can keep renewing your current users and products up to 28 March 2029.
What is changing in Atlassian Data Center?
At end of life, support and bug fixes stop, licences expire and the products become read-only. Until then, Atlassian continues technical support, fixes for critical vulnerabilities and the connectors to Cloud, winding support down in phases.
Read-only is not a safe archive. Atlassian strongly advises against running a read-only instance while it's connected to the internet and recommends backing up your data. Content that must stay reachable needs a hosting, access and retention decision before the migration is scoped.
Two milestones have passed: new Data Center app submissions closed on 16 December 2025, and sales to new customers stopped on 30 March 2026 (17 December and 31 March in Australia).
Bitbucket and Bamboo: the products continue, your licence changes
Atlassian says "Bitbucket and Bamboo Data Center will not end of life and will continue beyond the Data Center end of life in 2029". The route is the Bitbucket Hybrid License: one subscription for Bitbucket and Bamboo Data Center plus Bitbucket Cloud with Pipelines, with no data transfer, from early 2027 for existing Bitbucket or Bamboo customers. Pricing and an exact date aren't published yet.
Your current licence still ends. Existing licences run to 28 March 2029; after that, both products are sold only through the Hybrid License, and without it they become read-only and users can't push code.
One inconsistency: Atlassian's end-of-life FAQ still lists Bamboo as affected. Plan on the Hybrid License or the documented move to Bitbucket Pipelines, and confirm the terms with Atlassian.
When does it affect your organisation?
Three dates matter; whichever binds first is your deadline. Each cutoff is 23:59 Pacific Time, so Australian dates are one day later.
| Deadline | Atlassian's date | Australian date | What changes |
|---|---|---|---|
| Your subscription expiry | Your expiry date | Your expiry date | Without renewal, data stays read-only, without updates or support |
| Purchasing cutoff | 30 March 2028 | 31 March 2028 | No new subscriptions, expansions, upgrades, user tiers or Data Center apps; renewals continue |
| End of life | 28 March 2029 | 29 March 2029 | Support ends, licences expire, products become read-only; renewals prorated to this date |
Which deadline binds you?
Renewals don't stop in 2028, but "renewals cannot extend beyond March 28, 2029", prorated to that date. What the 2028 cutoff removes is growth.
- Adding users after March 2028You are bound by the 2028 purchasing cutoff.
- Letting a subscription lapse in mid-2027You are read-only from mid-2027.
- Stable headcount, renewing each yearYou can run to 2029.
- Needing more timeExtended maintenance and multi-year extensions exist by exception, at extra cost, with no published criteria.
What choices do you realistically have?
Atlassian's options page sets out three, and is plain about staying: "Ultimately, in order to continue using Atlassian products, you will need to move to cloud."
- Migrate to Atlassian CloudMigration assistants move data, not every customisation; the Migration Program helps plan and test.
- Move Bitbucket and Bamboo to the Hybrid LicenseRepositories and build plans stay put, with Bitbucket Cloud alongside: in our view, for teams keeping code self-managed.
- Stay on Data Center for nowLegitimate as a dated plan: renew within the 2029 cap, expect no growth after 2028, keep migrating. See licensing.
- Use Rovo before you moveAtlassian's connectors bring Data Center content into Rovo, with a Cloud plan. See our Rovo page.
What should you investigate before committing to migration?
Six decisions shape a migration's scope, cost and timing. Settle them before you fix a cutover date.
| Decision | Establish | Why it matters |
|---|---|---|
| Licences and purchasing | Each expiry and renewal owner; growth after March 2028; your Cloud plan | Sets your deadline and budget timing. Cloud migration trials last as long as your Data Center subscription |
| Marketplace apps | Essential, replaceable or removable; each vendor's migration path | App data migrates automatically only with a vendor path; otherwise manual, rebuild or replace. Use "Assess your apps" |
| Scripts, workflows and integrations | What needs redesign rather than migration | Custom notifications and events don't migrate; user macros become Forge or Connect apps; integrations are re-pointed |
| Identity, SSO and provisioning | What replaces Crowd; SSO, provisioning and domains to verify | SSO and SCIM need Guard Standard, included in Cloud Enterprise; verified domains make managed accounts |
| Data scope and retention | What migrates, is archived, retained or deleted | Archived projects migrate unless you scope them out; leave unused projects and stale spaces behind |
| Test migrations and cutover | A full test migration, sign-off criteria, cutover window and fallback | Gaps are cheaper in a test; acceptance criteria turn "it migrated" into "it works" |
Migration readiness check
Any line you can't yet confirm with confidence is the place to start. Prefer a partner? See our Cloud migration service.
- We know every subscription's expiry date and renewal owner.
- We know whether we'll add users, products or apps after 30 March 2028.
- Every Marketplace app is marked essential, replaceable or removable, with its Cloud path confirmed.
- We know which scripts, workflows, notifications, macros and integrations must be rebuilt.
- We've decided sign-in and provisioning in Cloud, including what replaces Crowd.
- We've agreed what data migrates, and who signs off a test migration.
Frequently asked questions
Do our Marketplace apps end at the same time?
Yes, for affected products: subscriptions and their associated Marketplace apps expire on the end-of-life date, and Data Center app sales to existing customers end on 30 March 2028. Whether each app has a Cloud version and a migration path is a question for its vendor.
Does Atlassian offer anything to help with the cost of moving?
Yes. Atlassian lists incentives: a possible first-year discount on Cloud Enterprise bought by June 2027, migration trials and step-up credits for unused maintenance. Larger customers can get dual licensing, "for up to 1 year at a 100% discount", or FastShift for 1,000+ seat moves within two to six months. Atlassian confirms eligibility.
We still run Atlassian Server. Does this apply to us?
Server support ended earlier: "As of February 15, 2024 PT, Server products are no longer supported". Jira and Confluence Server customers get a 60-day Cloud migration trial even where maintenance has expired, and Bitbucket and Bamboo Server customers are eligible for the Hybrid License.
Sources and currency (1), last reviewed 18 October 2026
- Atlassian's migration and end-of-life timeline, Cloud transformation options, Bitbucket Hybrid License, Cloud licensing and purchasing FAQs, FastShift, Server end of support, migration assistant documentation and Guard pricing pages, reviewed on 18 October 2026.
Why might Senzo's practical experience help?
Senzo is an Atlassian Platinum Solution Partner. Atlassian publishes the dates and tools; it can't tell you how your configuration will behave in Cloud.
- The binding dateWe read your subscriptions and growth plans against the three deadlines.
- What needs redesignWe separate the apps, scripts and integrations that need redesign from those that simply move.
- Sign-offWe plan identity, data scope and acceptance criteria with the people who sign off cutover.
None of this needs a decision to migrate this quarter.
It needs a clear view of where you stand.