Convert SQLite to PGSQL
Upload a .sqlite or .db or .sqlite3 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 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 .sqlite file
SQLite is a complete relational database in a single file, which makes it both the easiest source to read and the one people most often need to get out of: the tables, names and constraints are already there to be carried over.
- →The database is opened read-only through a file: URI, so the file you uploaded is never written to, not even to tidy up after itself.
- →SQLite's own bookkeeping tables - anything named sqlite_%, such as sqlite_sequence - are left out. Every other table is converted, in alphabetical order.
- →Declared types are matched the way SQLite matches them, by substring, so VARCHAR(20), NVARCHAR and CHARACTER all land as text columns.
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 SQLite
- →Declared types, primary keys, NOT NULL constraints and blobs all carry through.
- →SQLite reports INTEGER PRIMARY KEY as nullable because it aliases the rowid; the conversion corrects that.
- →SQLite type affinity is loose, so a NUMERIC column with no declared scale is given room for decimals rather than being rounded to whole numbers.
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 SQLite 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 SQLite 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.