Do you need all 80k rows of data for developing?

Can you use some fake data in your local dev database (let's say 100 rows which is easily faked and seeded as often as you want) and have the whole real 80k rows on production database?

so, use fake data on dev, but use real ones on production? Wait a second, that make sense. Why I didn't think of that? thank you for the answer. I'll try

I have a national-scale master data of my country's cities, districts, and villages. There's 80k rows on the village table.
I need to make the migration for a project, but inserting all 80k of rows into seeder doesn't seem realistic to me. On the other hand, if I add the table directly into the DB, the table will be gone every time I hit migrate:fresh.

How should I insert the master data? Should I put it on another schema? (I'm using mysql btw)