Additional SQL Server features and topics not covered by specific categories
I assumed that you changed the compatibility level from 130 to 150 when you did the upgrade. Microsoft makes changes to the optimizer in about every version of SQL Server, and you only get these changes if you change the compatibility level. These changes are meant to improve the overall performance, but the nature of a cost-based optimizer that works with estimates from statistics means that things can go wrong, and it is not unheard of plan regressions after upgrades.
I would recommend that you switch back the compat level to 130. That should remove the urgent problems. Then enable Query Store for the database. Run with this config for a week or two. Then go back to compat level 150 again. You can now use the Regressed Queries report in the Query Store folder in Object Explorer to see which queries they are. You can force the plans from compat level 130, while you work with analysing more closely why the query regressed. Often when this happens it is due to that the query has some imperfection - poor query construct, lack of a well-supporting index.
Rather than running this process as I described above, you can select the database in Object Explorer, and from the Tasks submenu select Database Upgrade at the very bottom. It will do the same process as I described, but help you with the steps.