Atlassian timeline for ending Connect support
Atlassian has announced the timeline for Connect's phased end-of-support.
From Sep 17, 2025, only Forge apps can be submitted to the Atlassian Marketplace. All new extensibility features will be delivered only on Forge.
Have an existing Connect app? Find out how to incrementally adopt Forge from Connect.
This page covers how to submit your Forge app to the Marketplace in order to replace your existing Connect app.
At this point, you should have already integrated your Connect app with Forge. See Migrate an app from Connect to Forge for detailed instructions (including known issues and limitations).
You'll also need to enable sharing on your app. This will allow you to distribute it via the developer console. See Distribute your apps for detailed instructions.
Read the following details before submitting your app to be listed on the Marketplace.
If your app stores personal data, it must comply with user privacy requirements, as set forth under applicable data protection laws; this may include the General Data Protection Regulation (GDPR).
It is your legal responsibility to provide accurate privacy and security information about your app, particularly through your app listing�s Privacy and Security tab. See Privacy and Security tab in your Marketplace listing for more information.
If your app supports data residency, you should also provide a complete list of all in-scope End User data.
Follow the Forge user privacy guidelines to implement flows to report and erase personal data as appropriate.
End User Terms and Data Processing Addendums (DPA)
To transact with customers in cloud, you'll need End User Terms, also known as a customer agreement or Terms of Service (TOS). Also, if you are a Data Processor under GDPR, or process personal data under other personal data laws and/or regulations, you'll need a DPA.
If you don’t have a customer agreement yet, Atlassian offers a standard, customizable end-user agreement that may meet your needs.
Learn more about the standard, customizable end-user agreement.
Forge apps can be deployed to development, staging, and production environments. If you're listing a paid app, you must always use the development or staging environment to test your app. This is because all installations of production paid apps are billed. Even if you're the app developer, if you install your production paid app on your Atlassian cloud instance just to test it, you will be charged for it.
Note that the Forge platform uses a consumption-based pricing model, offering most capabilities for free within monthly usage limits. Learn more about Forge platform pricing.
Once sharing is enabled, you can publish a new app version to the Marketplace by selecting the Forge app.

Once the Forge version's Marketplace listing is approved, install it. You can do so via Universal Plugin Manager (UPM) or Marketplace.
You should see an available update for your Connect app in the UPM.

Select Update and refresh the page.

You can install the Forge app on a new site via the Marketplace.

When you create a new version for your existing Connect app listing and select Forge as the framework, the dropdown that lists your Forge apps may be empty. This usually means the Marketplace platform can't link your Forge app to your existing Connect listing.

To resolve this, add the app.connect.key property to your Forge app's manifest.yml file. This property tells the Marketplace platform which Connect listing your Forge app replaces.
Step 1: Find your Connect app key
Your Connect app key is the unique identifier from your existing Marketplace listing (for example, com.example.myapp). You can find it in your Connect app descriptor or in your Marketplace listing's management URL.
Step 2: Add the app.connect.key property to your manifest.yml
Open your Forge app's manifest.yml file and add a connect.key entry under app:
1 2app: id: ari:cloud:ecosystem::app/cxxxxxx-xxxxx-xxxx-xxxxx-xxxxxxxxx connect: key: com.example.yourappkey
Replace com.example.yourappkey with your actual Connect app key.
Step 3: Deploy to production
Deploy the updated app to the production environment:
1 2forge deploy -e production
Step 4: Try creating the version again
Go back to your existing Connect app's Marketplace listing, select Create a Version, and choose Forge from the framework dropdown. Your Forge app now appears in the list, and you can proceed with creating the Forge version for your listing.
If your Forge app still doesn't appear after adding the app.connect.key and redeploying, raise a Marketplace Support ticket. To help the support team diagnose the issue quickly, attach the HAR logs captured while selecting Forge from the Create a Version dropdown.
Mistakes happen. In case of an emergency, you can ask our team to manually rollback the migration. To do this, please raise a Marketplace Support ticket under Need help with Marketplace listing?.
If you would like to follow a staged migration, please raise a Marketplace Support ticket under Need help with Marketplace listing?
Example
https://TESTINSTANCE.atlassian.netcom.atlassian.confluence.extra.team-calendarshttps://marketplace.atlassian.com/manage/apps/12345/detailsWe're excited to hear your feedback. Please join us in the Forge developer community.
Rate this page: