title: How can I use Flask-migrate across multiple development environments
body: <p>I have flask-migrate (version 1.8.0) working well with a sqlite database in a development environment.  Now I would like to migrate our data to MySQL and maintain all of our migration history (so it stays in sync with our Flask-SQLAlchemy models in our git repository).</p>
  
  <p>I created an empty MySQL database, and after changing my SQLALCHEMY_DATABASE_URI, I tried running:</p>
  
  <pre><code>python manage.py db upgrade
  </code></pre>
  
  <p>That resulted in an error about not being able to drop the table migrate_version.  (Which makes sense, since this is a new database, although sqlite actually contains the table 'alembic_version' not 'migrate_version'.)</p>
  
  <p>So, I tried to initialize this new database:</p>
  
  <pre><code>python manage.py db init
  </code></pre>
  
  <p>Now I get an error: "Directory migrations already exists".  </p>
  
  <p>I can rename that folder and re-run the command with no problem, but then I lose all of my previous migrations.  I think we would have the same issues when we also transition to our test and production environments.  </p>
  
  <p>I've seen in the docs Flask-Migrate has multiple database support, but I think that looks to be more for maintaining multiple databases in a single development environment.  Is there a way to have Flask-Migrate track changes across multiple development environments?</p>