SQL Server to FoxPro Converter

SQL Server tables and rows into files Visual FoxPro opens, 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 →

Export SQL Server tables into FoxPro files. DBConvert writes the tables, memo files, and indexes itself; Visual FoxPro opens the result.

Reads SQL Server tables.
Writes a Visual FoxPro .dbc database (created when it is missing) or a folder of free tables. Visual FoxPro opens what is written: .dbf, .fpt, .cdx, and .dbc.
Nothing to install for FoxPro: no Visual FoxPro OLE DB driver, no Visual FoxPro. Runs on Windows as a desktop application.
The same download reads FoxPro into SQL Server.

What it writes

Codepage of new tables

Set Codepage of new tables in the destination settings. 1252 is the default.

A .dbc or a folder

Write into a .dbc database, created when it is missing, or into a folder of free tables.

Files Visual FoxPro opens

The application writes the .dbf, .fpt, .cdx, and .dbc files itself.

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.

Where it refuses

Text the chosen codepage cannot hold is refused, not written as ?.
An index tag other than plain fields, STR, DTOS, or LOWER blocks writing into that table.
A FoxPro table is capped at 2 GB.

Supported versions and services

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

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

DBConvert Studio

30+ databases · cloud · scheduled sync

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

How to migrate SQL Server to FoxPro

Setup: connect SQL Server and FoxPro

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 SQL Server source and FoxPro destination side by side, and the job name

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

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

SQL Server source

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

FoxPro target

Write to a .dbc database (created when it is missing) or a folder of free tables. Choose the Codepage of new tables; 1252 is the default.

Tables & mapping: see every FoxPro type before a row moves

Pick the tables, then open one: each SQL Server column shows the FoxPro 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 SQL Server to FoxPro: the table list and one table's columns with their FoxPro 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 SQL Server to FoxPro 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 SQL Server ↔ FoxPro

Move SQL Server data into FoxPro

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