Seven reasons to modernise FoxPro beside it, not instead of it.
Sidecar mirrors your Visual FoxPro data into Postgres, SQL Server or MySQL as it changes, or into almost anything else through ODBC. It is built for systems whose data is still in .dbf files. Your reports, web apps and integrations get the data. Your business keeps the system it already trusts.
-
Reach your data
Your data finally gets out of the old application.
Most of the pain in a FoxPro estate is not the application. It is that reports, dashboards and web access all wait on files that only the desktop program can open. Sidecar keeps a live copy in a modern database, so anything that speaks SQL can use it.
The solid path is on from day one. The dashed write-back path stays off until you enable it, one table at a time.
-
Zero footprint
Nothing about your FoxPro files changes.
Your data files are the part of the system you cannot afford to damage. Sidecar is built around that fact.
- Opened read-only. Sidecar never writes to a .dbf, .fpt or .cdx file.
- No schema changes. No new columns, indexes or triggers. Its own bookkeeping lives in a separate file.
- Polite with live users. When FoxPro holds a lock, Sidecar waits and retries with a short back-off, then checks the table did not change mid-read.
-
Go at your own pace
You adopt it in four small steps, each one reversible.
Stop at any step. Many sites get real value from step one alone.
- 1. MirrorA read-only copy of your tables appears in the cloud. Point reporting and BI tools at it.
- 2. ProveScheduled row counts and checksums show the copy matches, so trust rests on evidence.
- 3. Write backLet a new web form or integration update chosen tables, trialled in dry-run first.
- 4. MigrateMove modules to new applications one at a time. Retire FoxPro last, or never.
mode inbound_only target postgres (supabase) tables 42 mirrored, 3 held back customer 18,204 rows synced 2s ago invoice 141,877 rows synced 2s ago stock 6,310 rows synced 9s ago orderlines no key one-way, by content hash buffer 0 queued conflicts 0 last reconcile matched 42 / 42 tables
Illustration of the status view. The dashboard, a live activity log and a help button on every page are described on the features page.
-
Safe write-back
FoxPro wins every conflict.
Writing back is where most sync tools earn their bad reputation. Sidecar treats it as optional and cautious.
- Off by default. Allow-listed per table, with a dry-run mode that logs what would happen.
- Checked before every write. If a user changed the record first, the incoming change is held back and both versions are logged.
- Through the official route. Updates go via the Microsoft FoxPro OLE DB provider, so indexes and memo files stay intact.
- A kill switch. Drop in one file, or stop the service, and writes halt within a second.
-
Resilience
A dropped connection loses nothing.
Offices lose internet. Servers restart. Changes are held in a durable local queue, not in memory, and replayed in order once the cloud database is reachable again. Where a table has no key, Sidecar says so, mirrors it one way and refuses to write back to it.
-
No lock-in
You pick the database your team already knows.
The same engine targets each of these, so you are not tied to one vendor. It reads FoxPro 2.x and Visual FoxPro tables, including memo fields, deleted-record flags and legacy code pages.
PostgreSQL Supabase SQL Server MySQL Any other database by ODBC (mirror only) -
Low-risk start
It begins with a read-only assessment, not an install.
Send a copy of your data folder, or run the scanner yourself. You receive a report on tables, keys, field types, code pages and anything unusual, before anything touches a live system.
What owners and developers ask first.
Will it change my FoxPro files?
No. Sidecar opens the files read-only and never modifies them. Its own bookkeeping lives outside your data folder.
Can people keep using the FoxPro application while it runs?
Yes. Sidecar waits and retries when a record is locked, rather than forcing its way in.
What if a table has no primary key?
Many FoxPro tables have none. You can declare a key per table. Tables without one are mirrored one way only, using a content fingerprint.
Does the machine need Visual FoxPro installed?
Not for mirroring, which reads the file format directly. Write-back needs the Microsoft FoxPro OLE DB provider, which is 32-bit, so Sidecar runs that part as a small separate helper.
Begin with a read-only assessment.
We report back on what is in your data folder and what a safe first step looks like. No commitment.