Right now the only way I see this possible is, Deploy as not required, run a migration, deploy again as required, hoping that no new rows are created in the meantime, there is no way this is the actual way to manage this, if it is, this is a large enough flaw to leave prisma and move to Hasura