Connect end of support in131 days
How far is your Connect app
from Forge?
Point it at your atlassian-connect.json and get a module-by-module readiness report — every Forge equivalent, every blocker, and an effort estimate you can actually plan against.
- 31 Jan 2027
- Connect end of support
- Mar 2026
- Updates already blocked
- 8–16 wks
- Typical migration
- 0%
- Forge rev share to $1M
No descriptor handy?
Fetched server-side to get around CORS, then analysed in your browser. Never stored.
What it checks
- Every declared module mapped to its documented Forge equivalent — including the ones Atlassian’s own table omits entirely.
- Web item and panel locations resolved individually. The same module is trivial in one location and unsupported in another.
- Webhooks mapped to their Forge product events.
- Platform risks that apply regardless of modules: discontinued lifecycle events, unlicensedAccess opt-in, FIT-vs-JWT on remotes.
How to read the estimate
Day counts are a planning heuristic — module counts weighted by documented difficulty, a surcharge on UI-bearing modules because frontend rework dominates real migrations, and fixed overhead for manifest, auth, build and regression work.
It is not a quote. This reads your descriptor, not your code, so it cannot see how complex your frontend really is. Anything flagged as a blocker needs a human decision before a date gets committed.