SwiftData Migration: Why no explicit ETL?

When I used to do Migrations, I always used ETL and then push to a dev system to review/test before going production.

The migration support is SwiftData is fine for a little tweak.

I might as well just just use new schema and context and write the custom code than use the SwiftData migration support.

SwiftData Migration: Why no explicit ETL?
 
 
Q