Technology

Progress OpenEdge & ABL Modernisation
so the licence stops growing with headcount.

Progress OpenEdge is still developed and the 4GL is now called ABL. The applications we are asked about are usually character-mode systems from the 1990s, running on licences that grow with headcount.

You get the ABL code read and documented, the data moved, and the character-mode screens replaced with something staff will use. We do this for businesses in Australia, New Zealand, the UK and the US, at a fixed price.

Book a 20-min scoping call
  • Independent No licence commission, no reseller agenda
  • 18+ yrs Building business software
  • Fixed Price scopes, no surprises
  • AU NZ UK US Perth-based, working remotely
Australian owned and operated

Built here. Your data stays here.

  • No offshore development. Everything is written by our own team in Australia. Nothing is subcontracted overseas.
  • Your data stays onshore. Hosted in Australia, on infrastructure you own, under Australian law.
  • Every state, not just ours. Perth, Melbourne, Sydney, Brisbane, Adelaide and everywhere between.
Where we fit

Green screens new staff refuse to learn

Progress ran a great deal of ERP, distribution and manufacturing software, often as the engine beneath a vendor package rather than something the business chose. The database and the 4GL are tightly coupled, which made development fast and makes leaving harder than it looks.

Two things bring people to us: green-screen applications that new staff refuse to learn, and a licensing model that charges by user and never gets cheaper.

See all legacy upgrade services

What the work actually is

Get your data clear of the old code, then choose

Progress couples the database and the language tightly, so the first useful step is establishing what the data looks like independently of the ABL code. After that, replacing the front end or the whole platform becomes a real choice.

What you have now

  • .p and .w ABL procedure files
  • A Progress database with per-user licensing
  • Character-mode or early GUI screens
  • A vendor package nobody supports any more
What we build

Separate the data from the 4GL, then choose

Progress couples the database and the language tightly, so the first useful step is establishing what the data looks like independently of the ABL code. After that, replacing the front end or the whole platform becomes a real choice.

Get a fixed-price scope

What you end up with

  • Data migrated to SQL Server or PostgreSQL with relationships intact
  • A web application replacing the green screens
  • Licensing that does not rise with headcount
What we do

Only the Progress OpenEdge work you actually need

Most engagements are some combination of these, and most start with the first.

  1. Document the schema

    The Progress database schema extracted and documented independently of the ABL code, which is what makes every later option possible.

  2. Read the ABL

    .p and .w procedures hold the business rules. They are readable and worth documenting even if the platform stays.

  3. Migrate the data

    Into SQL Server or PostgreSQL with relationships and constraints rebuilt, then reconciled against the source.

  4. Replace the screens

    A web application in place of character-mode or early GUI screens, so new staff do not need training on a terminal.

  5. Stage it sensibly

    Front end first while Progress still holds the data is a common and low-risk sequence.

Where you are now

It works, and nobody will touch it

  • Character-mode screens that new staff will not learn
  • Per-user database licensing that rises as you hire
  • Business logic in ABL that few developers read
  • A vendor package with no remaining support

After

Supported, documented and yours

  • Data in a mainstream database with no per-user licence
  • A browser interface staff can use without training
  • Business rules documented rather than assumed
  • Integration with other systems finally straightforward

Scoped and quoted before you commit. You own the code, the documentation and the credentials at the end of it.

Get a fixed-price scope
Common questions

What people ask us about Progress OpenEdge

Progress is still supported. Why move?

Usually licensing and hiring rather than support. If the licence rises every time you hire and nobody on the market reads ABL, being supported does not solve your actual problem.

Can Progress data go into SQL Server?

Yes. The schema is extractable and the migration is well understood. The care goes into reconciling the result, particularly around date and decimal handling.

Can we replace the screens but keep the database?

Yes, and it is often the best first step. A web front end over the existing Progress database delivers the visible benefit quickly and defers the bigger decision.

Our system is a vendor package on Progress. Does that change things?

It usually means less freedom to modify and more reason to get your data independently documented, especially if the vendor is no longer active.

Is ABL hard to read?

No, it is quite readable, which helps. The difficulty is the shortage of people who have seen it, not the language itself.

Tell us what your Progress OpenEdge system does

What the system does, roughly how old it is, and what is forcing the question. We will come back with a straight answer and a fixed-price scope, even if the answer is to leave it alone.

Prefer a quick chat? Call 0425 531 127. We answer the phone in Perth.