Migration · By Rivtor · Updated
Move a Django application from SQLite to PostgreSQL
Treat a Django SQLite-to-PostgreSQL move as a database compatibility and data-migration project. Create the target schema from reviewed Django migrations, rehearse data transfer and validate constraints, sequences and application behaviour before switching the live database setting.
Compare Rivtor plans for your workload →
Test PostgreSQL before moving data
A Django application working on SQLite can still make assumptions about types, case sensitivity, locking, raw SQL or schema operations that differ on PostgreSQL. Run the application’s meaningful tests against a disposable PostgreSQL database before changing production.
Install a compatible PostgreSQL driver and use a private DATABASES configuration. Keep the source SQLite file unchanged as a recovery artifact. A local database file inside an ephemeral container is not an appropriate persistence strategy for a hosted multi-process service.
Rehearse the schema and transfer method
For a small application, Django’s serialization tools can be one part of a reviewed transfer workflow. Choose natural keys and exclusions deliberately for the application’s content types, permissions and relationships. Do not blindly apply a universal dumpdata command to every project.
| Step | Acceptance evidence |
|---|---|
| Target migrations | Expected tables and constraints exist |
| Data transfer | Counts and critical relationships match |
| Identity/sequence check | A new record does not reuse an existing key |
| Application test | Authorized read/write and authentication still work |
Some projects need a custom migration script rather than fixtures. Record the chosen method and rehearse it end to end on copies. Larger or actively written datasets require a more deliberate downtime and transfer plan.
Investigate differences instead of disabling checks
A target constraint failure may reveal data that SQLite accepted but PostgreSQL rejects. Preserve the error and inspect the specific records. Do not disable foreign keys or remove validation merely to complete an import faster.
Review Django deployment on Rivtor and data-service configuration if selecting Rivtor. Confirm the supported import path and privileges before planning the live change.
Freeze writes for the final transfer
Stop web, worker and scheduled writes before taking the final source snapshot. Validate the restored target, then switch the application connection. Run a synthetic create/read operation and inspect the first real requests.
After new records exist in PostgreSQL, a rollback to the old SQLite file would omit them. Define a reconciliation decision before cutover, and retain the original snapshot according to the application’s recovery requirements.