I've searched for the answer in many places, but the only solution seems to generate the migrations files locally and push them to Heroku. That's something I wish I could prevent, but it is the only working option.
Hopefully, this will be solves as of Django 1.7, when migrations are built into Django. Until then, I moved away from Heroku.