I use .Net Core, and often make changes to data base through the application and the application updates the database in both staging/production. This creates a

I use .Net Core, and often make changes to data base through the application and the application updates the database in both staging/production. This creates a migration history and allows me to revert back to a previous database state. However, in some instances data is still lost, in that scenario I would just do a back up. This way I can almost painlessly revert back, and restore data.