There are three ways content becomes usable in ioMoVo, and picking the right one at the start saves a lot of rework. The question is not really "how do I upload this", it is "where should this actually live".
Connect it
Your content stays exactly where it is, in your own storage, and ioMoVo indexes it in place through ioHub. Nothing is duplicated and nothing moves.
This is usually the right answer for large existing libraries, for content that other systems are already writing to, and for anything subject to residency rules that make a second copy awkward to justify. It is also the fastest way to see value, because there is no migration to wait for.
Copy it
A duplicate is created in ioCloud while the original stays put. You now have two copies and they will drift apart over time.
Copying makes sense when you want a curated working set separate from a messy source, or when the source is somewhere slow or unreliable. Be deliberate about it, because copies are where version confusion starts.
Move it
The content is relocated and the original location no longer holds it. Use this when you are genuinely consolidating and you want one authoritative place.
Questions that decide it
Is anything else writing to this location? If yes, connect rather than copy, or the two will diverge
Does a second copy create a compliance problem? For regulated content, connecting avoids a conversation you would otherwise have to have
How big is it? Copying terabytes has a real time and cost, and connecting has neither
Who needs the original path to keep working? Moving breaks anything pointing at the old location
The common mistake
Teams often assume they have to copy everything into ioMoVo before they can search it. They do not, and starting with a migration is the slowest possible way to begin. Connect your existing storage first, work with it for a few weeks, and let the copying decisions come from what you actually learn.
Related
Bring your own storage covers which back ends can be connected. Moving and copying content between connected storage covers the mechanics.