Moving the Data

Moving the schema is easy. Moving the data is the work.

Django will create the tables in Postgres from your existing migrations without complaint. What it will not do is fix rows that were only ever valid because SQLite did not check them.

The audit, in order. Before moving anything, run these against the SQLite database and look at what comes back.

Columns declared as one type holding another.

Foreign keys pointing at rows that do not exist, which SQLite permitted while enforcement was off.

Duplicate values in a column you now want UNIQUE.

Nulls in a column you now want NOT NULL.

Text in a date column that will not parse.

Every one of those is a decision, not a delete. Fix it, or record why you dropped it and how many rows that was.