Is converting xBase to PostgreSQL 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 xBase data keep its types in PostgreSQL?

Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real PostgreSQL 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.

Convert xBase to PostgreSQL

Upload a .dbf file and get back a PostgreSQL SQL script you can load straight into your database. Types are preserved rather than flattened to text. Free, no registration, up to 10MB.

1Upload your file

Click to upload or drag and drop

CSV, Excel, SQLite, SQL, DBF (max 10 MB)

2Choose target format

How your data is typed in PostgreSQL

Generated from the converter's own PostgreSQL type mapping — this is what it actually emits, not an example.

Your data	PostgreSQL type
Whole number	BIGINT
Decimal (money)	NUMERIC(10,2)
Floating point	DOUBLE PRECISION
True / false	BOOLEAN
Date	DATE
Date and time	TIMESTAMP
Short text	TEXT
Long text	TEXT
Binary data	BYTEA

Working from an xBase table

xBase is the family name for the record layout dBase defined and Clipper, FoxBase and FoxPro adopted. A file from any of them opens here; the differences live in the header bytes, and those are read rather than assumed.

→Records deleted but never packed are still physically present, flagged with an asterisk. They are skipped, so the converted table holds the rows the application showed and not the ones it hid.
→Clipper is the trap in this family: it wrote version byte 0x03 even for tables with memo columns, so a naive reader picks the wrong memo layout and dies with "unpack requires a buffer of 8 bytes". That case is handled here.
→The header gives each field an 11-byte name slot, so xBase column names are at most 10 characters - a limit that follows the data into the target unless you rename the columns there.

What the PostgreSQL script contains

The conversion produces one dump.sql with a README beside it, zipped. It is a script you can open, grep and edit before you run it rather than an archive a tool has to unpack, and it is deliberately sparing in what it declares.

→Every string column is declared TEXT, whatever length the source declared for it. PostgreSQL stores a short value in a TEXT column exactly as cheaply as in a VARCHAR, and an unbounded column cannot reject a row on load for being a few characters too long.
→Identifiers are all double-quoted, and even so a name on PostgreSQL's reserved list is given a trailing underscore: a column called user arrives as user_, order as order_, limit as limit_.
→A decimal column whose source declared no scale is given six decimal places rather than none, keeping whatever precision it did declare: NUMERIC(10,6) from a source that said 10, and NUMERIC(18,6) from one that declared neither. A scale of zero would have the server round 19.99 to 20 as it loaded.

Reading xBase

→Numeric fields with decimals are read as exact decimals, not floats, so currency does not drift.
→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 PostgreSQL

→Backslashes are left alone, because PostgreSQL treats them as ordinary characters — doubling them would corrupt every Windows path.
→Auto-increment columns become GENERATED BY DEFAULT AS IDENTITY.
→Binary data is written as bytea, and identifiers respect the 63-character limit.

What you get

A ZIP containing dump.sql, plus a README with the exact command to load it. If anything about your data needed a judgement call, a _warnings.txt explains it.

Load this dump into PostgreSQL:

  psql -U USER -d DATABASE -f dump.sql

Create the database first if it does not exist:

  createdb -U USER DATABASE

Questions

Is converting xBase to PostgreSQL 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 xBase data keep its types in PostgreSQL?: Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real PostgreSQL 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.