Forge migration plan
Advanced Export already runs on Atlassian Forge, and it will keep working after January 2027. You do not need to do anything, and there is no plan to discontinue the app.
If you administer Jira, you may have seen a message like this next to Advanced Export on the Connected apps page in Atlassian Administration:
This app may stop working after January 2027, as it's running on a platform that will be unsupported from that date.
This page explains what that message means, why it appears for our app, and what we are doing about it.
Why you are seeing this message
Atlassian is retiring Atlassian Connect, its older app platform, on 31 January 2027. It is replaced by Forge, the modern platform. To help administrators plan, Atlassian now shows a notice on every app that still uses any part of Connect.
Advanced Export has already moved to Forge. Everything you interact with — the dashboard, the export screens, the board and backlog actions, the admin settings, authentication and permissions — runs as a native Forge app today.
However, a small internal component of the app still uses a Connect interface. It is not something you see or use directly: it is the mechanism our backend uses to authenticate to your Jira site when generating scheduled reports. Because that component still exists, Atlassian's automated check classifies the whole app as "using Connect", and shows the notice.
The notice is generated automatically from that classification. It is not an assessment of our app specifically, and it is not a signal that we have stopped maintaining it.
Will the app stop working?
No. We are completing the migration well before the January 2027 deadline, and we have formally declared that commitment to Atlassian in the app itself.
There is no plan to sunset Advanced Export. It remains actively developed and supported.
Will I need to do anything?
No. The remaining work is entirely internal to how our backend talks to Jira.
- You will not need to reinstall the app.
- You will not lose your saved exports, templates, schedules or settings.
- Your scheduled reports will continue to run without interruption.
If a future update ever requires an administrator to approve new permissions, Atlassian will prompt you in the usual way and we will announce it in the changelog beforehand.
Our timeline
| Phase | Status |
|---|---|
| Move the user interface, authentication and permissions to Forge | Complete |
| Publish our migration commitment to Atlassian | Complete |
| Move backend Jira authentication to Forge tokens | In progress |
| Replace the remaining Connect lifecycle component | Planned |
| Remove all Connect components; Atlassian notice disappears | Target: before 31 January 2027 |
We will keep this page updated as each phase completes.
Why Advanced Export uses its own backend
A question that often comes up alongside this one: why does the app have a backend server at all, rather than running entirely on Atlassian's infrastructure?
Several of the app's core features cannot be provided by the Forge runtime alone:
- Scheduled reports that run on a recurring cadence, independently of anyone's browser session.
- Large exports that take longer to generate than Forge's function time limit allows.
- Delivery to your systems — uploading report files to your SFTP server, or sending them through your own email provider.
- Temporary file storage for download links and API access, retained for the period you choose.
For these cases Atlassian provides Forge Remote, a supported part of the Forge platform that lets a Forge app delegate work to a backend operated by the vendor. This is the documented and recommended approach for apps like ours, and it is unaffected by the Connect end-of-support timeline.
You choose the geographic region in which that processing happens — see App Settings. Details of what is stored, where, and for how long are in our Data Security and Privacy Statement.
Questions
If you have questions about this migration, or you need something in writing for an internal review, please contact our support team. We are happy to help.