← Bionic Forms

Visual FoxPro replacement options in 2026, compared honestly

By Matt Bidwell · 28 August 2026

Every list of Visual FoxPro replacements I can find was written by somebody selling one. So is this one: I build Bionic Forms, and it appears near the bottom where a pre-launch product belongs. What I can offer instead is a question the other lists skip, the arithmetic where prices are published, and a straight answer about who should not move at all. Prices checked 18 August 2026 on each vendor's own pricing page, alongside the Access and FileMaker versions of this comparison; Ninox publishes in euros, so I quote euros. Where a vendor does not publish a price I say so rather than guess.

First, the question the other lists never ask

Is your FoxPro application actually a program?

That sounds rude and it is not meant to be. A great many VFP applications are a handful of related tables, forms over them, a few reports, and twenty years of procedural glue that exists because the tool of the day made you write it, not because the business logic was ever complicated. If that describes yours, then every answer below that starts with "rewrite it" is answering a question you do not have, and you will pay for a rewrite to end up with the same six tables.

If instead the value really is in the code — pricing engines, scheduling, regulatory calculations, decades of accumulated rules nobody can restate — then the rewrite answers are the honest ones, and the no-code answers, mine included, are a waste of your afternoon. Work out which one you are before reading the rest, because it splits this list in half.

The honest case for staying where you are

Visual FoxPro 9 was the last version, and Microsoft support ended on 13 January 2015. Eleven years later a great many VFP applications are still running businesses, which is the part vendor scare stories leave out. Nothing expires. Your application does not stop working on a date.

What is true is narrower and worth stating precisely. VFP is 32-bit, so it depends on the 32-bit compatibility layer current Windows still ships, which means relying on Microsoft continuing to carry something it stopped supporting. There are no security patches. And the practical risk in most shops is not technical at all: one person understands the code, and that person is closer to retirement every year.

If the application works, one person maintains it happily, and nothing external is forcing your hand, doing nothing is a defensible decision and I am not going to pretend otherwise in order to sell you something.

What actually forces the move

Roughly in the order it comes up: the person who wrote it leaves or retires; a customer or an auditor asks a question about supported software that you cannot answer well; somebody needs it on a Mac, or from home, or on a phone; or a Windows update breaks something and the fix takes a fortnight because nobody left knows the code.

Staying in the family: Xbase++ and PolarFox

Alaska Software's Xbase++ shares xBase and dBase ancestry with FoxPro, and the company has been open about wanting to be for VFP developers what it already is for Clipper developers. Xbase++ 3.0, codenamed PolarFox, is built around loading existing VFP projects, with a transpiler that turns PRG source into Xbase++ PRG with, they say, minimal changes.

Two things to weigh honestly. This is the closest thing on the list to keeping what you have rather than rebuilding it, which for a genuine program is a very large advantage. And as of April 2026 V3 was in an Early Experience Program with a selected group of developers rather than generally available, so check where it has got to before planning around it. Alaska Software does not publish a price I could find, so I will not quote one.

Putting the same application on the web: FoxInCloud

FoxInCloud takes a different angle: it adapts an existing VFP desktop application for the browser, moving the visual surface to a web client and leaving the events, business code and database broadly as they are. Their own material claims well over 99% of instructions unchanged.

If your trigger is "people need it from somewhere else" rather than "the code is a liability", this is the answer that changes least. Pricing is not published on the pages I could reach, so ask them.

Rewriting it properly

The .NET rewrite is the industry's default recommendation, and a real consultancy ecosystem exists around it. West Wind's Web Connection has served VFP shops moving that way for years, and firms like Servoy pitch a whole platform whose development model deliberately resembles VFP's forms and data sessions.

This is the right answer when the code is the asset. It is the wrong answer, and an expensive one, when the code was only ever plumbing. The cost that catches people is not the build; it is the third change request in year two, when the process has moved and the people who built it have to be booked again.

Microsoft Access, the sideways step

Access is the most common destination and deserves its own warning. It is a genuine step up in supportability and a genuine step sideways in architecture: still a file, still Windows-only, still one ceiling. And it brings VBA, which is the same "one person understands this" problem wearing a different hat. If you are moving because of the retirement risk, Access does not solve it.

The table-shaped tools

Prices below were checked 18 August 2026 on each vendor's own pricing page.

Ninox is free to five users, then EUR 25 per user per month, on Mac, iPad and the web. Knack is $49 a month billed annually, flat, unlimited users, with 20,000 records and 3 apps on Starter; the $19 quoted online is a three-month promotion. Zoho Creator is $8 per user per month on Standard, $20 Professional, $25 Enterprise, and its scripting language is Deluge, so FoxPro maintenance debt becomes Deluge maintenance debt held by one person again. Airtable, Baserow and NocoDB all have free tiers; Baserow is MIT licensed and free to self-host, which makes the exit real, while NocoDB is source-available under a Sustainable Use License rather than OSI open source. FileMaker is worth a look if Macs are the reason, with the caveat that its five-seat minimum on an annual term sets the floor whatever your headcount is.

The common thread, and the reason a FoxPro shop often bounces off all of them: these are hosted, online, per-seat products. If your application runs in a workshop, a warehouse or a van where the connection is bad, none of that list is what you had.

LibreOffice Base

Free, desktop, relational, and the closest free like-for-like shape. It answers the concurrency question badly: the bundled engine is described in the project's own Base Guide as a single-user database system, and real multi-user means running PostgreSQL or MariaDB yourself, which is precisely the skill the shop that just lost its FoxPro person does not have.

Where Bionic Forms fits, and where it does not

Mine is a desktop database app that works offline. The data lives in an encrypted SQLite file on your own machine and syncs to a server you choose, so it keeps working when the connection does not. You describe what you keep records of in plain English and it writes the schema, the forms and the views. Pricing is flat by what you build rather than per seat, so it is unlimited users on every plan, and one app is free permanently.

Now the parts that disqualify it, before you spend any time on me. It is pre-launch. There is no scripting language of any kind, which is a decision rather than a gap, so if your value is procedural logic I am not your answer. The Windows download is not code-signed, so Windows shows a "Windows protected your PC" warning the first time you run it and some antivirus flags it. There are no mobile apps. And offline is a desktop feature — the browser version needs a connection.

What migrates, and what you rebuild

Be clear-eyed here, because it is where the other lists are vaguest. Bionic Forms imports records from CSV. It does not read a .dbf, a .dbc or an .accdb, and there is no automatic conversion of a FoxPro application into a Bionic Forms one. The assistant builds a schema from your description of the work; it does not convert your existing program. Your data comes across. Your forms and reports get rebuilt, quickly, but rebuilt. If anybody promises you a one-click conversion of a twenty-year-old VFP application, ask them to demonstrate it on yours before money changes hands.

Ten people, a year

Annual list prices for ten people, against the nothing you pay for FoxPro today. LibreOffice Base: $0. Bionic Forms: $0 on one app, or $348 for ten. Knack: $588. Zoho Creator Standard: $960. FileMaker Starter: $2,280. Xbase++ and FoxInCloud do not publish prices, so they are a phone call. A .NET rewrite is not on this scale at all: it is a project, quoted in tens of thousands, and for a genuine program it may still be correct.

How I would choose

If the code is the asset, look at Xbase++ or a .NET rewrite and stop reading lists like this one. If people simply need it from elsewhere and the code is fine, FoxInCloud changes least. If it is really six tables and some forms, almost anything modern will do and the question becomes who maintains it, which argues for the tools with no scripting language, mine included, because there is nothing left for one person to hoard. If it must run where there is no connection, the list is short and I am on it. And if it works and nobody is forcing you, stay.

OptionPriceKeeps your code?Notes
Stay on VFP 9$0YesUnsupported since 13 January 2015, 32-bit, no patches. The risk is the person, not the date.
Xbase++ / PolarFoxNot publishedMostly, via a transpilerShared xBase ancestry. V3 was in an Early Experience Program in April 2026, not general release.
FoxInCloudNot publishedYes, claims over 99% unchangedMoves the visual surface to a browser; the rest stays.
.NET rewriteProject-pricedNo, it is a rebuildCorrect when the logic is the asset. Web Connection and Servoy serve this path.
Microsoft AccessBundled or standaloneNoStill a file, still Windows-only, and VBA recreates the one-person problem.
NinoxEUR 25/user/mo, free to 5NoMac, iPad and web. Published in EUR, so quoted in EUR.
Knack$49/mo flat, annualNoUnlimited users, 20,000 records on Starter. The $19 online is a 3-month promo.
Zoho Creator$8 to $25/user/moNoScripting is Deluge, so the maintenance debt moves rather than goes.
Baserow / NocoDBFree self-host, paid cloudNoBaserow is MIT. NocoDB is source-available, not OSI open source.
LibreOffice Base$0NoBundled engine is single-user per the project's own Base Guide.
Bionic Forms$0 one app, flat aboveNoOffline desktop, unlimited users, pre-launch. No scripting, and no automatic conversion.

Quick answers

Is Visual FoxPro dead? Unsupported since 13 January 2015, and still running businesses in 2026. Two conferences, Southwest Fox and Virtual Fox Fest, are still being held. Unsupported and dead are not the same word.

Can anything convert my VFP application automatically? Xbase++ aims to transpile the source, which is the closest thing on this list. Nothing in the no-code category does, mine included: there is no automatic conversion, and it does not convert your program, it rebuilds the shape from a description.

What if it has to work with no internet? That rules out most of the hosted list. Xbase++, FoxInCloud on a local server, a desktop rewrite, or Bionic Forms are what is left.

Open the live demo — no signup, no email, no card. It is Northwind rebuilt, so a FoxPro developer will recognise the shape immediately. Give it a few seconds on the first click: it is building you a real workspace rather than showing you a screenshot. Then read the Access version or the FileMaker version of this comparison, or the FoxPro page for what a migration actually involves.

And if you would rather not rebuild it yourself: describe the app your business runs on and we will build a working version and show you. No fee and no card — what we build fits the free plan, and we ask you to pay only once it is genuinely running your business.