Choose and execute the path for your Atlassian Data Center estate before support ends.
iTmethods assesses the products, apps, integrations, data, workflows and operating requirements in the current estate, compares the viable paths, and can plan, migrate and operate the selected target. The recommendation follows the customer’s requirements.
Every date on this page is Atlassian's, published at atlassian.com/licensing/data-center-end-of-life and at atlassian.com/migration/bitbucket-hybrid-license, both read on 25 August 2026. Timelines for third-party products belong to their vendors and can change without reference to us. Nothing here represents the views of Atlassian Pty Ltd.
Confirm the 2028 purchasing and renewal position before planning the path to 2029.
Most plans are built against the end-of-life date. The date that actually constrains an enterprise is the one before it — 30 March 2028, when new sales and expansion end.
From 30 March 2028, you can renew or reduce the Data Center subscriptions, user tiers and Marketplace apps you already hold. New subscriptions, expansions, upgrades and Marketplace app purchases end that day. Standard renewals are prorated so that every term ends by 28 March 2029. Atlassian also says some customers may purchase a multi-year extension beyond that date by exception. Have Atlassian confirm your position in writing before you base a 2028–2029 plan on it.
For most estates the apps are the migration, not the platform. An inventory of which apps have a destination on each path is the first piece of work, and it is usually the one that decides the answer.
That distinction matters to a risk function. An unpatched read-only system holding live business records is a fact pattern for your risk function to evaluate before that date arrives.
So the exemption runs through a license that Atlassian still describes as coming mid-2026, and we have found no confirmation it has shipped. Source control and work management are still two decisions on two timetables, and that is the useful part — but “Bitbucket is fine” is a stronger sentence than Atlassian’s own page supports. What we run for Bitbucket Data Center →
What closes, and when.
Each row is Atlassian's published position, and the last column is what it closes.
| Date | What Atlassian published | What it closes |
|---|---|---|
| September 2025 | End of life announced for the Data Center product line. | Nothing yet. It starts the planning clock, and it is the point after which "we did not know" stops being available. |
| 16 December 2025 | New Data Center apps can no longer be submitted to the Marketplace. | The app inventory. Anything not already listed is not arriving, which bounds the app-substitution work this page calls the decisive piece. |
| 30 March 2026 | New customers can no longer purchase Data Center subscriptions or Marketplace apps. | The path in. If you do not already hold a license, Data Center is not an option you can still choose. |
| July 2026 | Isolated Cloud, Atlassian’s single-tenant Cloud offering, became generally available. | Nothing on the Data Center clock. It is the point after which the Cloud path can offer single-tenant, region-locked hosting, which answers most of what data residency used to rule out. |
| 30 March 2028 | Existing customers can no longer purchase new subscriptions, expansions or Marketplace apps. | Growth ends here. Atlassian allows renewal at the user and app count you hold today, through 28 March 2029; what stops on this date is new subscriptions, expansions and Marketplace app purchases. The subscriptions, user tiers and apps you hold on 30 March 2028 can continue or become smaller. |
| 28 March 2029 | Data Center subscriptions and any associated Marketplace apps expire and become read-only. Standalone Bitbucket Data Center licenses — the exemption that keeps Bitbucket off the end-of-life list — also stop being available on this date, after which Bitbucket is sold exclusively through a Hybrid License Atlassian still describes as coming mid-2026. | Support, security patches and any vendor path back for Data Center; the data remains readable. For Bitbucket, the standalone license — it stays a separate decision, but not one without a date. |
Atlassian has also published what does not change before then. Through 28 March 2029 it continues technical support, security bug-fixes for critical vulnerabilities, and the connectors from Data Center products to Atlassian Cloud. What the dates above close is the ability to buy, not the ability to run.
Times are stated by Atlassian as 23:59 PST on each date. Atlassian also offers “extended maintenance for certain Data Center customers by exception” after 28 March 2029, with no published criteria, no price and no application process — a real escape hatch with nothing behind it you can plan against. We publish no price figure for any of these steps: Atlassian’s end-of-life page states no increase, partner sources report one, and an unattributed market number is the same class of problem as an unattributed customer quote.
Three options. iTmethods can help with each one.
Staying on Data Center, moving to Atlassian Cloud and moving to another platform are all real options. Each card names whose product the option runs on, what iTmethods can do, and what stays with the vendor or with you.
Operate the current estate for a defined period
Address lifecycle, upgrade, support and capacity work while the target decision and migration plan are completed. Treat this as a time-bounded operating decision.
Move to Atlassian Cloud
Assess product fit, marketplace apps, integrations, identity, data residency, control requirements, migration tooling, operating change and cost.
Move to another platform
Assess requirements and migration feasibility for an alternative such as Plane, including workflow and data mapping, feature gaps, integrations, validation, cutover, rollback and ongoing operation.
Use different paths for different products. Evaluate a mixed target where the requirements justify it, including the integration and operating consequences of the split.
Delivered as a single-tenant dedicated instance, in infrastructure iTmethods operates or in your own cloud account. The FAQ below states what is available today, what is planned, and that there is no multi-tenant option.
Whichever tracker you land on, agents will be reading it.
The work tracker holds the backlog, the incident history and the change record. Atlassian Intelligence, Jira's own agents, MCP servers and whatever your engineers add next all read and write it at machine pace. Reign Gateway governs them at the call layer, applying policy to the call itself rather than to whichever tool made it.
Who holds what, on the way across.
Written down before anything moves, so the boundary is a document rather than a discovery halfway through a cut-over weekend.
| Who | What they hold | Examples |
|---|---|---|
| Reign Ops, automated | Decisions closed inside the substrate without human intervention, once the estate is live. | Operate the instance inside your authorization boundary. Enforce your identity provider at the platform edge. Stream audit logs to your SIEM. Patch on an upstream-matched cadence. |
| Customer authored | Decisions you own under the shared-responsibility model. You are the author here rather than the approver. | Which projects move and in what order. Workflow and field decisions that were never right in the first place. Which Marketplace apps have a destination and which are retired. The change window. Sign-off on each cut-over. |
| Operating partner engagement | The work that needs a named engineer rather than a runbook, done with your team rather than to it. | The app and workflow inventory. Migration scoping and phased cut-over. Data mapping and the dry runs before it. The decisions that change the design rather than the configuration. |
iTmethods makes no compliance, certification or accreditation claim under any framework. What each framework asks for is set out on regulatory alignment.
FAQ
Where would Plane actually run?
Do you have a view on Atlassian Cloud?
How long does a Jira to Plane migration take?
Start with the estate and the decision date.
Bring the products and versions, user counts, apps, integrations, renewal dates and the target options already under consideration. Use the conversation to discuss which decisions are time-sensitive and what evidence would be needed to choose a path.