@claudius I quite like the idea that each database object (be it a collection or a single object) has its own migration code encapsulated within it. So if from version 2 to 3 only Collection X and Object Y have changed, they can lazily carry out their migrations the first time they’re accessed.
Just had a quick look at JSDB to remind myself how I’m doing things and it should work by having the Proxy methods carry out the migration check.
Going to spike it and see how/if it works :)