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

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

Upload a .dbf file and get back a PGSQL 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 PGSQL

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

Your data	PGSQL 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 a .dbf file

A .dbf holds one table and describes its own fields in a header, so none of the structure has to be guessed. What it does not always hold is all of its data: long text lives in a second file beside it.

→The header is inspected before conversion, and if it declares a memo field with no companion file present the upload is refused with that companion's exact name - CUSTOMER.fpt, not "a memo file".
→That name is derived from your file's own stem plus the version byte in its header, and the check is case-insensitive because DOS-era files usually arrive in upper case.
→Upload the .dbf and its companion together in one request. Several files are accepted at once, and the 10 MB free limit applies to the total rather than to each file.

Loading into an application's database

PGSQL is the name PostgreSQL wears inside application code: PHP's pgsql extension, Laravel's pgsql connection driver, the pdo_pgsql DSN prefix. If that is where you met the name, the database you are loading into probably belongs to a framework, which changes what to watch for.

→The script creates its own tables. Point it at a schema your migrations own and the next migration run and this file will disagree about who defines the table - load into an empty schema, or a database of its own, and point the application at that.
→Because every identifier is double-quoted, the case the source used is the case that gets stored. A column that arrives as "CustomerID" has to be quoted in your queries too: an unquoted CustomerID folds to customerid and is not found.
→No FOREIGN KEY, index or view statement is generated at all, so a framework that introspects the database finds unrelated tables. Declare the relations in your models, or add them with ALTER TABLE once the rows are in.

Reading DBF

→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 PGSQL

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