> For the complete documentation index, see [llms.txt](https://docs.mybytes.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mybytes.tech/connect-to-forge-migration-plan.md). # Connect to Forge Migration Plan **Current status:** In Progress\ **Last updated:** July 28, 2026 ### Overview **Commitment status:** We intend to migrate all of our apps from Atlassian Connect to Forge before Atlassian Connect reaches end of support on December 31, 2026. This page outlines the planned migration approach, expected timeline, potential customer impact, and any actions that may be required from administrators. The app is being modernized to align with Atlassian Forge, Atlassian’s cloud app development platform. Forge provides Atlassian-hosted infrastructure and better alignment with Atlassian Cloud security and platform standards. ### Expected customer impact The migration is planned to avoid customer-facing downtime. Short maintenance windows may be communicated if required. Existing functionality is expected to continue working after the migration. Administrators may be prompted to approve updated Forge permissions during the app update process. If any connected service needs to be reauthorized, affected administrators will be notified. ### Planned timeline #### Phase 1: Development and validation Incrementally migrate existing Connect functionality to Forge. **Target period:** Q3 2026\ **Customer impact:** None expected #### Phase 2: Customer rollout Release the Forge-based version to eligible customers. **Target period:** Q4 2026\ **Customer impact:** Administrators may need to upgrade the app and approve updated permissions. #### Phase 3: Post-migration stabilization Monitor migration completion, app performance, and support requests. Remaining Connect dependencies will be removed. **Target period:** Q4 2026\ **Customer impact:** None expected ### How we will communicate updates We will communicate migration updates through: * Updates to this migration plan as milestones are reached * Release notes for app versions that include Forge related changes * Support guidance for known issues, required actions or reauthorization steps ### Support and contact For questions about the migration plan, contact us at