When Regulation Meets the Cloud: What the End of Jira Data Center Means for Regulated Organisations
When Atlassian announced in September 2025 that it would retire its Data Center products, the news was unlikely to affect most of its customers. By Atlassian’s own count, 99% were already using its cloud products.
The remaining customers are in a different position. Many are banks, insurers or public institutions, where moving Jira or Confluence to someone else’s infrastructure involves more than a technical migration. Data ownership, operational control and regulatory obligations all need to be considered, and these are not questions that can be left to the IT department alone.
How much time do organisations have?
New customers have been unable to buy Data Center since 30 March 2026. Existing customers can continue to renew, but from 30 March 2028 they will no longer be able to add licences, users or new Marketplace apps. On 28 March 2029, the licences expire and instances switch to read-only. Jira Software, Jira Service Management, Confluence and Crowd are all affected. Bitbucket is not.
Atlassian has said it will provide extended maintenance after 2029 for “certain Data Center customers with unique circumstances”. That may give some organisations more time, but it is not something to build a migration strategy around. For most customers, March 2028 is the date that matters.
What DORA has to do with it
Since January 2025, banks, insurers, investment firms, payment institutions and other financial entities in the EU have had to comply with the Digital Operational Resilience Act (DORA). Despite what is sometimes assumed, DORA does not prohibit the use of cloud services. It does, however, treat external IT services as third-party risks that need to be documented, covered by appropriate contracts and, where necessary, supported by an exit plan.
In practice, this means maintaining a register of information for reporting to the supervisor, ensuring contracts cover matters such as data location, service levels, audit rights and termination, assessing concentration risk and, for services supporting critical or important functions, having a tested exit plan.
Atlassian makes an important distinction in its own DORA guidance: the requirements it describes apply to its cloud products. With Data Center, the software runs on the customer’s own infrastructure and Atlassian acts as a software vendor.
That distinction matters when an organisation considers moving to Atlassian Cloud. It is no longer simply licensing software that runs on its own infrastructure. It is relying on an external ICT service provider, which brings additional contractual, oversight and risk-management requirements.
This kind of move is certainly possible. Commonwealth Bank of Australia, for example, moved around 25,000 Jira users to Atlassian Cloud in 2022. The project involved keeping its data in Australian data centres and checking where each plugin was hosted.
Is EU data residency enough?
Atlassian allows customers to keep product data in the EU and has more recently introduced Isolated Cloud, a single-tenant environment running on dedicated infrastructure. Both options may be useful for organisations with specific security or data-location requirements.
But data residency is only one part of the picture. DORA does not simply require data to remain in the EU. It requires organisations to understand and document where data is processed and stored, and to pay particular attention to risks associated with providers based outside the EU. Keeping data in a particular region does not change who operates the service. Contractual safeguards, audit rights and a workable exit plan still need to be in place.
Not only a banking issue
The same broader focus on supply-chain security is relevant beyond the financial sector. NIS2 is pushing organisations in that direction, too. In Czechia, the new Cybersecurity Act took effect on 1 November 2025 and covers sectors including energy, transport, healthcare, manufacturing, digital infrastructure and public administration. It makes management accountable for security across the supply chain, including the tools used to manage projects and service tickets.
The EU Data Act also addresses the practicalities of leaving a cloud provider. Since September 2025, providers have had to allow customers to switch with no more than two months’ notice. From January 2027, they will no longer be able to charge switching fees. That is a useful step, but having the legal right to leave is not enough on its own. The data also needs to be portable, and the organisation needs to know how it will use it in the next environment.
Three ways forward
Organisations still running Data Center have three broad options. They can move to Atlassian Cloud and complete the necessary third-party risk and compliance work. They can seek to buy more time through extended maintenance, where Atlassian makes that available. Or they can move to a platform that they can continue to run on their own infrastructure.
None of these options removes the need to plan a migration. Moving from Data Center to Atlassian Cloud, for example, still means reviewing and rebuilding workflows, integrations and apps for a different environment. The decision is therefore not simply whether to migrate, but which operating model makes sense for the organisation in the longer term.
Why YouTrack is worth a look
For organisations that want to retain control over their infrastructure, YouTrack Server from JetBrains is one option worth considering. JetBrains develops YouTrack Server and YouTrack Cloud from a shared codebase, so new features are made available across both editions. In its 2026 roadmap, the company describes server hosting as “isn’t a legacy choice – it’s a valid long-term strategy.”
With YouTrack Server, the organisation keeps its data and operations on its own infrastructure. If its requirements change later, an instance can be moved from Server to Cloud, or back again, using a database backup. That gives organisations a practical degree of flexibility when planning for a possible change of provider or hosting model. Teams that prefer SaaS can use YouTrack Cloud, which is available from Frankfurt.
YouTrack also brings project management, a knowledge base and a helpdesk together in one product. For teams currently using Jira, Confluence and Jira Service Management, that may make it possible to consolidate several tools in one place.
JetBrains, which was founded in Prague in 2000, says it began migration projects with several Fortune 500 companies in 2025 in cooperation with consulting partners, with further projects planned for 2026.
Before you decide
A few questions are worth addressing early in the process:
- What does Jira support in your organisation? If Jira Service Management is used to handle ICT incidents or changes, it may support an important function under DORA, which can raise the level of scrutiny required.
- How much have you customised your setup? Workflows, scripts and Marketplace apps will all need to be migrated, replaced or retired.
- When will compliance be involved? Bring the compliance team into the discussion at the beginning, rather than waiting until the migration is ready for sign-off.
- How would you leave your next platform? Test data exports and understand what can realistically be transferred before committing to a new solution.
It is worth working backwards from March 2028 rather than treating March 2029 as the planning deadline.
The bottom line
Cloud services can be a perfectly viable choice for regulated organisations. The important thing is to understand what comes with that choice: where data is processed, who operates the service, what oversight is available and what happens if the organisation needs to leave.
With Jira Data Center approaching its end, organisations have a good reason to review not only where their work-management tools will run, but how much operational control they need to retain over the long term. The best choice will depend on their regulatory obligations, technical requirements and ability to manage a future migration.
This blog post is general information, not legal advice.


