Legacy Rescue · Visual FoxPro

Visual FoxPro Migration UK: A Safe Exit Plan

Microsoft ended all support for Visual FoxPro on 13 January 2015 and confirmed back in 2007 that there would never be a version 10. A VFP system can still leave calmly: data extracted, behaviour rebuilt as a modern web application, the old system live in parallel until the new one has proven itself.

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

Is Visual FoxPro end of life?

Yes, completely. Mainstream support ended on 12 January 2010 and extended support on 13 January 2015. Microsoft announced in March 2007 that there would be no VFP 10, and no Windows release after Vista was ever officially supported. Every VFP system running today does so outside vendor support.

Final version VFP 9.0, December 2004
No VFP 10 Confirmed by Microsoft, March 2007
Mainstream support Ended 12 January 2010
All support Ended 13 January 2015
Architecture 32-bit only, 2 GB per table
Out of all support since 2015
SYSTEM STATUS VFP 9.0 SP2
SUPPORT ENDED . : 13/01/2015
VFP 10 . . . . : NEVER
MAX TABLE SIZE : 2 GB, FIXED
LAST OS TESTED : WINDOWS VISTA
PRESS ANY KEY TO WORRY
Sources: Microsoft lifecycle: Visual FoxPro 9.0 · Microsoft: A Message to the Community (2007) · Microsoft Visual FoxPro FAQ · NCSC Cyber Essentials requirements · IT Jobs Watch: FoxPro (VFP)
Staying costs too

The risks of staying on FoxPro

  • Unpatched since 2015 Any flaw found after extended support ended stays unpatched forever. There is no vendor to call and no fix coming.
  • Unsupported on modern Windows No Windows after Vista was ever officially supported for VFP 9. Every Windows update is a gamble with no recourse if it breaks the app.
  • The 2 GB wall VFP is 32-bit only with a hard 2 GB per-table limit Microsoft declined to lift. Growing data eventually hits a ceiling that cannot be raised.
  • A vanishing talent pool IT Jobs Watch recorded zero permanent UK adverts citing FoxPro in the six months to June 2026. The community VFPX project is volunteers, not vendor support.
  • Cyber Essentials exposure The NCSC requires unsupported software to be removed or isolated from the internet. A live VFP system can cost you certification.
Honest trade-offs

Your exit options, compared

OptionWhat it means RiskVerdict
Stay Keep running unpatched VFP 9 on unsupported Windows. Every Windows update is unsupervised risk; ends in a forced exit. Borrowed time.
Refactor Move the data to SQL Server, keep the VFP front end. Buys headroom; the front end stays unsupported and unstaffable. A stopgap, sometimes useful.
Replace Off-the-shelf package, migrate the data. Decades of bespoke logic rarely fit a package. Works for simple systems.
Rewrite Rebuild as a modern web application, parallel run, then cut over. Managed by the parallel run; old system stays live. 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.

VFP specifics: .dbf tables, .fpt memo files and .cdx indexes are open formats that extract cleanly over ODBC or OLE DB. Data moves to a modern SQL schema first; the application layer is rebuilt against it.

The safety net

The parallel run is the proof.

We do not ask you to trust a brochure. Your FoxPro 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 FoxPro owners

Questions

Can you read our FoxPro data?
Yes. VFP stores data in open .dbf files with memo and index files alongside. Extraction over ODBC or OLE DB is routine; mapping it well is the skilled part.
The system still works fine. Why move now?
Because it works until Windows changes something, and Microsoft has not tested VFP against any Windows since Vista. Exits are calm when chosen and rushed when forced.
What about FoxPro 2.6 and the DOS versions?
Handled the same way. The data formats are simpler, and the screens are rebuilt rather than converted.
Could we keep part of the system in VFP for now?
Yes, via a staged exit with the database moved to SQL first. The Roadmap compares a staged route against a clean rebuild honestly, with prices for both.
Our tables are near 2 GB. What happens then?
VFP has no supported way past that limit. Archiving buys months; migration is the fix. If you are close, say so on the audit call and we will prioritise it.

Get a straight answer on your FoxPro system.

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