connectModules) and declare the migration with core:connectToForgeMigration. Your backend and screens stay as they are. A stepping stone, not the end state: the Connect modules inside still need to be replaced.| Connect | Forge | Status | Estimate |
|---|---|---|---|
webSections | grouping only — no module needed | Moves as-is | 1–1 h |
adminPages | jira:adminPage / confluence:globalSettings | Moves as-is | 4–12 h |
jiraProjectPages | jira:projectPage | Moves as-is | 4–12 h |
jiraEntityProperties | jira:entityProperty | Moves as-is | 1–3 h |
dialogs | Modal (UI Kit or Custom UI) | Moves as-is | 2–6 h |
| Area | Forge | Status | Estimate |
|---|---|---|---|
| Install / enable events | avi:forge:installed:app, avi:forge:upgraded:app | Moves as-is | 2–4 h |
| Uninstall event | — | Moves with caveats No direct Forge equivalent yet (FRGE-1246). A small change: cleanup moves to data-retention handling. | 2–6 h |
| Backend authentication (Connect JWT) | Forge Remote (keep your backend) or Forge functions | Moves with caveats Calls to the backend move from Connect JWT to Forge Remote tokens; UIs are bundled into Forge instead of being served from your server. | 8–20 h |
| Scopes: READ, WRITE, DELETE, PROJECT_ADMIN | Granular Forge scopes | Moves as-is | 1–3 h |
| Modules | 12–34 h | ||
| Platform: lifecycle, authentication, scopes | 13–33 h | ||
| Forge app setup, manifest, migration declaration | 6–10 h | ||
| Testing and staged release (development → test site → production) | 6–10 h | ||
| Full migration | 37–87 h |
We turn this into a fixed price after a short look at the code — usually within two business days.