Data migration - migrate Canto assets that have already been added to Craft with the existing codebase to the new approach's schema

[ericdrosas87]

No description provided.

[ericdrosas87]

One thing I wanted to mention is that @blnkt reminded me that we only have 51 assets from Canto currently added to entries, so we should weigh the trade-off of having our content creators re-add the assets manually with the new version of the field versus auto DB migration.

[khalwat]

Well, that's an answer I can't answer for you -- but yeah it's possible it might be easier to just have them do it.

So the tradeoff is a one-time migration and the engineering / testing effort vs. them doing it manually.

[ericdrosas87]

Can you estimate based on doing this programmatically and Blake and I can assess manual/programmatic migration on our side?

[blnkt]

I think this is not worth; not worth estimating. There is no doubt in my mind: it will be easier to just have them do it manually than engineer, test, and run some migration.

[khalwat]

Writing the code to do it won't be horrible, but to test it anywhere other than a vacuum, I'd need to get a copy of the production db & composer.json so I can spin it up locally to test against your actual data.

Estimate: 4 hours