Copilot has replaced almost all of the annoying tedious stuff, especially stuff like writing (simple) SQL queries.
“Parse this json and put the fields into the database where they belong” is a fantastic use case for copilot writing SQL.
(Yes I’m sure there’s an ORM plugin or some middleware I could write, but in an MVP, or a mock-up, that’s too much pre optimization)
ORM is more for future, because it abstracts away the database implementation, so you could in theory change the db or change some behaviour more simply.
E.g. if you add something like deleted_at column, ORM can have a single place where to configure system to use it, but if you have SQL queries lying around you may need to find all spots to add that to your where clauses everywhere.
But otherwise SQL is easier to work with in my view.
It's just a question of whether you want to use a toolkit to help the transformations, or if you want to 'do it by hand'.