Since 2016, codefortynine has built 13 Connect apps that together exceeded 20,000 installs and served 2.5+ million users across 150+ countries. When Atlassian accelerated the move to Forge, we committed to migrating our largest Connect apps in just six months — without degrading reliability or customer value.

In this session, we share concrete, anonymized migration metrics (e.g., commits, hours, # of ECOHELP tickets, etc.) and the decisions that made the biggest impact. We’ll cover how we navigated Forge limitations (request timeouts, response sizes, resource ceilings), what we did when previously used Connect modules were unavailable, and the architecture & operations patterns that kept us shipping confidently.

It’s a constructive, data-backed playbook from an Atlassian Platinum Marketplace Partner. You’ll leave with realistic benchmarks, reusable engineering patterns, and a practical checklist to de-risk your own Connect-to-Forge journey in 2026.

Key takeaways:

• Realistic effort ranges for migrating sizable Connect apps to Forge — benchmarks for commits, person-hours, tickets, and releases.
• Reusable engineering patterns for Forge constraints.
• Bridging module gaps when a previously used Connect module isn’t available in Forge — UX adjustments, smart API combinations, and other shortcuts.