How to Remove Old Database Migrations in Ruby on Rails
Rails data migration should be performed in accordance with some rules, tips and notes, so that you won’t need ages to finish it. This is all the more important when you are tasked with creating a clear development environment setup, and removing old records is key. Check how we did that when we overtook one of the Ruby projects.

Recently we’ve overtaken a big project for maintenance and further development. It’s a Rails application with many models, controllers and of course lots of database migrations. There were about one hundred files in db/migrate directory. The question is: how can we setup development environment with current database structure? Running rake db:migrate
would just be a suicide. It won’t simply work, because these migrations were written long time ago and the current code and models implementation don’t fit them. Instead let’s load schema.rb
file using this command:
tsx
It will create all needed tables for models and also a special table schema_migrations
to track migrations. Selecting all rows you will see something like this:
tsx
So, how can we use this special table to get rid of smelly migration files?
The solution
We can just create new migration and copy all add/create statements from schema.rb
tsx
The migration can look like this:
tsx
Then we need to change it a little bit, because we don’t won’t to lose any data while deploying new migration to staging or/and production environment. Just remove force: true
option to make sure we will never lose any data by recreating tables. So let’s try to run this new migration:
tsx
Yes, well, it didn’t work, because we’ve already loaded schema.rb
and all our tables are already there. So what can we do? We can use the latest version of migration from our schema_migrations
and rename the new one:
tsx
Finally, we can remove all migrations excluding the current one:
tsx
Now, if we run db:migrate
we won’t see any results or errors because we’ve have already migrated the database. However, if we have to setup a new environment we can run all (one) our migrations without any problems.
What’s left?
There is a small problem with this solution. If you have migrations which are modifying data like adding admin account or so, you need to find them manually and copy the code to our structure migration or add a new migration. The data is not included in schema.rb
Ending…
We just removed all migrations by adding new one with the whole structure. We can now continue hacking and adding new migrations in normal way. Above steps can be repeated any time we want. So, you can keep small number of migrations. Just be careful when you have new migrations on your local branch, but they are not deployed to staging or production yet. It won’t work. You need too rollback your local migrations until it matches staging/production and then copy schema.rb
Thanks all for now. Thank you and bye :)
Let’s Create a Great Website Together
We'll shape your web platform the way you win it!
More posts in this category
August 26, 2025 • 15 min read
READ MOREChoosing the Right Website Platform: CMS Comparison, Scalability, and Ownership Explained
For years, we’ve witnessed architectural transformation of CMSes, and the shift from monolithic systems to decoupled, API-first architectures that define modern web development. So, the question is no longer simply "which CMS?" but rather "which architectural philosophy" best aligns with your business goals.
August 11, 2025 • 12 min read
READ MOREHow Much Does Website Development Cost and How Long Does It Take?
Planning a website development project can feel overwhelming, especially when you're trying to balance quality, functionality, and budget constraints. Understanding the real costs and timelines will help you make smart decisions and avoid expensive surprises.
July 30, 2025 • 13 min read
READ MOREHow Fast Should Your Checkout Process Be for Maximum Conversions?
Imagine losing $2.5 million in annual revenue because of a single second. Sounds dramatic? If your online business generates $100 million yearly, a mere one-second delay in your checkout process could cost you exactly that much. This is neuroscience, backed by decades of research into how the human brain processes digital experiences.