Microsoft ended support for Visual FoxPro on January 13, 2015. Here's an accurate look at what that means in 2026 — the real risks of staying, what inaction costs, and the migration paths available to you.
As a supported product — yes. Microsoft announced in 2007 that Visual FoxPro 9 would be the last version, mainstream support ended in January 2010, and extended support ended on January 13, 2015. Since then there have been no security patches, no compatibility updates, and no new versions — and there never will be.
As running software — not quite. Plenty of VFP and VFP9 applications are still in production today, quietly doing real work. That's the trap: because it still runs, the risk of staying feels theoretical right up until the day it isn't. (For the record, the "2007" date some articles cite as FoxPro's end-of-life is wrong — 2007 was the announcement that no new versions would ship; the actual end of support was January 2015.)
| Year | Milestone |
|---|---|
| 1984 | FoxBASE released by Fox Software — the FoxPro lineage begins. |
| 1992 | Microsoft acquires Fox Software and takes over FoxPro. |
| 1995 | Visual FoxPro 3.0 — the first object-oriented, "Visual" release. |
| 2004 | Visual FoxPro 9.0 ships — the final major version. |
| 2007 | Microsoft announces there will be no VFP 10; development ends. |
| Jan 2010 | Mainstream support ends. |
| Jan 13, 2015 | Extended support ends — Visual FoxPro reaches full end of life. |
VFP was a powerhouse in its day. But unsupported software compounds risk every year it stays in production.
Any vulnerability discovered after 2015 is permanent. There is no patch coming — your data and users stay exposed by design.
HIPAA, PCI-DSS, and SOC 2 require encryption, audit logging, and access controls that VFP cannot provide natively. Auditors increasingly flag it.
The FoxPro developer pool shrinks every year. When your maintainer retires, replacing them is slow, expensive, and sometimes impossible.
32-bit binaries, aging drivers, printing, and OS policy changes all chip away at compatibility — and nothing will be fixed upstream.
File-based DBF tables hit hard limits under concurrent users and growing data volumes. A modern database removes that ceiling entirely.
VFP runs on Windows desktops only. Remote work, tablets, and mobile access are unsupported, while competitors move to the browser.
"It still works" feels free, but staying on VFP carries a real, rising bill that rarely shows up on a single line item:
Migrating deliberately, while the system is stable and the people who understand it are still around, is almost always the cheaper path. The most expensive migration is the one you're forced into.
The goal isn't a like-for-like desktop clone — it's a supported, browser-accessible system that keeps your business logic and removes VFP's risks.
If you're not sure which path fits, that's normal — and it's exactly what a structured assessment resolves. We map your application, then recommend the lowest-risk route, often starting with a read-only data layer so you see value before committing to a full migration.
The cheapest migration is a planned one. Get a free assessment and a clear, phased plan — while your system is stable and the people who understand it are still here.
Get a Free Assessment