Convert DuckDB to PGSQL

Upload a .duckdb or .ddb 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.

Click to upload or drag and drop

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

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 dataPGSQL type
Whole numberBIGINT
Decimal (money)NUMERIC(10,2)
Floating pointDOUBLE PRECISION
True / falseBOOLEAN
DateDATE
Date and timeTIMESTAMP
Short textTEXT
Long textTEXT
Binary dataBYTEA

Working from a .duckdb file

DuckDB keeps an entire analytical database in one file, with real types behind it - decimals that are decimals, and integers wide enough to be worth checking before you move them somewhere narrower.

  • Only the main schema is read. Tables created in another schema, or in a second database attached at query time, are not part of the conversion.
  • Views in main are read as though they were tables, so a view's rows are materialised into the target rather than skipped.
  • HUGEINT is the one type with nowhere to go: no target here has a 128-bit integer, so those columns are carried across as text rather than silently truncated.
  • A DuckDB process that was killed leaves a .duckdb.wal sidecar holding everything it had not checkpointed yet. Upload the database on its own and it opens with no error and no tables at all - send the .wal file alongside it, or checkpoint before you copy the database out.

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 DuckDB

  • Types, primary keys and NOT NULL constraints are read from the database.
  • The file is opened read-only, so your upload is never modified or upgraded in place.

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 DuckDB 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 DuckDB 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.

This conversion, under other names

Convert DuckDB to something else

Convert something else to PGSQL