Jira Service Management Data Center End of Life: Your Options Before 2029
Atlassian is shutting down Data Center, its last self-managed edition, and Jira Service Management Data Center is included. If your support or IT team runs JSM on your own servers, you have a deadline, and you also have a decision to make.
Atlassian's answer is simple: move to Atlassian Cloud. For some teams that's the right call. For others, the end of Data Center is a good time to ask whether the help desk needs to be in Jira at all.
I'll cover the dates, what changes at each one, your three realistic options, and a checklist for moving your help desk if that's the route you choose.
The Data Center end of life timeline
These dates come from Atlassian's Data Center end of life page.
- February 15, 2024: Server reached end of support. Data Center became the only self-managed edition.
- March 30, 2026: New customers can no longer buy Data Center subscriptions or Data Center Marketplace apps.
- March 30, 2028: Existing customers can no longer buy new Data Center subscriptions, expansions, or Marketplace apps.
- March 28, 2029: Data Center subscriptions and apps expire. Jira Service Management Data Center becomes read-only.
Until March 28, 2029, Atlassian continues to provide technical support, fixes for critical security vulnerabilities, and connectors to Atlassian Cloud. Renewals can't run past the end of life date. A 12-month renewal that would cross it is prorated.
Atlassian says it will offer extended maintenance "by exception" for some customers who can't move in time. Plan as if that exception won't apply to you.
Confluence Data Center has the same end of life date. If your JSM knowledge base lives in Confluence, it's on the same clock.
What "read-only" means for a help desk
A read-only help desk is not a help desk. After March 28, 2029 your agents can't reply to tickets, your email channels stop creating requests, and your automation stops running. Your history stays visible, but your team can't work.
So the real deadline is earlier. You need time to choose a platform, migrate, train agents, and run in parallel for a while. For most teams, that means deciding during 2027.
Your three options
1. Move to Atlassian Cloud
This is the path Atlassian is building for, with migration tooling, cloud migration trials, and credits for unused Data Center maintenance.
It makes sense when:
- Your service desk is tightly linked to Jira Software projects and engineering workflows.
- You rely on Assets (CMDB), change management, or other ITIL processes.
- Your security and compliance teams are comfortable with Atlassian's cloud, or one of its government or data residency options.
The trade-off is control. Your data moves to Atlassian's infrastructure, you move to per-agent cloud pricing, and some features you have on Data Center may sit on higher cloud plans. Check Atlassian's current cloud pricing for your agent count before you assume the cost is the same.
2. Stay on Data Center until the deadline
You can keep renewing until March 28, 2029. That buys time, but it doesn't change the outcome. You'll get critical security fixes, but the product won't move forward, and Marketplace apps you depend on may stop being maintained before the end.
This is a reasonable plan only if you use the time to choose and test where you're going next.
3. Move your help desk to a different platform
Many teams adopted JSM because they already owned Jira, not because they needed an ITSM platform. If your team mostly handles email, portal requests, and internal questions, you're paying for, and administering, a lot of process you don't use.
The end of Data Center is a natural point to separate the help desk from the developer tools. Engineering can follow Jira to the cloud. Support can pick the tool that fits support.
Questions to ask before you decide
- Where does your support data need to live? If policy, regulation, or customer contracts require your own servers, Atlassian Cloud is off the table for that data.
- How much of JSM do you really use? List the request types, queues, SLAs, and automation rules your team uses every week. Compare that list with what you'd pay for in the cloud.
- Who maintains it today? If simple changes need a Jira administrator, count that time as part of the cost.
- How tightly is support linked to engineering? Linking a ticket to a Jira issue is easy to keep with an integration. Running your support workflow inside Jira is a different requirement.
- What happens to the knowledge base? If it's in Confluence Data Center, it needs a new home too.
Where HelpSpot fits
HelpSpot is a help desk built for support and IT teams that work mostly by email and web portal. It's one of the few that still offers a real self-hosted option.
- Self-hosted, cloud, or both. Run it on your own Linux or Windows servers with MySQL, MariaDB, or SQL Server. See the full requirements. If you'd rather not host it, US Cloud and EU Cloud are available too.
- One price for every hosting option. Self-hosted costs the same as cloud: one annual price based on team size, from $899/year for 3 agents and $2,199/year for 10 agents. Every feature is included. See pricing.
- Built for support, not ITIL. Ticketing, automation, reporting, a knowledge base, and a customer portal, without schemes, screens, and permission matrices to manage.
- Help moving in. Our team helps you import your ticket history and get configured, and onboarding is included.
HelpSpot isn't the right fit for everything. If you need a CMDB, formal change management, or a service desk that lives inside your engineering workflow, stay in the Atlassian ecosystem. If you need a dependable help desk that you can still run on your own servers after 2029, HelpSpot is built for that.
A migration checklist for JSM teams
Whichever platform you choose, this is the work to plan for.
- Inventory what you use. Service desk projects, request types, queues, SLAs, automation rules, email channels, and portal forms. Mark each one keep, simplify, or drop.
- Export early. Back up your Data Center instance and export the ticket history you need to keep. Atlassian recommends a backup before your subscription expires.
- Map your fields. Match JSM custom fields and request types to the new system's categories and custom fields.
- Plan the knowledge base. Move the articles customers and employees use most, and retire the rest.
- Rebuild automation simply. Recreate the rules that matter, not every rule that exists.
- Point email at the new system. Switching mailboxes is usually the moment the move becomes real for customers.
- Run both for a short overlap. Keep Data Center read-only for reference while agents work in the new help desk.
- Finish well before March 2029. Leave margin for testing, training, and surprises.
Next steps
If your help desk needs to stay on your own servers, or you simply want a help desk that's easier to run than JSM, compare the two side by side on our Jira Service Management vs HelpSpot page.
You can also start a free 21-day trial or talk with our team about moving your history over.
March 28, 2029 at 23:59 PST. On that date Data Center subscriptions and Marketplace apps expire and the product becomes read-only. Atlassian says it may offer extended maintenance to some customers by exception.
Not as a new customer. New Data Center sales ended March 30, 2026. Existing customers can buy new subscriptions, apps and expansions until March 30, 2028, and renew until March 28, 2029.
According to Atlassian, your data stays available read-only, but updates and support stop. Atlassian recommends backing up your data before your subscription expires.
Yes. HelpSpot runs on your own Linux or Windows servers with MySQL, MariaDB or SQL Server. Self-hosted HelpSpot costs the same as HelpSpot Cloud, from $899/year for 3 agents with every feature included. US Cloud and EU Cloud are also available if you decide you no longer want to host it yourself.
No. If your service desk depends on Jira Software issue links, Assets/CMDB, or ITIL change management, Atlassian Cloud is probably the shortest path. Teams that mainly answer email and portal requests from customers or employees have more choice, because their help desk does not need to live next to Jira.
