 <p>South's main concern is handling issues regarding changes in relational db schemas. This is not required in a non-rel db, where smart coding practices and simple scripts can handle migrations as an online operation.</p> <p>See also:</p> <ul> <li><a href="http://code.google.com/appengine/articles/update_schema.html" rel="nofollow">http://code.google.com/appengine/articles/update_schema.html</a></li> <li><a href="http://code.google.com/p/appengine-mapreduce/" rel="nofollow">http://code.google.com/p/appengine-mapreduce/</a></li> </ul> <p>Keep in mind that many Django field types are <a href="http://www.allbuttonspressed.com/projects/djangoappengine#field-types" rel="nofollow">supported by djangoappengine</a>. This means you can use <a href="https://docs.djangoproject.com/en/dev/ref/django-admin/#django-admin-dumpdata" rel="nofollow"><code>dumpdata</code></a> on your sql project to save your data to files and later use <a href="https://docs.djangoproject.com/en/dev/ref/django-admin/#django-admin-loaddata" rel="nofollow"><code>loaddata</code></a> in your new project to load it into your models.</p> <p>If you need further processing, you can create a small script that copies data from the old models to the new models.</p>