How to migrate Django from SQLite to PostgreSQL

migrate-django.md

How to migrate Django from SQLite to PostgreSQL

Dump existing data:

python3 manage.py dumpdata > datadump.json

Change settings.py to Postgres backend.

Make sure you can connect on PostgreSQL. Then:

python3 manage.py migrate --run-syncdb

Run this on Django shell to exclude contentype data

python3 manage.py shell

>>> from django.contrib.contenttypes.models import ContentType
>>> ContentType.objects.all().delete()
>>> quit()

Finally:

python3 manage.py loaddata datadump.json

Source: https://stackoverflow.com/questions/3034910/whats-the-best-way-to-migrate-a-django-db-from-sqlite-to-mysql

tables created, ok, but data were not inserted!

because datadump.json have no data user data

How did you resolve the issue. I carried out the instructions successfully, and it showed [Installed 156 objects from 1 fixture]. But there is no data when i see in the web-app or in the pgadmin4. Any help is appreciated.

Error migrating from MySQL to MSSQL

To not found error when use loaddata to load fixture, exclude contenttype and auth.Permission modules. So the dump line will be:

python manage.py dumpdata --exclude=contenttypes --exclude=auth.Permission > datadump.json

I found this help on: https://coderwall.com/p/kogbla/django-fixture-dumpdata-loaddata-and-integrity-error

This worked for me. Thanks

Error migrating from MySQL to MSSQL

Try this:

> python manage.py shell
from django.contrib.contenttypes.models import ContentType
ContentType.objects.all().delete()

To not found error when use loaddata to load fixture, exclude contenttype and auth.Permission modules. So the dump line will be:
python manage.py dumpdata --exclude=contenttypes --exclude=auth.Permission > datadump.json
I found this help on: https://coderwall.com/p/kogbla/django-fixture-dumpdata-loaddata-and-integrity-error

This worked for me. Thanks

This works for me also. I was not able to go back and do the data dump in the proper way as most of the web suggests.
I needed to have the loaddata adjusted to work.
Why does every assume you have the original data to do the dump again away?
If you have loaddata issues try the the suggestion at https://coderwall.com/p/kogbla/django-fixture-dumpdata-loaddata-and-integrity-error as stated above.

For those with django.db.utils.IntegrityError duplicate entry.

Check if you have any signal creating content post_save, etc.. Comment those and run the process again.

https://stackoverflow.com/questions/75122526/psycopg2-duplicate-key-value-violates-unique-constraint-when-migrating-from-sql

It worked well for me to migrate database models and data from sqlite3 to PostgreSQL as promised.
Thank you, @scarabeo7 !

It is not working for me, when I run python3 manage.py migrate --run-syncdb, after change settings.py to Postgresql, I get the following Error: django.db.utils.ProgrammingError: relation "etl_categories" does not exist Am I making a mistake? SOLVED: Yes I was making a mistake. Since some views and forms in my app use some Models, when I run "python manage.py migrate" the ERROR above appear. If you are having the same problem just delete or comment all your views, forms and urls that uses any model. Then Follow the steps (migrate, load again your data) and finally uncomment/restore your files.

@gamonsalve, thanks!!