Convert FoxPro to SQLite3
Upload a .dbf file and get back a SQLite3 file. Types are preserved rather than flattened to text. Free, no registration, up to 10MB.
Click to upload or drag and drop
CSV, Excel, SQLite, SQL, DBF (max 10 MB)
How your data is typed in SQLite3
Generated from the converter's own SQLite3 type mapping — this is what it actually emits, not an example.
| Your data | SQLite3 type |
|---|---|
| Whole number | BIGINT |
| Decimal (money) | NUMERIC(10,2) |
| Floating point | REAL |
| True / false | BOOLEAN |
| Date | DATE |
| Date and time | TIMESTAMP |
| Short text | TEXT |
| Long text | TEXT |
| Binary data | BLOB |
Working from a FoxPro table
FoxPro extended the dBase file layout with types dBase never had, and gave its memo files a different format and a different extension. Both of those differences change what comes out the other side, and both are read from the file.
- →The FoxPro-only field types are read as themselves: Currency (Y) becomes an exact decimal rather than a float, Integer (I) a 64-bit integer, DateTime (T) a timestamp, Double (B) a floating-point number.
- →Memo text is expected in a .fpt, chosen from the Visual FoxPro and FoxPro 2.x version bytes 0x30, 0x31, 0x32, 0xF5 and 0xFB, rather than in the dBase .dbt.
- →Only the .dbf itself is read. A table bound to a Visual FoxPro database container keeps its long field names and relations in the .dbc, so columns arrive under the short names in the table header.
The .sqlite3 name and what carries over
The 3 in sqlite3 is the file format version and the name of the command-line tool, not a property of your conversion. One database file arrives, and the two things worth knowing about it are what it is called and what it leaves behind.
- →The file inside the zip is always database.sqlite, whichever spelling brought you to this page. Rename it to database.sqlite3, or to whatever a framework expects, once you have it - the header is what identifies it, never the extension.
- →An auto-increment column arrives holding all of its values and nothing that assigns new ones. No AUTOINCREMENT keyword is written, and the column is declared BIGINT rather than exactly INTEGER, so it is not an alias for the rowid either: rows you insert later have to supply their own key.
- →Only the rows are transactional. The very first CREATE TABLE runs in autocommit, and everything after it - that table's rows, and every later table - sits in one transaction that commits after the last row. A conversion that fails partway therefore leaves a file holding an empty shell of the first table and nothing else. You never receive that file: the zip is only assembled once the writer has returned.
Reading FoxPro
- →Numeric fields with decimals are read as exact decimals, not floats, so currency does not drift.
- →Visual FoxPro Currency fields become DECIMAL(19,4), their fixed four decimal places, and the hidden _NullFlags system column FoxPro keeps in each table is left out.
- →Character field widths are read from the header and carried into the target.
- →The code page declared in the file header is used, so Cyrillic, Western European and other legacy DOS encodings decode correctly instead of turning into mojibake. 157 code pages are recognised.
- →Files written by dBase III or Clipper declare no code page at all — the header byte for it did not exist yet. For those, the most plausible encoding is chosen by inspecting the text, and the conversion tells you it had to guess. The API takes a sourceEncoding parameter (e.g. cp866) to force it instead of guessing, though the widget above does not have a control for it yet.
- →Memo columns keep their text in a separate .dbt or .fpt file. If the .dbf declares one and it was not uploaded, the conversion stops and tells you which file to add, rather than handing you a table whose long text is silently blank.
Writing SQLite3
- →Columns get real declared types rather than everything being TEXT.
- →Primary keys and NOT NULL constraints are preserved.
- →A money column is declared DECIMAL_TEXT(10,2): because the type name contains TEXT, SQLite keeps 19.99 as written instead of converting it to a float. SQLite itself does arithmetic in floating point, so for exact sums in SQL pick the DuckDB target.
- →The same text storage means ORDER BY, min(), max() and comparisons treat money as text, so 99.23 sorts above 1007.64. Write CAST(column AS REAL) there; the README in the zip lists the columns.
What you get
A ZIP containing database.sqlite. If anything about your data needed a judgement call, a _warnings.txt explains it.
Questions
- Is converting FoxPro to SQLite3 free?
- Yes. Files up to 10MB convert free with no account. There is a limit of five conversions per day per IP address.
- Will my FoxPro data keep its types in SQLite3?
- Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real SQLite3 types rather than everything becoming text. The mapping table above shows exactly what you get.
- Do you store my file?
- No. The file is written to a temporary directory, converted, and the directory is deleted as soon as your download has been sent.