The policy and its scope
Atlassian’s September 2025 transition announcement set a 28 March 2029 end-of-life date for affected Data Center products.Read more
Its current policy includes Jira and Confluence, while Bitbucket Data Center and Jira Align Data Center are excluded. Exceptional extensions may be available; check the current vendor terms for your deployment.
IGEARS analysis: the deadline is a discovery trigger
A renewal calendar cannot tell you how to replace custom issue fields, marketplace apps or embedded knowledge links.Read more
Start with the teams who use those features. Separate the decision to adopt Atlassian Cloud from the decision to evaluate alternative tools and from any need to retain an archive.
Build a migration inventory
Give every important workflow an owner and a measurable acceptance test.
Supporting detail
- Jira fields, statuses, automations, reports and cross-project links.
- Confluence pages, attachments, permissions and app-generated content.
- Identity, integrations, audit history and external collaborators.
- Contract dates, export rights and app-specific migration support.
Compare plausible paths
OpenProject, BookStack and Zammad address different jobs; none should be presented as an automatic recreation of an Atlassian installation.Read more
Pilot a bounded project or knowledge area, reconcile history and test user permissions. IGEARS can assess cloud migration, open-source alternatives or a phased combination against your actual requirements.
Sources and verification
- Atlassian: Data Center transition announcement, September 2025 ↗
- Atlassian: Current Data Center end-of-life policy and exceptions ↗
Policies and features can change. Verify the current terms and your installed edition before implementation.