Visual FoxPro end of life: your options in 2026

Microsoft announced in 2007 that there would be no new versions of Visual FoxPro after version 9, and extended support ended in January 2015. There have been no security updates, bug fixes or official help for over a decade.

Yet thousands of UK businesses still run on it: stock control, job costing, accounts, membership databases, bespoke order systems. Many were written in the 1990s or 2000s by a developer or small software house that has long since moved on. They’ve kept working because FoxPro was genuinely good at what it did.

The question isn’t whether FoxPro still works. It’s how much risk you’re carrying by relying on it.

The real risks

People. The number of developers who can confidently read and change FoxPro code shrinks every year. If your system depends on one person, internal or external, that’s your biggest exposure.

Windows. Visual FoxPro is 32-bit software on a platform that is increasingly 64-bit and cloud-first. It still runs on Windows 11 today, but new PCs, updates and security tools regularly break things, as anyone who has seen the support library error will know.

Data. FoxPro tables have a 2GB size limit, can be corrupted when networks misbehave, and lack the security and audit controls that customers, insurers and Cyber Essentials assessors now expect.

Integration. Your FoxPro system probably can’t talk to your website, online accounts, CRM or phone system without someone re-keying data or passing spreadsheets around.

Your five options

1. Stabilise and document

If the system works and the business isn’t ready to change, the sensible minimum is to document it, back it up properly, make sure the runtime set-up can be reproduced on a new PC, and have someone available who can support it. Low cost, buys time, fixes nothing long term.

2. Move the data, keep the screens

Your tables can move into SQL Server or PostgreSQL while the familiar FoxPro screens stay in place. That removes the size limit and the corruption risk, and opens your data up to reporting and other systems, while spreading the cost of change.

3. Convert the code

Tools exist to carry FoxPro code across to modern platforms such as .NET, and AI-assisted tools now make it far quicker to analyse and translate old code than it was even two years ago. This suits well-structured systems with a lot of business logic worth keeping.

4. Rebuild as a modern web application

For systems that have outgrown their original design, a rebuild lets you drop years of workarounds, add remote and mobile access, and connect to everything else. Done one module at a time, it doesn’t have to be a big-bang risk.

5. Replace with a packaged system

If your FoxPro system does something standard, such as accounts, stock or CRM, a platform like Odoo may cover most of it out of the box, with your history migrated across and the gaps built as add-ons. See replacing old FoxPro accounting and stock software.

Which is right for you?

It depends on how critical the system is, how unusual your processes are, how good the original code is, and your budget and timescale. That’s what our fixed-price Health Check is for: we review your system, data and set-up, then give you a written report with the risks and costed options, so you can decide with real information rather than guesswork.