Database Schemas Module

I guess I misunderstood your question. Migrations and Schemas both are only intended to work with the table schema, not the data. I could see using migrations for some “fixtures”, like project-specific settings that would never change, but in most cases a Seeder would be more appropriate. If you’re looking for a complete database copying solution you might be better handling that outside the framework. I question though the desire to copy data from development to production - do you even want that?