Version Upgrade

From a retired release to a supported LTS, rehearsed.

OpenEdge Version Upgrade and Database Migration

Moving an OpenEdge estate from a retired or sunsetting release onto a supported long-term support release is mostly careful, repeatable work. The risk lives in the parts that are done once, in a hurry, on production. Our job is to make sure nothing is done for the first time on cutover night.

What the upgrade covers

  • Database conversion with rehearsals. The conversion is run against copies of production until it is boring: timed, scripted and checked. Every rehearsal ends with record counts, index checks and application smoke tests.
  • A rollback plan. Backups verified by restoring them, a written point of no return, and the steps to get back to the old release if the cutover has to stop.
  • Storage-area restructuring. Where tables and indexes still live in Type I areas, we plan the move to Type II areas, usually through a dump and load, and size the window it needs.
  • Index and schema cleanup. Unused or duplicate indexes, inactive indexes, and schema changes that are easier to make during the move than after it.
  • ABL recompile and runtime fixes. The application is recompiled against the new release, and compile errors, warnings and behaviour changes are worked through.
  • Classic AppServer to PASOE. Where the estate still runs the classic AppServer or WebSpeed, we convert it to the Progress Application Server for OpenEdge. See the PASOE checklist for the shape of that work.
  • Client and deployment changes. Client installs, startup parameters, connection strings and the deployment scripts that move r-code between environments.
  • Performance validation. A baseline captured on the old release, the same measurements on the new one, and tuning until the numbers agree.
  • A cutover runbook. Written for your team to execute, with timings from the final rehearsal.

Knowledge transfer

The upgrade includes working sessions with your in-house developer and DBA, so the people who run the system afterwards understand what changed and why. The runbook, the rehearsal scripts and the configuration notes stay with you.

Billing

Hourly time and materials, by senior US engineers. The assessment is the usual first step because it fixes the scope; if you already have a clear inventory, we can start from it.

Tell us your OpenEdge release, database size and what is prompting the move. A senior engineer replies within one business day.
Start with an assessment