OpenEdge 11.7 Is Retired
What it means for your estate, and what to do next.
Still running OpenEdge 11.7 or earlier?
Progress retired OpenEdge 11.7 on 1 April 2025 and points remaining OpenEdge 11 users to a supported long-term support release in the 12 series (Progress). Progress's published product lifecycle gives each LTS release a fixed sunset phase, so the same question will come round again for whichever release you move to next (OpenEdge Product Lifecycle).
Retired does not mean the software stops. Your application will keep running tomorrow. It means the release is no longer where fixes, security updates and support effort go, and the gap between your estate and a supported one grows every month.
What moving to OpenEdge 12 usually involves
- A database conversion. OpenEdge 11 databases are converted to the 12 format. It is a well-documented step, and it is also the step practitioners warn about most, so it should be rehearsed on copies of production before it is run for real.
- A recompile. The ABL application is recompiled against the new release, and compile errors and behaviour changes are worked through.
- AppServer changes. Estates still on the classic AppServer or WebSpeed move to PASOE, because OpenEdge 12 does not include the classic AppServer.
- Client and deployment updates. New client installs, startup parameters and deployment scripts.
- A good moment for housekeeping. Many estates also move tables to Type II storage areas, clean up indexes or adopt source control during the upgrade, because the testing effort is already being spent.
Where to start
The Estate and Upgrade Readiness Assessment answers the first questions: which release to target, what will break, how long the conversion takes on your data, and in what order to do the work. If you already know the shape of the job, we can go straight to a rehearsed upgrade.
For the detail behind each step, see what OpenEdge release retirement means and rehearsing the 11 to 12 database conversion.