Jira Data Center

Jira Data Center is Atlassian's self-managed Jira product. It runs inside the customer's own data center or private cloud, with Atlassian shipping the binaries and customers operating the database, search, storage, and clustering themselves. Historically it was the Atlassian answer for regulated industries, sovereign programs, and environments that cannot connect to the public internet.

Atlassian's roadmap has changed that. As of March 30, 2026, Atlassian no longer sells Data Center to new customers. Existing Data Center customers can continue to renew through March 30, 2028. All Data Center products reach end of life and become read-only on March 28, 2029. Regulated and sovereign programs can request extended maintenance by exception, and Bitbucket Data Center has a separate hybrid license path, but every other Data Center footprint is on a migration clock.

Merito's role on Data Center is twofold. First, we run existing Data Center footprints well: configuration and permission schemes, custom field rationalization, workflow simplification, automation cleanup, Marketplace app consolidation, and healthy clustering. Second, we plan and execute the migration to Jira Cloud using Atlassian's Cloud Migration Assistant and FastShift program where applicable, and validate what actually landed on the other side.

For customers who cannot move to Cloud for sovereignty, FedRAMP, or air-gap reasons and who cannot secure a DC extension, Merito runs a platform evaluation that looks at DC continuation, non-Atlassian on-prem ALM options, and hybrid paths. The Data Migration solution covers the Jira DC to Jira Cloud move and the Jira DC to a different-platform move equally.

Most Jira Data Center footprints Merito sees have accumulated a decade of custom fields, permission schemes, workflows, and Marketplace apps. Migrating all of that as-is to Cloud is the most expensive possible path: the migration is slower, more brittle, and the resulting Cloud instance inherits every bit of the drift. The right sequence is rationalize first, then migrate.

The migration window is finite. Atlassian's published timeline gives existing customers until March 30, 2028 to renew and March 28, 2029 for full end of life. That sounds far, but a multi-hundred-thousand-issue footprint with 40 custom fields, 30 workflows, and 15 Marketplace apps realistically needs 18 to 30 months of planning and execution. Programs that start the conversation in 2028 are behind.

For programs that cannot go to Cloud for genuine reasons, the answer is not necessarily DC extension. Merito runs a neutral evaluation that looks at DC continuation, non-Atlassian on-prem ALM, and hybrid patterns. We do not sell Atlassian licenses, so the recommendation is not license-driven.