Upgrading non-Marketplace apps to Forge
The Atlassian Platform is endlessly customizable, and many customers build their own cloud apps to solve unique, custom workflows. In this blog post, we’ll cover important information about keeping your custom cloud apps up to date.
In early 2025, we announced that support for the Connect framework will end in late 2026 and advised developers to begin transitioning to Forge. Forge is Atlassian’s modern cloud app development platform that replaces Connect. It lets you build secure, scalable apps for Jira and Confluence, running on Atlassian’s infrastructure for easier deployment and management. Because end of support affects all Connect apps, it’s important for developers maintaining custom Connect apps to be aware that these changes will affect them too.
This post breaks down how to determine whether Connect end of support impacts your custom apps and how to plan your migration to Forge to avoid disruption.
What Is a Custom App?
Custom apps are typically developed by a customer themselves, or by a Solution Partner. They’re often used for internal tools, prototypes, or custom solutions and workflows. This blog post only concerns custom apps that are compatible with Atlassian Cloud and built on the Connect framework.
Here are a few ways you can determine whether an app is a custom app:
- Not listed on the Atlassian Marketplace
- Installed manually or via developer mode
If you have a custom cloud app that was built more than 5 years ago, it is likely a Connect app (although some Connect apps were built more recently). Connect apps are hosted externally to the Atlassian platform, typically on a service like Heroku, AWS, Azure, or Google Cloud Platform. This is a key difference from Forge apps, which are hosted by Atlassian.
What does end of support mean for custom apps?
Custom apps are maintained by the developer—in this case, by the customer who built the app. Unlike Marketplace apps that receive updates from the partner, customers are responsible for keeping custom apps up to date.
Custom app builders should familiarize themselves with the Connect end of support timeline, which includes several key milestones:
- You’ll no longer be able to push updates to Connect apps after Phase 2, which takes effect March 31, 2026.
- Connect will reach end of support at the end of 2026.
Once end of support takes effect, Connect will no longer receive security updates or feature updates. Over time, some Connect features may stop working as Connect capabilities begin to fall behind the Atlassian Platform.
Custom app identification checklist
If you’re unsure whether an app is custom, use the checklist below. If you answer “yes” to most of these points, it’s likely a custom app:
- Installed via direct link or developer mode, not the Marketplace
- Not visible in Marketplace search
- You maintain the source code for the app
- No app licensing info; your org is the only one listed under installations
On your Connected Apps screen, you can check whether the related links sidebar is present. The sidebar will appear for Marketplace apps, but not custom apps.
How to get started upgrading custom apps
- Check if your app is custom: Use the Connected Apps screen to identify any custom Connect apps in use.
- Determine if you have access to the app’s source code: To migrate to Forge, you will need to have access to the source code for your app. If not, it may be necessary to rebuild on Forge from scratch. You may wish to engage a Solution Partner to assist with this.
- Audit the app: Assess the use case the app is serving. The app’s functionality may be covered by a native Cloud feature or a Marketplace app, or certain features may no longer be required. It’s a good idea to only migrate functionality that is still needed by your organization.
- Start a Forge proof-of-concept: Even if your app is simple, Forge’s model is different; start experimenting early. If Forge doesn’t yet support a capability your custom app uses, let Atlassian know and keep an eye out for the changes we are bringing out. Review the docs to compare Connect capabilities to their Forge equivalents.
If you rely on custom Connect apps for your workflows, now is the time to get started. Migrate early, explore Forge, and future-proof your tools. While change may take some effort, it also offers a chance to modernize and simplify.
Join the live Q&A session
We’re hosting a live session to share more information about migrating to Forge, geared specifically toward builders of custom apps (customers and Solution Partners). Sign up to explore Forge with our panel of experts and join us for live Q&A.
FAQ
Q: Do I need to take any action if I’ve installed Connect apps purchased from the Marketplace?
A: No, no action is required. Marketplace apps are supported by partners, and many partners are already well underway with migrating to Forge. Partners still have considerable time to complete migration, and Connect will continue to be supported until late 2026. If you have a question about a specific app’s migration status, you can reach out to the partner directly.
Q: What happens if I continue to use Connect modules after 2026?
A: When Connect reaches end of support, it will be considered “use at your own risk.” Connect will no longer receive updates or security patches and some features may eventually stop working as Connect begins to fall behind core platform capabilities.
Q: Can I migrate my custom Connect app to Forge at any time?
A: Migration is encouraged as soon as possible to avoid disruption, but Connect will continue to be supported until late 2026. Apps that do not begin migration by March 2026 will no longer be able to push Connect-based updates.
Q: How can I determine if my custom app is on Connect or already on Forge?
A: An easy way to identify if it’s Connect or Forge in Connected Apps is to look at the URL when viewing the app – Connect apps look like this:
Forge apps look like this:
Q: Where can I find more information about the Connect end of support timeline and migration steps?
A: See the official Atlassian blog post