One of the reasons you want to use migrations is to avoid that kind of
error.
The schema_migrations table automatically keeps track of what
migrations have been applied and which have not.
You don't want to see errors for duplicate columns or duplicate
tables.
Have you been using migrations from the beginning of your project?
Or perhaps you are trying to convert to using migrations for a
database schema that already exists?