Best approach for migrating culture-agnostic media from KX13 to Content Hub in XbyK

Has anyone dealt with culture handling for media items in Content Hub when migrating from Kentico Xperience 13 to Xperience by Kentico?

We have a client with a large media library in KX13 that is currently used across all 8 language versions of their site. In KX13, media library files are culture-agnostic, so the same media asset can be used in any language.

As part of planning the migration to Xperience by Kentico, we are analyzing how this media library should be migrated. Since media assets are now stored in Content Hub and must have a culture assigned, we are considering a couple of possible approaches:

1. Use a single culture for all media items and rely on language fallback, though this approach does not allow for localized metadata such as alternative text.
2. Duplicate all media items for every culture in the system, possibly using a global event or custom migration logic. This has a drawback that every file is duplicated 8 times, consumes 8 times the storage, and can potentially break.

Has anyone encountered this scenario before? I would greatly appreciate hearing about the approach you took, how you addressed it, and any drawbacks or issues we should be aware of.

Thanks in advance for any insights.

Environment

• Xperience by Kentico version: [31.4.1]