After migrating app to forge. Deleting connect infrastructure

[SandroHerrmann]

Hi,

we have completely migrated our app to forge. Customers are migrated. So we are now at a point to deactivate the old connect infrastructure. Is there anything we need to do additionally in regards of communication with Atlassian? Because we still see the connect variant of the app in the developer console… with metrics about its availability.

Regards,

Sandro

[remie]

I would suggest contacting Atlassian Developer and Marketplace support (Jira Service Management)

As long as there are customers using Connect, the Marketplace Partner agreement stipulates that you will need to support them. I expect that Atlassian will want to make sure that all customers have been migrated, and that there has been customer communications prior to sunsetting the Connect app.

[markrekveld]

Next to contacting Atlassian Developer and Marketplace support, you can also add a notice to the Connect app UI if you still have that.

After the first UI elements where migrated for my app, I added a notice to the connect app stating that people should update because the connect will go dark after migration is completed.

I’m now in the process of dismantling the connect app, as I don’t see any more traffic looking at my own metrics.

[mehmetaydogdu]

While the onboarding process for Forge is well-covered, there is a gap regarding the Connect decommissioning process. Documenting the official exit procedure would help prevent inconsistencies.

For instance how can we stop the automated health-check pings and Eco Scanner from targeting to our legacy Connect endpoints without affecting our Marketplace listing status?

[goncalomb]

Having some official documentation on this would be nice. We want to get rid of the old connect backend as soon as possible, but just disconnecting it will probably trigger some errors with Atlassian’s automated security scanners, because the old connect versions are still available.

I’ll be contacting support when the time comes.

[goncalomb]

I was thinking about this again… Maybe one possible way to address this would be to give partners the possibility to delete previous connect app versions (with no installs). Currently that option is grayed out (I’m not sure if it was ever available).

EDIT(2026-02-22): I ended up contacting support (App retirement/archival) looking for guidance on how to procede with retiring the old connect versions and deleting the infrastructure. After some back and forward, and some input from the “Internal Team“ we decided to delete all the previous AC versions (4). I don’t think it’s ideal, but we are a small app and it made sense. I saw the scanners stop hitting the server and then deleted the infrastructure. They also said that we could delete the connect.key from our manifest (I have not tested that yet). I had asked about that because we want to support multiple Atlassian apps in the future, and I think not having a connect.key is a requirement.