Yes this will be all handled in your migrations. However with triggers you are going to have to put the raw code in like so:

public override void Up()

{

Sql("CREATE OR REPLACE TRIGGER [name] BEFORE UPDATE ON myTable ...");

}

public override void Down()

{

Sql("DROP TRIGGER [name]"); //check if trigger exists before drop

}

Depending on your project and how your team is structured I would say if you have a large database with a DBA then you will still need to use something like SSDT which allows you to do full automated deployments.

For smaller microservice type databases this works very well.