Migrating from Connect to Forge

We are migrating License Manager app from Atlassian Connect to Atlassian
Forge, Atlassian’s supported cloud app platform.

Preparation is currently underway, and implementation is scheduled to begin
on 20 July 2026. We intend to complete the migration before Atlassian Connect
reaches end of support in December 2026.

License Manager will continue to be distributed through its existing Atlassian
Marketplace listing. Customers will not need to install a separate app or
purchase a new subscription.

We have completed the initial Forge registration and established a development
environment for the Forge successor app.

The currently available production version of License Manager continues to use
Atlassian Connect components. The Forge version installed in our development
environment is not yet available to production customers.

Our next steps are to migrate the active License Manager functionality, move
application data to Forge-hosted storage, and validate the upgrade process for
existing installations.

We are following an incremental migration process to reduce operational risk
and maintain compatibility with existing customer installations.

The work includes:

• Moving the License Manager interface to Forge Custom UI.

• Replacing Connect authentication and lifecycle handling with Forge
  capabilities.

• Migrating license, domain and SSL certificate data to Forge-hosted storage.

• Moving scheduled expiration checks and Jira issue processing to
  Forge-managed triggers.

• Retaining a secured Forge Remote service for domain lookups, SSL certificate
  checks and other operations that require external network access.

• Removing the remaining Connect components after feature and data
  compatibility have been verified.

• Finalize the Forge architecture and permission model.

• Define the Forge storage schema and data migration process.

• Establish secure communication with the Forge Remote backend.

• Prepare automated build, testing and deployment environments.

• Migrate custom license, domain and SSL certificate management.

• Migrate calendar, permissions and notification settings.

• Implement scheduled background processing.

• Replace the remaining Connect-dependent user interface and API calls.

• Verify feature compatibility with the existing License Manager version.

• Test data migration, reconciliation and recovery procedures.

• Validate upgrades from supported Marketplace versions.

• Test the Forge version in controlled non-production environments.

• Perform security, performance and regression testing.

• Publish the Forge successor through the existing Marketplace listing.

• Begin a controlled rollout to customer installations.

• Monitor upgrades and address compatibility issues.

• Complete the removal of production dependencies on Atlassian Connect before
  Connect end of support.

These dates are planning targets. They may be adjusted based on testing,
Marketplace approval or Atlassian platform dependencies. Material changes will
be published on this page.

No customer action is required at this time.

When the Forge version becomes available, some installations may be updated
automatically by Atlassian. Other installations may require a Jira
administrator to approve the update, depending on the installed app version
and the permissions required by the Forge release.

We will publish upgrade instructions before the production rollout begins.

Customers should not uninstall License Manager as part of this migration.
Uninstalling the app is not required and may affect access to existing
configuration or application data.

Our objective is to preserve existing:

• Custom license records.

• Domain records.

• SSL certificate records.

• Tags and record-level permissions.

• Notification settings.

• Jira project and issue creation settings.

• Identifiers linking License Manager records to Jira issues.

Before production rollout, we will validate the migration using record counts,
data consistency checks and rollback testing.

Customers will not be asked to manually export and re-import their License
Manager data as part of the planned upgrade process.

We aim to preserve the current License Manager workflows and minimize changes
to the day-to-day user experience.

Some interface, URL, permission or administrative behavior may change because
Forge and Connect use different platform capabilities. Any confirmed customer-
visible differences, limitations or required actions will be documented before
the production update.

A separate upgrade FAQ and expected-changes document will be published closer
to the rollout.

We are designing the migration to avoid extended service interruption.
However, the expected impact cannot be confirmed until upgrade and data
migration testing has been completed.

If any temporary limitation or maintenance window is required, affected
customers will be notified before production rollout.

This page will be updated when the following milestones are completed:

1. Forge architecture and storage model finalized.

2. Core License Manager functionality available in Forge.

3. Existing customer data successfully migrated in testing.

4. Marketplace upgrade path validated.

5. Controlled production rollout started.

6. Migration completed and remaining Connect components removed.

For questions about the License Manager migration, please contact us through our support portal.