Name each external dependency
Open the intended project revision and list every local media or image source needed for the presentation. Record its current path, purpose and the first scene where it appears. Include the original file itself in the transfer plan rather than relying on a preview image as evidence of portability.
Move a small complete scene first
OBS documents source properties that select local files, while Scene Collections preserve the composition. A useful transfer experiment therefore includes one collection and all files used by one small scene. Place them in deliberate destination folders and update the relevant source paths through the installed application.
Use a distinctive owned title card and a short clip. Their identity should be obvious, so an old cached-looking image or similarly named revision is less likely to be mistaken for the intended material.
Prove the destination sequence
Open the destination scene, inspect the title card and play the clip through its ending. Record which dependencies needed relocation. Repeat the method for remaining scenes only after the first complete example works as intended.
Keep source originals until the presentation and saved output have been checked. The inventory is an authored transfer aid; no files were moved, embedded or recovered for this article.
Questions answered
Is a visible source name proof that its file moved?
No. Inspect the path and actual content on the destination.
Should the relocation list include unused old media?
Focus on required presentation dependencies, and label any separately archived material clearly.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.