I considered lightweight migration before, and also compared the main changes, but I googled and crowded and did not find a similar case where the name of the object remains unchanged, but the type of the attribute changes from int (I would have thought it would be easy to do)
It seemed to me that I was on the right path, subclassing NSEntityMigrationPolicy, then I set the custom policy field in mapmodel to this subclass (it did not autocomplete even after restarting Xcode ...)

but I see that createDestinationInstancesForSourceInstance does not receive the call

Now, since I'm dealing with a custom mapping model and policy, do I still have to output the mapping model, but with Migrate automatically disabled in persistent storage?
NSDictionary *options = @{NSMigratePersistentStoresAutomaticallyOption:@NO,
NSInferMappingModelAutomaticallyOption:@YES};
!
" ", - $source.incrementer.string:)
