Your description suggests more of copying state to another db than migration? XT is schemaless and migrations are about setting the schema correctly. If an entity doesn’t exist, puts won’t fail on XT.

What’s your use case?

My use case is ensuring transaction functions I need for my app exist, and if they don’t, add them

I know there is no harm running the same ::xt/put transaction multiple times (unless I care about the validity time I guess), but I’d like to be able to “set up” a database once with tx functions im using then use them as needed in my app

Yeah I’d do that assertion in the app startup. Not sure if any existing tools would do that.

I have done kinda similar thing with integrant which sets it up when building the connection