title: What does "Migrating a Django application" mean?
body: <p>I kept thinking a lot about the meaning of <code>migrating a Django app</code> the last few days and heard about migrating Django apps with <a href="http://south.aeracode.org/" rel="noreferrer">django-south</a>. Maybe it's just the lack of sufficient English skills (as English is not my native language) or this is one of the things you confront in a programmer's life which are so simple, that it takes a genius to understand them (at first).</p>
  
  <p>I've read the translation of 'migrate' in my native language, read the definition of <code>migration</code> on Wikipedia and read <a href="http://south.aeracode.org/wiki/About#TheIdea" rel="noreferrer">"the idea</a>" of django-south, citing:</p>
  
  <blockquote>
    <p>With South, you install it and then
    give one or more of your apps some
    migrations (either writing them by
    hand, or autogenerating them from your
    model definitions). When you syncdb,
    you'll only sync apps that don't have
    migrations (things like
    django.contrib.auth, for example,
    which have a fixed schema), and then
    when you run ./manage.py migrate,
    South kicks in and does the
    migrations. Intelligently.</p>
  </blockquote>
  
  <p>This is confusing and I still don't understand the whole thing behind "migration of django applications" or "migration in general". I'd understand if I'd know how to interpret the word <code>migration</code></p>
  
  <p><strong>You get the point, I hope.</strong></p>
  
  <p>Have patience with me, but I'd really like to know. So maybe one of you could explain me, please.</p>
  
  <p>Thanks for your time in advance.</p>