Ask any company still running Visual FoxPro what keeps them up at night, and it is rarely the code. It is a person. The system works because one developer understands it, and that developer is getting harder to replace every single year. This is the risk that does not show up on a balance sheet until the day it does.
The talent problem is not a hunch. It is a straight line drawn from a date.
Why the pool is draining
Visual FoxPro's last release was in 2007, and Microsoft ended support in 2015. That means no new developer has learned FoxPro in a modern classroom, on a modern project, or as a path with a future for well over a decade. The people who know it learned it in its heyday, and that generation is now moving toward retirement. In the Stack Overflow Annual Developer Survey, which polls tens of thousands of developers on the languages they actually use, FoxPro does not register as a meaningful share at all. The pipeline is not slowing. It has effectively stopped.
The math of a shrinking supply
When supply falls and demand holds, price rises. That plays out in three ways for FoxPro:
- Higher rates. The remaining specialists command a premium, and it climbs every year as the pool thins.
- Slower hiring. A role that used to take weeks to fill can take months, or never fills at all.
- Less leverage. When one contractor is the only realistic option, you are negotiating from a position of weakness on both price and timeline.
The real number is the bus factor
The most expensive line item is not the hourly rate. It is the concentration of knowledge in one head. When a single person understands the business rules, the data quirks, and the undocumented workarounds, the business is one resignation, illness, or retirement away from being unable to change or even safely run its core system.
Ask the uncomfortable question: if the one person who understands your FoxPro system was unavailable for a month starting tomorrow, what would break, and who would fix it? If you do not have a confident answer, that is the risk, quantified.
Modernization is succession planning
Here is the reframe that changes the decision. Migrating off FoxPro is not only a technology project. It is how you turn a system that one scarce person understands into one that a broad, hireable market can maintain. A modern web stack on .NET, Go, or Node.js with a standard database is something you can staff from a deep talent pool, today and in ten years.
Better still, a proper migration is the moment the undocumented knowledge finally gets captured. Reverse-engineering the business logic during the move turns "whatever is in Bob's head" into a real specification that outlives any single employee.
Bottom line: the FoxPro talent market only gets tighter from here. The cheapest, safest time to move to a stack you can actually hire for is while your current expert is still around to help you do it, not after they are gone.
Not sure how deep your single-expert risk runs? A free assessment maps what your application does and how much of it lives only in one person's memory, with no obligation. It also pairs naturally with our look at what a migration costs and how long it takes.