A migration can move every file and still make content harder to find. Start by tracing how titles, assets and versions are identified across the systems that already use them.
Separate editorial and technical identity
A title or episode describes a piece of content. A master, a compliant edit and a dubbed version are assets related to it. Keep those entities distinct so you can update one without breaking links to the others.
Establish the source for each field
The catalogue might own the canonical title and episode number, while the MAM owns the technical file properties. Record that ownership and decide how downstream copies are updated. Where a field is translated, carry the language and the source with the value.
Rehearse with difficult records
Use orphan assets, duplicates, alternate cuts and multi-language versions in a pilot. Reconcile counts and relationships as well as file checksums. Any unresolved identifier should enter an exception queue with context for an operator to resolve it.