@petecorey my go-to is to use migrations only for schema migrations and have separate machinery for data migrations. More on this here (although in Ruby context, but it applies to Ecto and others too): https://dev.to/katafrakt/data-migrations-in-regular-migrations-and-why-you-probably-should-not-do-that-2eem