Atlassian has set March 28, 2029, at 23:59 PST as the end of life for Jira Software Data Center, Jira Service Management Data Center, and Confluence Data Center. At that time, affected subscriptions and associated Marketplace apps expire and become read-only. The main paths are moving to Atlassian Cloud or evaluating replacements against your hosting, workflow, app, migration, integration, and support requirements; none should be assumed to be a one-for-one substitute.
What does end of life mean?
Atlassian says that on March 28, 2029, at 23:59 PST, subscriptions for affected Data Center products and their associated Marketplace apps expire, leaving the products and apps read-only. That is a defined end-of-life deadline, not simply the date when new sales stop. See Atlassian’s Data Center end-of-life policy for the current terms.
The transition has earlier milestones. Atlassian says support began winding down on March 30, 2026. New customers could no longer purchase new Data Center subscriptions or Marketplace Data Center apps after March 30, 2026, at 23:59 PST. Existing customers can buy new subscriptions, apps, and expansions until March 30, 2028, at 23:59 PST.
| Milestone | What Atlassian says |
|---|---|
| March 30, 2026 | Support wind-down begins; new customers can no longer purchase new Data Center subscriptions or Marketplace Data Center apps after 23:59 PST. |
| March 30, 2028, 23:59 PST | Existing customers’ window to buy new subscriptions, apps, and expansions ends. |
| March 28, 2029, 23:59 PST | Affected subscriptions and associated Marketplace apps expire; products and apps become read-only. |
The announced change does not apply to every Atlassian Data Center product. Atlassian excludes Bitbucket Data Center and Jira Align Data Center; it describes a hybrid license for existing Bitbucket customers. The affected list includes Jira Software, Jira Service Management, Confluence, Bamboo, and Crowd Data Center, as well as Data Center mobile apps, Atlassian Data Center apps, and third-party Marketplace apps for affected products. Check the policy page for the complete, current product scope.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11#1 Best Overall
What if I can’t move to cloud yet?
Do not treat an exception as an extension plan. Atlassian says some organizations may qualify for extended maintenance after the deadline, but only by exception; it is not a general entitlement. Its migration information acknowledges that some organizations have complex requirements and encourages them to discuss those needs directly.
If cloud is not currently feasible, use the remaining transition period to identify the blocker and choose a supported path: validate whether a replacement can meet the need, plan the migration in stages, or ask Atlassian about your specific constraints. Document any hard requirements—such as deployment control, regulatory obligations, app dependencies, or integrations—rather than assuming an exception will be granted.
Rank #2
- Keep track of everything from attendance to test scores
- Spiral bound
- Measures 8-1/2" x 11"
Which alternatives are worth evaluating?
Atlassian’s stated route for customers who need to continue using the affected capabilities is its Cloud platform, with migration support through the Atlassian Migration Program. OpenProject is a candidate for project and work management when self-hosting, open-source software, or infrastructure control matters. If replacing both Jira and Confluence, evaluate OpenProject alongside XWiki rather than treating either product’s wiki as a complete Confluence replacement.
| Option | Why it may fit | What to validate |
|---|---|---|
| Atlassian Cloud | Consider it if retaining Atlassian products and capabilities is the priority. | Cloud feature fit, security and compliance, data residency, Marketplace app availability or replacements, integrations, administration, and total cost. |
| OpenProject | Consider it for project and work management when self-hosting, open-source software, or infrastructure control are important. Its documented capabilities include work packages, agile boards, backlogs and sprints, Gantt charts, portfolio and team planning, time and cost tracking, meetings, documents, and a project wiki. | Workflow and field fit, migration behavior, integrations, support needs, and the operational work of the chosen deployment. |
| OpenProject plus XWiki | Consider the pair when replacing project work and enterprise knowledge management while retaining a self-hosting option. The products have integrations connecting project work packages and knowledge pages. | Plan Jira and Confluence migrations separately; test permissions, macros, attachments, diagrams, and links between issues and pages. |
Atlassian Cloud
Cloud may reduce the need to operate the core products yourself, but it still requires a fit assessment. Verify the features your teams rely on, required security and compliance controls, data residency, identity and other integrations, and whether critical Marketplace apps are available or have suitable replacements. Atlassian states that Cloud costs more per user than Data Center while also arguing that Cloud includes additional capabilities; treat that as Atlassian’s comparison, not an independent price analysis. Build your own current cost model using Atlassian’s current policy and pricing information and the costs of required apps.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Atlassian reported in 2025 that 99% of its customers were in Cloud or on a path there. That is a vendor-reported figure, not an independent measure of market adoption, and it does not establish whether Cloud is suitable for a particular organization.
OpenProject for project and work management
OpenProject offers a free on-premises Community edition, an on-premises Enterprise edition with add-ons and support, and an Enterprise cloud edition hosted in an EU data center, according to its installation and operations documentation. Confirm the deployment model, support terms, and current edition details directly before planning around them.
Rank #4
OpenProject explicitly says it is “not intended to be a one-to-one copy of Jira” in its Jira migration FAQ. Its Jira Migrator is in beta and continuously developed; the documentation warns against relying on it outside test setups. The FAQ says commonly used field types are supported, but unsupported types can be skipped. Treat an import as something to prove with representative data, not as an assured transfer of every configuration or extension.
OpenProject with XWiki for project work and knowledge
OpenProject’s own wiki may suit project documentation, but its FAQ says it does not migrate Confluence content and recommends planning a separate Confluence-to-XWiki migration. Map the Confluence spaces, pages, permissions, macros, attachments, diagrams, and references between Jira issues and Confluence pages you need to preserve.
In a joint announcement dated July 8, 2026, OpenProject and XWiki said OpenProject 17.6 introduced a native integration and that the XWiki Confluence Migration Toolkit natively supported 147 Confluence macros. The vendors also reported increasing the toolkit’s migration-trial limit from 30 to 200 pages. These are version-specific vendor claims, not guarantees that your instance’s macros or customizations will migrate unchanged; verify the current toolkit terms and test your own content. See the OpenProject and XWiki announcement.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to choose: test fit before choosing a destination
Compare each candidate against the work your organization actually does. A product can cover familiar concepts such as tasks, boards, or pages while differing in workflow behavior, permissions, extensions, administration, or the way data moves.
- Record your deployment requirements. Decide whether workloads must remain self-hosted or can move to vendor-hosted cloud. Include data location, administrative control, upgrade responsibility, and the operating capacity your team can provide.
- Map processes and configuration. Inventory issue and work-item types, workflows, permissions, custom fields, boards, service-management processes, assets, reporting, and extensions. Mark which are mandatory and which can change.
- Inventory migration data. List projects, users, history, links, identifiers, attachments, permissions, app-specific data, Confluence macros, diagrams, and references between issues and pages. Assess Jira and Confluence migration as separate workstreams where necessary.
- Check the integration and app ecosystem. Identify dependencies on source control, identity, document storage, chat, automation, APIs, and Marketplace apps. OpenProject documents integrations including GitHub, GitLab, XWiki, Nextcloud, OneDrive, and SharePoint, and warns that community plugins may not be officially supported. Review its integration and community plugin documentation for the current details.
- Run a representative test. Use a test environment to try complex workflows, custom fields, issue links, permissions, attachments, macros, extensions, scripts, and downstream integrations. For OpenProject’s beta Jira Migrator, follow the documentation’s warning not to rely on it outside test setups.
- Calculate total cost and operating work. Include subscriptions or licenses, app replacements, hosting, migration services, internal administration, training, and ongoing support. Obtain current quotes; the available evidence does not establish a comparable price ranking.
- Set acceptance criteria and a migration sequence. Define what must work before a team can move, what data must be retained, who owns each integration, and how users will be trained. If you need outside assistance, OpenProject’s integration documentation names ALM Toolbox as a provider that can assist with Jira or Confluence migration; confirm scope and terms directly.
Where the evidence stops
There is no established universal ranking of replacements, nor does the available product documentation establish equivalent coverage for Jira Service Management, custom workflows, Marketplace apps, or every Confluence macro. Microsoft Azure DevOps project wiki is another adjacent candidate organizations may investigate, but suitability, hosting, feature parity, and migration from Jira or Confluence are not established here. Treat the options above as a shortlist for fit-gap testing, not as interchangeable products or a complete market comparison.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
