South run migrations per app not in order migrations where created. This may cause some problem with dependencies between migrations. Sometimes it's needed to add depends_on attribute to migration class.
Is it possible to run south-migration in order they were created? And also, anyone know reason why south is doing it this way?