FoxPro to SQL Server Converter

Tables and rows into SQL Server, once or as a sync, with saved jobs you can run again.

Version: 5.4.3
Release Date: Oct. 29, 2026
Size: 131.5 MB
Platform: Windows 10 or later

Download DBConvert Order from US$ 199

Rather not run it yourself?

Let us do the migration →

Copy a FoxPro database into SQL Server without writing the target schema by hand. DBConvert reads the .dbf files itself and creates the tables before it moves a row.

Reads a Visual FoxPro .dbc database or a folder of free tables. Plain dBase III and IV files read too.
Writes to SQL Server.
Converts once, or keeps SQL Server in step with FoxPro as a sync. The same download converts SQL Server back into FoxPro.
Nothing to install for FoxPro: the application reads the files itself. Runs on Windows as a desktop application.

What it reads

Text in its own codepage

Text is read in each table's own codepage. Field names arrive in lower case, as Visual FoxPro shows them.

Keys and relations

Candidate tags become unique keys, the .dbc primary tag the primary key, and relations foreign keys.

A .dbc or a folder

Pick a .dbc database, or a folder of free tables. Memo files (.fpt) and indexes (.cdx) stay with the tables.

A job keeps both connections, the table selection, and the options. Run it again from the application, or by name from Task Scheduler with --run-job.

What to know

A tag expression such as LEFT(name,3) has no SQL index. It is logged and the index is skipped.
A FoxPro table is capped at 2 GB.

Supported versions and services

FoxPro

Visual FoxPro .dbc databases and folders of free tables
Plain dBase III and IV files read too
Nothing to install for FoxPro: the application reads and writes the files itself

SQL Server

SQL Server 2008-2022, including Express editions
Azure SQL Database and Amazon RDS for SQL Server
SQL Server schemas (dbo, custom schemas)
Windows authentication or SQL authentication

DBConvert Studio

30+ databases · cloud · scheduled sync

Need more database pairs? One tool covers 30+ databases.

How to migrate FoxPro to SQL Server

Setup: connect FoxPro and SQL Server

Pick Convert or Sync, then choose the source and destination connections side by side on one screen. A connection is saved once and reused by every job.

The Setup step in DBConvert: the mode, the FoxPro source and SQL Server destination side by side, and the job name

Sync keeps an existing SQL Server database up to date with FoxPro: each run carries only the inserts, updates and deletes since the last one.

The Setup step in Sync mode for FoxPro to SQL Server: how changes are detected and the direction

FoxPro source

Select a .dbc database or a folder of free tables. Text is read in each table's own codepage.

SQL Server target

Use TCP/IP or Named Pipes, Azure SQL, or the RDS connection guide.

Tables & mapping: see every SQL Server type before a row moves

Pick the tables, then open one: each FoxPro column shows the SQL Server type it becomes. Change a type or a name in place; the line at the bottom names anything that would fail.

Tables and mapping for FoxPro to SQL Server: the table list and one table's columns with their SQL Server types

Execution: start it, and the job is saved

Review what the run will do, start it, and read the log as it goes. The job stays in the list to run again or put on a schedule.

A finished FoxPro to SQL Server conversion: the summary and the operation log

Every option, in the guide

Naming rules, table options, row filters, scheduling and the command line work the same for every database pair, so they live in one place.

Open the full guide

See all features

More guides for FoxPro ↔ SQL Server

Move FoxPro data into SQL Server

Download the current build and run the first job against your own database.

Download DBConvert 5.4.3 Order from US$ 199

Windows 10 or later · 131.5 MB