schema-migration

This is an extension to this question: How to move a model between two Django apps (Django 1.7) I need to move a bunch of models from old_app to new_app . The best answer seems to be Ozan's , but with required foreign key references, things are bit trickier. @halfnibble presents a solution in the comments to Ozan's answer, but I'm still having trouble with the precise order of steps (e.g. when do I copy the models over to new_app , when do I delete the models from old_app , which migrations will sit in old_app.migrations vs. new_app.migrations , etc.) Any help is much appreciated! Migrating a

This question already has an answer here: How do I migrate a model out of one django app and into a new one? 7 answers I made the stupid mistake of creating too many models in the same Django app, now I want to split it into 3 distinct ones. Problem is: there's already data in production in two customers' sites, so I need to carefully plan any schema/data migration to be done (I'm using django-south). I'm unsure on how to proceed, any advice would be greatly appreciated. (I'm using PostgreSQL on a Ubuntu server 12.4 LTS, if that's of any relevance) I thought about using db.rename_table , but

I quite like Rails' database migration management system. It is not 100% perfect, but it does the trick. Django does not ship with such a database migration system (yet?) but there are a number of open source projects to do just that, such as django-evolution and south for example. So I am wondering, what database migration management solution for django do you prefer? (one option per answer please) I've been using South , but Migratory looks promising as well. Migratory looks nice and simple. We use Django at work, and we've been using dmigrations . While it has its quirks, it's been useful