Atlassian has officially extended the End of Support (EOS) date for its Connect app framework to January 31, 2027. This extension provides marketplace vendors and developers additional time to transition their apps to the Forge platform under a structured three-phase process.
- Connect EOS extended to January 31, 2027
- Three-phase timeline with deprecation notices
- Forge adoption encouraged to ensure compliance
What happened
Atlassian has extended the End of Support date for Connect to January 31, 2027, in response to feedback from developers and marketplace vendors. The company revealed a three-phase deprecation plan, starting with a halt on new Connect app listings from September 17, 2025, followed by disabling updates to Connect apps later, and finally moving Connect into a support-free state where it will no longer evolve alongside Atlassian's products.
Developers received newly published documentation to assist with their migration efforts, clarifying the distinction between Connect and Forge apps and outlining which Connect modules will not be replicated in Forge. The phased approach aims to provide ample notice and planning time, balancing the needs of those already migrating and those yet to begin.
Why it matters
This transition marks a significant shift in Atlassian's app development ecosystem toward Forge, its next-generation platform emphasizing security and modern capabilities. Connect modules that are low usage or incompatible with Forge’s security model will be deprecated, pushing developers to adopt Forge to maintain marketplace presence and app functionality.
The extended timeline reflects Atlassian’s commitment to transparency and responsiveness to developer concerns, recognizing the varied progress in migration readiness. It encourages all developers to explore Forge adoption soon, offering alternatives like Forge Remote to ease the migration process without requiring full backend changes.
What to watch next
Market participants should closely monitor the enforcement dates for each phase, starting with the September 2025 cutoff for new Connect app listings. Developers maintaining Connect apps must plan for the second phase to ensure continued update capabilities by adopting Forge manifests and modules as required.
Atlassian will continue updating developer documentation and the Connect equivalence roadmap for feature parity and migration tracking. Vendors should leverage community forums and the FRGE project to submit feedback and access support, ensuring alignment with evolving requirements before the final Connect EOS.