Jira Data Center: the real deadline is not 2029

Most organisations running Jira Data Center, the last way to host your tickets without sitting under American jurisdiction, have settled on one date: March 2029. That deadline feels far off. It is next year's problem, or the year after's.

The real deadline falls in March 2028, and it is a great deal closer. Back to the calendar.

The calendar Atlassian announced

Atlassian announced Data Center's end of life on 8 September 2025, with four dates that matter. They are published on its migration page and in its announcement to Marketplace partners.

16 December 2025: no new apps. The Marketplace stopped accepting new Data Center applications.

30 March 2026: no new customers. Data Center is no longer an offer anyone can reach. For an organisation of twenty people, this date closed the last door that answered a sovereignty requirement.

30 March 2028: the last renewal. The last day your existing licence can be renewed, for one final year in its current form.

28 March 2029: read-only. Jira Data Center stops accepting writes. Your tickets are still there, as a read-only archive.

The first two dates have now passed. You have a little over 2 years to migrate, a little less to decide.

Why 2028 is your deadline

A renewal is annual. The last one you can sign falls on 30 March 2028, and it buys you the year to March 2029. The final decision, stay or go, is therefore taken at the previous renewal. For most organisations, the one in 2027.

Now work backwards from that date, without optimism, for an organisation of any size.

Someone has to survey what Jira is actually used for. Not the list of projects, the processes. That is several weeks of asking people what they do, and it cannot be delegated to whoever administers the tool: they know the configuration, not the work.

If you are a public body, you need a tender. Publication, questions, offers, evaluation, award, standstill. Months, and only on condition that nothing is challenged. The sovereignty clauses you will be asked for get settled when the specification is written, not when it is evaluated.

You also need a budget line, and you know as well as I do how budget lines move.

You need a migration, probably with a parallel run, because nobody switches a live register over a weekend and crosses their fingers.

And you need people who learn the new tool while still doing their own job.

Add all that up and the decision sits in 2027. The renewal in front of you is the last comfortable one.

Atlassian's three options

Read Atlassian's migration documentation carefully: there are three paths.

The cloud.
The cloud in an isolated edition, on the upper plans.
And the cloud later, through extended maintenance, which is paid, time-limited and granted by exception to those who can make their case.

If your reason for running Data Center was inertia, the cloud is probably your answer. If the reason is more like a regulator, an air-gapped network, a procurement rule, a data protection officer, or simply a preference for holding your own data, then none of the three answers it. We take each of those reasons in turn, and what is left once you take them seriously, in what remains self-hostable.

In September 2025, Atlassian told its Marketplace partners that 99% of its customers were already in the cloud or on their way there. Take the figure at face value: you are in the remaining 1%. Inertia aside, that remaining percent is the name for the group whose needs an American cloud requirement does not meet.

The fourth option

There is a fourth option: do not replace Jira. Replace what you were using Jira for.

Most organisations on Data Center are not doing software development in sprints. They track files, worksites, inspections, internal requests, supplier qualifications, corrective actions. That is a different trade from the one Jira was designed for, and we gave a whole episode to alternatives for teams that do not build software. That work needs a structure your own people can change, a trail you can show an auditor, and reporting that comes out of the data instead of being reassembled by hand every month. It does not need 47 custom fields or a certified administrator.

We built Klaro Cards for exactly that work. We host it in European data centres or on your own servers, from a Belgian company. The countdown page carries the whole argument, prices included.

But back to our calendar for now.

Five things worth doing in the next few months

None of them commit you to anything.

1. Write down what Jira is actually used for. One process per line. You will be surprised twice: by how much is in there, and by how little of it needs Jira.

2. Separate the software development from the rest. If you have teams living in sprints, their answer may well be Atlassian Cloud; otherwise there are some excellent European tools. The rest of the organisation is a different question, and it deserves time spent on a different answer.

3. Export once, as a test. The point is not to migrate but to measure. An afternoon will tell you which fields survive a CSV export and which do not. That is where the real work turns out to be.

4. Find the exact date your licence renews. Not the year. The date. Then count how many are left before 30 March 2028.

5. Ask a supplier a hard question. Under which country's law does your company operate? The question is short, the answer is too, and it teaches you more than a feature matrix. Why that one rather than the address of the servers: what hosting in Ireland does not settle.

Jira, Confluence and Atlassian are trademarks of Atlassian. Klaro Cards is not affiliated with Atlassian.

Sources: Atlassian's migration page and end-of-life pages; the announcement to Marketplace partners of September 2025; ITdaily. Dates are as published by Atlassian, in Pacific time.