FoxPro Migration Tools
FoxPro databases and free tables into SQL Server, MySQL, PostgreSQL, or SQLite, and back. One installer, one licence key.
Rather not run it yourself?
Let us do the migration →
What DBConvert for FoxPro does
It moves data between FoxPro and SQL Server, MySQL, PostgreSQL, or
SQLite, in both directions. FoxPro is a .dbc database or a
folder of free tables. One Windows installer and one licence key cover
every pair.
FoxPro into a database
- FoxPro to SQL Server
- FoxPro to MySQL, or to a MySQL dump
.sqlfile - FoxPro to PostgreSQL, or to a PostgreSQL dump
.sqlfile - FoxPro to SQLite
A database into FoxPro
How it works
-
Nothing to install for FoxPro. The application reads and writes the files itself, and Visual FoxPro opens what it writes:
.dbf,.fpt,.cdx, and.dbc. - Reading: text is read in each table's own codepage, and field names arrive in lower case as Visual FoxPro shows them. Plain dBase III and IV files read too.
-
Candidate tags become unique keys, the
.dbcprimary tag the primary key, and relations foreign keys. -
Writing: pick a
.dbcdatabase (created when it is missing) or a folder of free tables, and set Codepage of new tables. 1252 is the default. -
Convert once, or sync. A saved job runs again from the application, or from Task Scheduler with
--run-job.
Limits
-
Text the chosen codepage cannot hold is refused, not written as
?. -
An index tag other than plain fields,
STR,DTOS, orLOWERblocks writing into that table. - A FoxPro table is capped at 2 GB.
-
A tag expression such as
LEFT(name,3)has no SQL index. It is logged.
Forms, reports, .prg programs, and FoxPro business logic are
the application, not the database, and are not converted. Need help with
that part? See Migration services.