Atlassian has announced the official End-of-Life (EOL) date for Data Center products – March 28, 2029.
We understand that some organizations face unique challenges and requirements that may delay their move to the cloud. For these scenarios, Atlassian is committed to offering an extended maintenance schedule for Data Center customers (by exception) beyond March 28, 2029, to ensure teams have the flexibility and support needed for a successful transformation (see FAQ “When will end of life occur”).
K15t is following Atlassian’s lead. We are committed to offering extended maintenance for eligible apps to those customers who have been granted an exception by Atlassian.
How the Program Works
Eligibility for K15t’s extended maintenance is tied directly to your status with Atlassian:
-
Atlassian Approval First: You must first be granted an exception by Atlassian for your core Data Center products (Jira or Confluence).
-
K15t Alignment: Once Atlassian approves to extend your core product support beyond March 2029, K15t will offer the same extended maintenance for the eligible apps listed below.
Eligible Apps
If Atlassian grants you an exception for extended Data Center support beyond March 2029, we are happy to offer extended maintenance for the following K15t Data Center apps:
-
Scroll PDF Exporter for Confluence Data Center
-
Scroll Word Exporter for Confluence Data Center
-
Scroll HTML Exporter for Confluence Data Center
-
Scroll Sites for Confluence Data Center
-
Scroll ImageMap for Confluence Data Center
-
Scroll Content Manager for Confluence Data Center (including Variants and Translations modules)
-
Backbone Work Sync for Jira Data Center
Important: Scroll Versions & Scroll Translations Customers
If you are currently using Scroll Versions or Scroll Translations, please take note of the following requirements:
Transitioning to Scroll Content Manager
Our goal is to have all Scroll Versions and Translations customers migrated to Scroll Content Manager by March 2029, as we can not offer extended maintenance for those two apps after March 2029 at this point.
To take full advantage of extended maintenance after March 2029 and remain ready for an eventual move to Cloud, you must migrate Scroll Versions and Translations to Scroll Content Manager before the March 2029 EOL date.
Scroll Content Manager is the future-proof equivalent for version control and translation management and it’s available for both Data Center and Cloud. By moving to Scroll Content Manager now, you ensure that your content remains fully supported and that your instance is optimized for the long term.
Once you have successfully converted your content to Scroll Content Manager, we will include your instance in our extended maintenance offering.
We are here to help
Our goal is to make this transition as smooth as possible and ensure every customer has a clear path forward. If you are currently in discussions with Atlassian regarding an exception for extended support after March 2029, or if you are planning your long-term migration strategy, please reach out to us as soon as possible.
Our team is ready to assist you with the conversion process to Scroll Content Manager, ensuring your instance is stable, supported, and Cloud-ready when you are eventually ready to make the move.