"What will it cost, and how long will it take?" is the first question every FoxPro owner asks — and the honest answer is that anyone who gives you a number before understanding your application is guessing. But that doesn't mean the question is unanswerable. It means you need to understand the drivers, so the eventual number makes sense and you can shape it.
This is a no-spin look at what moves the cost and timeline of a Visual FoxPro migration, what realistic ranges look like, and — just as important — what it costs to do nothing.
Why there's no single price
"Migrate a FoxPro app" describes projects that differ by 50× in effort. A 12-form departmental tool with clean data is a different universe from a 400-form enterprise system with two decades of undocumented logic and a reporting suite nobody wants to touch. The price tracks the work, and the work tracks your specific application — which is exactly why a real estimate comes from a scoped assessment, not a rate card.
The seven cost drivers
Almost all of the variation comes down to these. Knowing them lets you predict roughly where your project will land:
- Number of forms / screens. The most visible driver — more screens, more to rebuild and validate.
- Business-logic complexity. How much undocumented calculation, validation, and workflow has to be reverse-engineered and verified. This is often the biggest hidden cost.
- Data condition. Clean, well-structured DBF data is cheap to migrate; tangled relationships, code-page issues, and decades of quirks are not. (See our DBF data guide.)
- Reporting. Heavy FoxPro report suites (FRX) take real effort to reproduce as modern dashboards, PDFs, and exports.
- Integrations. Each external system — payments, accounting, EDI, hardware — adds scope.
- Validation rigor. Regulated or financial systems need exhaustive parallel-run verification; that confidence has a cost, and it's usually worth it.
- Target stack. Your choice of .NET or open source affects licensing (SQL Server vs. PostgreSQL), hosting, and long-term cost of ownership.
Realistic timelines by size
Cost and time move together. These ranges are typical starting points; your assessment produces a precise, phased schedule:
| Application size | Typical timeline |
|---|---|
| Small — under 20 forms | 6–10 weeks. A focused departmental tool, simple data model, limited reporting. |
| Medium — 20–100 forms | 3–5 months. Complex business rules, multiple roles, custom reports. |
| Large — 100+ forms | 6–12 months. Enterprise systems with deep integrations and extensive reporting — almost always phased. |
The number nobody puts on the invoice: the cost of staying
A migration has a price tag. Staying on FoxPro has one too — it's just spread out and easy to ignore until it isn't:
- Rising risk. Every year unpatched raises the expected cost of a breach or an unfixable outage.
- Talent premium. Scarce FoxPro expertise costs more each year, concentrated in one or two key people.
- Opportunity cost. Every integration and analytics project you can't ship because the data is locked in DBF files.
- The forced-march premium. A migration done in a panic after a failure costs far more than a planned one — rushed, over a barrel, with no leverage.
The cheapest migration is the one you start while the system is stable and the people who understand it are still around. Waiting doesn't avoid the cost — it raises it.
How to spend less without cutting corners
- Phase it. Start with a low-risk read-only data layer — value arrives early, and confidence compounds into later phases.
- Preserve the logic. Reusing your existing business rules (via a parser and logic map) is far cheaper than re-specifying them from interviews.
- Choose a stack you can hire for. Lower long-term cost of ownership beats a clever choice nobody can maintain.
- Use tooling for the repetitive 80% and expert judgment for the 20% that decides success — not all-manual, not all-automated.
Bottom line: there's no honest flat price, but there is an honest process. Get the application scoped, weigh it against the rising cost of staying, and phase the work so you control the spend. That's how a migration becomes a budget line instead of a leap of faith.
Want a real number for your application? Our free assessment produces a scope, a phased timeline, and a plain-English plan — with no obligation.