Jira Data Center End of Life (2029): Key Dates, Options and What to Do Now
Jira Data Center end of life is March 28, 2029. See every date, new Cloud prices, what migration tools skip and a quarterly plan. Start now.
Published Updated 12 min read

On this page
- Jira Data Center end of life: the key dates
- What changes on each date for Jira Service Management teams
- Your options: move to Atlassian Cloud or leave Atlassian
- What Atlassian's migration tools move, and what they don't
- Leaving Atlassian for another ITSM platform
- A backwards plan from March 28, 2029
- Jira Data Center end of life checklist
- Jira Data Center end of life FAQ
Jira Data Center end of life is March 28, 2029. On that date Data Center subscriptions, including Jira Service Management Data Center, expire and the products become read-only (Atlassian end of life page, as of 23 Oct 2026). New customers could no longer buy from March 30, 2026, and existing customers can buy licenses, apps and expansions only until March 30, 2028.
If you own a Jira Service Management Data Center service desk, you have two real choices: move to Atlassian Cloud or leave Atlassian for another ITSM platform. This guide covers the dates, the new Cloud prices, what Atlassian's migration tools move, and a quarter-by-quarter plan back from the deadline.
Jira Data Center end of life: the key dates
Atlassian announced the wind-down on September 8, 2025 (as of 23 Oct 2026).
| Date | What happens | Source (as of 23 Oct 2026) |
|---|---|---|
| December 16, 2025 | New Data Center apps can no longer be submitted to the Marketplace | Atlassian developer blog |
| March 30, 2026 | New customers can't buy Data Center subscriptions or Marketplace apps | Atlassian end of life page |
| June 2027 | Last month to buy Cloud Enterprise with a possible 10-20% first-year discount | Atlassian end of life page |
| March 30, 2028 | Last day for existing customers to buy subscriptions, apps and expansions | Atlassian end of life page |
| March 28, 2029 | End of life: subscriptions and Marketplace apps expire; products turn read-only | Atlassian end of life page |
In scope: Jira Software, Jira Service Management, Confluence and Crowd Data Center and their Marketplace apps. Bitbucket and Bamboo Data Center "will not end of life", and Jira Align is excluded (Atlassian, as of 23 Oct 2026).
What changes on each date for Jira Service Management teams
| Phase | You can | You can't |
|---|---|---|
| Now to March 30, 2028 | Renew, buy licenses and add agents. Run a free cloud migration trial | Buy as a new customer |
| March 30, 2028 to March 28, 2029 | Renew | Buy licenses, apps or expansions, so agent headcount can't grow |
| After March 28, 2029 | Read your data | Use the product, get updates, support or security fixes |
Source: Atlassian end of life page, as of 23 Oct 2026.
Atlassian says "You will not be able to use your Data Center products after your subscription is expired." Data stays readable, but no new security fixes ship, and Atlassian strongly advises against keeping the read-only product connected to the internet (as of 23 Oct 2026).
For a service desk, read-only means no new requests, approvals or SLA clocks. Your real deadline is earlier: cutover, reconciliation and hypercare must finish first.
Atlassian offers "extended maintenance for certain Data Center customers by exception after March 28, 2029" (as of 23 Oct 2026). Criteria and cost aren't public, so don't plan around it.
Your options: move to Atlassian Cloud or leave Atlassian
Atlassian's answer is Cloud: "99% of Atlassian customers are in cloud, or on a path there" (as of 23 Oct 2026). For an ITSM platform owner, every option now involves a migration, so this is the moment to ask whether Jira Service Management still fits.
| Option | Choose this if | Price signal (vendor page, as of 23 Oct 2026) | Watch out for |
|---|---|---|---|
| Jira Service Management Cloud (Service Collection) | JSM fits your processes and your engineering teams live in Jira | Standard $21.50, Premium $55.28 per agent/month; change and problem management from Premium | Automation and Assets allowances by plan; Assets migration needs Premium or Enterprise per Atlassian's migration doc |
| Atlassian Government Cloud or Isolated Cloud | You stayed on Data Center for FedRAMP, isolation or sovereignty rules | Not published | Atlassian calls Government Cloud FedRAMP Moderate authorized and Isolated Cloud single tenant; confirm feature parity |
| Another ITSM platform, such as ServiceNow ITSM or Freshservice | JSM no longer fits your CMDB, process depth or scale, or you want to rightsize | ServiceNow: custom quote, problem and change from ITSM Advanced. Freshservice: $19, $49, $99 per agent/month billed annually, problem and change from Pro | Atlassian's migration assistant only targets Atlassian Cloud; everything is mapped and rebuilt |
| Stay on Data Center until read-only | You need a bridge and treat old history as reference only | Renewals only after March 30, 2028 | No agent growth after 2028, no fixes after end of life |
On G2, Jira Service Management scores 4.3/5 from 986 reviews; ease of use is the most-cited pro, learning curve and complexity the most-cited cons (G2, as of 23 Oct 2026). If you are weighing a move away, our Jira to ServiceNow migration guide covers that pair.
Atlassian Cloud prices from October 13, 2026
Atlassian raised Cloud list prices for new purchases, renewals and upgrades from October 13, 2026 PT; earlier quotes keep the old price until they expire (Atlassian list-price FAQ, as of 23 Oct 2026).
| Service Collection plan | Per agent/month | Annual, 100 agents: before → now | Automation steps per user/month | Assets objects included |
|---|---|---|---|---|
| Standard | $21.50 | $19,700 → $21,000 | 3,000 | 5,000 |
| Premium | $55.28 | $51,000 → $55,000 | 6,500 | 50,000 |
| Enterprise | Contact sales | 1,000 agents: $396,500 → $436,000 | 9,500 | 500,000 |
Sources: Atlassian Service Collection pricing page and Cloud pricing tables, as of 23 Oct 2026.
Two costs a Data Center owner doesn't pay today. Extra automation is billed at $0.50 per 1,000 steps from December 3, 2026 (Atlassian automation docs, as of 23 Oct 2026), and extra Assets objects start at $0.02 per object per month (pricing page, as of 23 Oct 2026). Plan tier matters more: Atlassian's Assets migration guide says "You need to have a Jira Service Management Premium or Enterprise plan to migrate Assets", while the pricing page lists Assets from Standard. If Assets holds your CMDB, budget for Premium until Atlassian confirms otherwise. Our Jira Service Management pricing guide covers every plan and add-on.
Atlassian's migration incentives
- Cloud migration trial: free, matched to your user tier and remaining subscription, up to 12 months and 20,000 users; 60 days if fewer than 60 days remain. Trial data is not backed up (Atlassian support doc, as of 23 Oct 2026).
- Dual licensing and step-up credits: dual licensing "to avoid double paying", and a credit for the pro-rated value of unused Data Center maintenance for qualified customers (end of life page, as of 23 Oct 2026).
- FastShift: for 1,000 or more seats, "complimentary and included with your purchase of cloud" (Atlassian FastShift page, as of 23 Oct 2026).
The trial runs against your current subscription, so start it when your test migrations are ready, not when you first sign up.
What Atlassian's migration tools move, and what they don't
Atlassian's tool is the Jira Cloud Migration Assistant (JCMA), built only for moves to Atlassian Cloud. Our Jira Data Center to Cloud migration guide walks through running it.
| Moves | Not migrated: rebuild | At risk: check in test |
|---|---|---|
| Service projects, request types, queues, workflows, portal settings, approvals, reports | Services | SLA results and elapsed time (not documented) |
| SLAs, calendars, notification templates | Linked knowledge base articles, canned responses, mail handlers, issue collectors | Users who already have a cloud customer account get two accounts |
| Users, agents, groups, customers, organizations | Workflow functions and triggers; app custom fields | Assets: 20 objects per field per work item |
| Assets schemas, objects, attachments, object history | Assets imports, reports and automation | Archived Assets objects arrive non-archived |
| Automation for Jira flows | Outgoing webhooks, Send Web Request, Teams messages | All migrated flows arrive disabled |
Sources: Atlassian JCMA, Assets, automation and customer migration docs, as of 23 Oct 2026.
Three details trip up service desks:
- SLAs move as configuration, not proven history. Atlassian's Cloud KB says changing an SLA configuration recalculates all open issues, and "data loss can occur when SLAs are changed after their cycles have completed" (updated June 25, 2026). Freeze SLA edits until reconciliation is signed off.
- Priorities differ. Atlassian says per-project priorities are "not available in Cloud", and SLA configuration can't be exported from one project into another.
- Customers aren't told. Atlassian sends no notifications to migrated customers, so plan your own portal and email message.
The rule holds for every migration. Workflows, automations, business rules, SLA definitions and running SLA timers are rebuilt and re-validated on the target, even when a tool copies their configuration.
Leaving Atlassian for another ITSM platform
Leaving Atlassian is an ITSM platform migration, not a cloud migration. JCMA doesn't apply, so incidents, requests, problems, changes, knowledge and CIs, plus the links between them, move into a different data model.
Start with Assets. Atlassian's Data Center object schema export includes objects and attachments, but not object history and comments, automation and import configurations, or connected Jira tickets (Atlassian docs, as of 23 Oct 2026). Ticket-to-CI links must be rebuilt in the target CMDB.
Then map states, the priority matrix, request types, comment visibility and SLA outcomes. For budgeting, see what an ITSM migration costs.
A backwards plan from March 28, 2029
There is no neutral public benchmark for migration length, so these quarters follow Atlassian's dates, not a typical project. Larger estates should start each step earlier. Teams on Microsoft's service desk face a nearer deadline; see our System Center Service Manager end-of-life guide.
| Quarter | Milestone | Why then (Atlassian, as of 23 Oct 2026) |
|---|---|---|
| Q4 2026 | Inventory projects, SLAs, automation, Assets, apps and email channels. Decide history scope. Model Cloud cost | New Cloud prices from October 13, 2026 |
| Q1 to Q2 2027 | Choose Atlassian Cloud or another platform, and the plan tier | Enterprise discount for purchases by June 2027 |
| Q3 to Q4 2027 | Map states, priorities, SLAs, groups and CIs. Start the cloud migration trial. Test migrations and user acceptance testing | Atlassian strongly recommends a trial run |
| Q1 2028 | License every agent you need until cutover | Last date to buy or expand: March 30, 2028 |
| Q2 to Q4 2028 | Freeze window, cutover with delta sync, reconciliation, go/no-go, hypercare | Atlassian advises read-only mode on the source first |
| Q1 2029 | Final backup, archive access, take Data Center offline | End of life March 28, 2029 |
Before each go/no-go gate, confirm what a test migration should prove: counts, relationships, attachments and SLA results.
Jira Data Center end of life checklist
- Confirm your existing-customer status, renewal date and trial window.
- List every service project, request type, queue, SLA and calendar.
- List automation flows and flag unsupported actions.
- Count Assets objects and confirm the plan Assets migration needs.
- Find a target equivalent for every Marketplace app.
- List mail handlers, canned responses and linked knowledge articles to rebuild.
- Decide which history moves and which is archived.
- Choose your target and model cost at October 2026 prices.
- Run an end-to-end test migration, user acceptance testing and SLA checks.
- Plan the freeze window, delta sync, go/no-go, reconciliation and hypercare.
- Back up your data and keep the read-only instance offline.
Facts checked October 23, 2026 from Atlassian Data Center end of life, Atlassian list-price FAQ, Atlassian Service Collection pricing and Jira Cloud Migration Assistant docs. No vendor paid for this article. How we research
Jira Data Center end of life FAQ
Is Jira Data Center going away?
Yes. Jira Software, Jira Service Management, Confluence and Crowd Data Center reach end of life on March 28, 2029, when subscriptions expire and products turn read-only (Atlassian, as of 23 Oct 2026). Bitbucket and Bamboo Data Center continue. Extended maintenance is offered only by exception, so plan to be live elsewhere first.
What happens to my Jira Service Management data after March 28, 2029?
It stays readable, but Atlassian stops updates, support and security fixes (as of 23 Oct 2026). Agents can look up old tickets, but no new requests, approvals or SLA clocks run. Atlassian advises against keeping the read-only product online, so back up your data and decide how long audit needs the archive.
Can I still buy Jira Service Management Data Center licenses?
Only as an existing customer, meaning your organization paid for Data Center before March 30, 2026. Existing customers can buy licenses, apps and expansions until March 30, 2028, then only renew until end of life (Atlassian, as of 23 Oct 2026). License every agent you will need before the 2028 cutoff.
Does the Jira Cloud Migration Assistant migrate SLAs?
Atlassian lists SLAs and calendars as migrated (as of 23 Oct 2026), but doesn't say whether elapsed time on open tickets or results on closed tickets carry over. Its Cloud KB warns that later SLA configuration changes recalculate open issues. Test breached, paused and running SLAs in your test migration and freeze SLA edits until sign-off.
How long does a Jira Data Center migration take?
There is no neutral public benchmark. Atlassian says it "can't provide an exact estimation of downtime" and recommends a test migration to work it out (as of 23 Oct 2026). For 1,000 or more seats, Atlassian says FastShift can cut timelines from 12 to 16 months to 2 to 6 months, a claim for Cloud moves only. Apps, Assets, automation rebuilds and history scope drive yours.
Written by
Ayush BothraFounding Member, MigrateX
Ayush writes about ITSM platforms, pricing and what it takes to move a service desk to a new platform without losing its history.


