What must be rebuilt?
Inventory UI surfaces, webhook handlers, custom fields and scheduled jobs. Separate genuine Forge module equivalents from assumptions that need testing.
CONNECT TO FORGE / PAID ASSESSMENT
Know the migration scope before committing to a cutover.
Best fit
Atlassian teams responsible for private or business-critical Connect apps with real dependencies.
Deliverable
An agreed assessment of modules, data and permission risks plus an actionable migration and acceptance plan.
Price and next step
€490 indicative for the bounded desk assessment. Final scope and quote are agreed in writing; no app secrets or access credentials are needed for the initial inquiry.
Assessment is a scoped service, not automatic Connect-to-Forge conversion, a guaranteed cutover or an authorized implementation without contract and access review.
The service
Assess the expensive failure modes, not just the manifest syntax.
Atlassian offers free Connect-to-Forge tooling. We focus on the application-specific work those tools cannot complete for you: preserved behavior, permission boundaries and existing customer data.
What must not be lost?
Identify stored configuration, install lifecycle, tenant secrets, entity properties and permission assumptions before any destructive cutover.
How do you prove parity?
Written acceptance criteria, staging-test matrix, owner approval points, safe rollback approach and an implementation estimate.
A bounded first engagement
Start with written scoping. Commission the migration only if it makes sense.
The initial assessment is deliberately smaller than a migration sprint. We review the architecture and issue a concrete technical plan; we do not promise that every Connect extension has a direct Forge replacement. Start with our private Connect → Forge migration checklist to see the risks worth checking.
- One private Jira or Confluence Connect application, up to 10 extension-module instances for a standard desk assessment
- Sanitized descriptor and owner-approved architectural context
- Module, authorization and migration risk review, with explicit unknowns and one written revision
- Written deliverable, implementation scope and test acceptance gates
- Optional contracted implementation after scoping — not automatic
How engagement works
No credentials up front. No surprise cutover.
1. Explain your app
Send the Atlassian product, private app purpose, approximate module types and deadline. Do not include source code, secrets or customer records in email.
2. Agree secure scope
Confirm ownership, written terms and a permitted method to exchange only the materials necessary for the assessment.
3. Receive decisions
Review the migration options, blockers, testing requirements and a separate quotation for any implementation work.
Questions
Designed for private, business-critical extensions.
Does this replace Atlassian's free migration CLI?
No. We use the official tools where applicable and provide architectural analysis, risk ownership and client-specific acceptance criteria.
Does the assessment migrate our application?
No. Any build, staged installation or production cutover is contracted separately, after verifying technical feasibility and access.
Will our application data leave Atlassian?
No data needs to be sent for the first enquiry. Later assessment materials are transferred only through an agreed secure channel, with explicit confidentiality and retention terms.
What's the Connect deadline?
Atlassian has stated that Connect end of support begins on 31 January 2027. Private apps may face compatibility and security risks afterward; this is not a prediction of an immediate outage.
Private app · written-first
Show us the workflow, not your credentials.
A short written description is enough to determine whether a scoped assessment is sensible.