title: How to reset migrations in Django 1.7
body: <p>(I know there is a title the same as this, but the question is different). </p>
  
  <p>I have managed to get my development machine migrations and production migrations out of sync. </p>
  
  <p>I have a Django app which was using South. I had my own workflow that worked fine (it probably wasn't the correct way to do things, but I had no problems with it). </p>
  
  <p>Basically I have a script that copies the production database dump to my development machine. It also copied the migration files. That way the two were in synch, and I could run South commands as normal. </p>
  
  <p>Now I have upgraded to 1.7, and started using migrations. When I use my previous workflow (copy database dump, and migration files from production), it is not detecting changes on my development machine.</p>
  
  <p>I have read through the migrations document, and I see that the correct way to use it is to </p>
  
  <ol>
  <li>run "make migrations" and "migrate" on my development machine.</li>
  <li>run "migrate" on my devlopemnt machine to actually make the database changes</li>
  <li>Copy changes over, including migration files.</li>
  <li>run "migrate" on the production machine. (without the "makemigrations" step)</li>
  </ol>
  
  <p>Anyway. It is all a mess now. I would like to "reset" my migrations and start from scratch, doing things properly from now on.</p>
  
  <p>What do I need to do? </p>
  
  <ol>
  <li>Delete the contents of the migration table (on both machines)?</li>
  <li>Delete the contents of the migration folder? (Including the <strong>init</strong>.py file).  </li>
  <li>Start the migrations as per the documentation for a new one.</li>
  </ol>
  
  <p>Have I missed anything?
  Is there a reason why copying everything from production(database and migration files) doesn't detect any changes on my development machine afterwards</p>