Legacy Rescue · Clipper / dBase

Clipper and dBase Migration UK: A Safe Exit Plan

CA-Clipper last shipped on 20 May 1997, and the dBASE line has had no release since 2019, with its vendor effectively gone dark in 2026. DOS xBase programs cannot run natively on 64-bit Windows. The data can still be extracted cleanly and the system rebuilt as a modern web application, without losing a record.

Book a free Legacy Risk Audit Back to Legacy Rescue
The facts

Are Clipper and dBase end of life?

Unambiguously. CA-Clipper’s final release was 5.3b in May 1997, and Computer Associates exited via a licensing deal in 2002. dBASE last shipped in 2019; by 2026 its newsgroups and online store had gone dark. Compiled DOS executables from either platform cannot run natively on 64-bit Windows, which is the only kind Windows 11 comes in.

CA-Clipper, final release 5.3b, 20 May 1997
dBASE, last release dBASE 2019
dBase LLC store Reported offline, May 2026
16-bit DOS programs No 64-bit Windows runs them
Windows 11 64-bit only
Vendor support: none, anywhere
SYSTEM STATUS CLIPPER 5.2
LAST VENDOR FIX : 1997
RUNS ON . . . . : DOS / 16-BIT
WINDOWS 11 . . : INCOMPATIBLE
SURVIVES VIA . : ONE OLD PC
PRESS ANY KEY TO WORRY
Sources: Microsoft: 16-bit programs on x64 Windows · Microsoft: NTVDM and 16-bit app support · The Register on dBase (May 2026) · NCSC: obsolete products
Staying costs too

The risks of staying on Clipper or dBase

  • The hardware is the runtime These systems survive on ageing machines or emulators. Microsoft recommends the only built-in DOS layer, NTVDM, be switched off in business environments.
  • No patches since the 1990s Clipper has had no vendor fix since 1997. The NCSC’s advice on obsolete products is blunt: the only full mitigation is to stop using them.
  • Vendor extinction dBase LLC’s newsgroups went dark in late 2025 and its online store was reported offline in May 2026. Replacement licences and media may not be obtainable at any price.
  • A retiring talent pool Almost no new commercial Clipper work has been written since the mid-1990s. The remaining expertise clusters around a volunteer open-source compiler.
  • Certification risk Cyber Essentials requires unsupported software to be removed or isolated from the internet entirely. A live DOS system on the main network is a finding waiting to happen.
Honest trade-offs

Your exit options, compared

OptionWhat it means RiskVerdict
Stay Keep the old PC alive and hope. A power cut or disk failure could end the system permanently. The riskiest square on this page.
Refactor Recompile surviving source with the open-source Harbour compiler. Needs source code; you remain on a niche, volunteer-run stack. A stopgap where source exists.
Replace Off-the-shelf package, migrate the data. Decades of bespoke logic rarely fit a package. Works for simple systems.
Rewrite Extract the .dbf data, rebuild as a modern web application. Managed by the parallel run; the old PC stays on until proven. Our method.
The process

How the migration runs

  1. Audit

    A free 30 minute call plus a written one-page risk summary.

  2. Roadmap

    Code and data audit, migration options, fixed-price proposal. £1,950, credited against the build.

  3. Parallel run

    Your old system stays live until the new one has proven itself.

  4. Cutover & aftercare

    Switch over when ready. We stay on hand.

xBase specifics: Clipper and dBASE store data in open .dbf tables with memo and index files alongside. Indexes are regenerable, so the tables are the canonical extraction target, and they read cleanly into a modern SQL schema.

The safety net

The parallel run is the proof.

We do not ask you to trust a brochure. Your Clipper or dBase system stays live and primary while the new one runs alongside it, reconciled record by record until the comparison is boring. Cutover happens when you say so, with the old system kept as a fallback.

Read the Field Notes
Asked by Clipper or dBase owners

Questions

The system only runs on one old computer. What should we do first?
Image that machine this week, before anything else. A full disk image turns a catastrophic failure into an inconvenience while the migration is planned.
We lost the source code decades ago. Is migration still possible?
Yes. The .dbf data extracts without source code, and the behaviour is rebuilt from the running system and the people who use it.
Can it be made to run on Windows 11 instead?
Not natively; 64-bit Windows cannot run 16-bit DOS programs at all. Emulators exist and are useful as a stopgap, but they are a way of waiting, not an exit.
Is forty-year-old data even safe to move?
xBase tables are among the best-documented legacy formats there are. Extraction is routine; reconciliation during the parallel run proves nothing was lost.
Nobody here knows how it works any more. Is that a blocker?
It is normal. The audit maps what the system actually does from the running screens, the data and the people who use it daily.

Get a straight answer on your Clipper or dBase system.

Book a free Legacy Risk Audit
Replies within one working day, from the engineer, not a sales team.