Earlier quoted context omitted.
+1 for code-first migrations. It's a bit of a learning curve, but the effort is worth it imo.
I prefer dB first. Create an SQL project that defines the schema. It automatically compares the schema with your current dB schema and auto generates a migration script for you. Then update entities from the dB. Few steps involved but avoids writing and maintaing migrations yourself.
I would like to suggest code-first, at least try it once.
I don't want to go back to any sort of migrations outside of this.