There's definitely a language/paradigm switching cost if you jump back and forth too much. What I found helpful was to prototype all the migrations and queries

There's definitely a language/paradigm switching cost if you jump back and forth too much. What I found helpful was to prototype all the migrations and queries (of whatever feature or user flow you're building) in a .sql file first with mocked values. You'll be surprised by how much you can do if you're simply forced to write pure sql. Once you've reached the limit of what you can do you can move the queries back into your app to wire the rest up. This is usually not much work if you use raw queries instead of ORMs. You usually end up writing a lot more efficient apps this way!