Once your storage is connected, ioMoVo can move and copy content between locations without you going through each system separately. This is the single most common thing teams ask about, so it is worth understanding what happens underneath.
Where you can move content
Any storage you have connected can act as a source or a destination. That covers cloud object storage, the content platforms your team already works in, drop locations reached over SFTP or FTP, and NAS shares on your own network.
The full list is in Bring your own storage. The important point is that once two systems are connected, moving content between them is one operation in ioMoVo rather than a download from one and an upload to the other.
Move or copy
A move relocates the content and the original location no longer holds it. A copy leaves the source intact and creates a duplicate at the destination.
Copies drift. The moment you have two, they start diverging, and six months later nobody knows which one is current. Copy when you have a specific reason, not as a default.
Working in bulk
You can select multiple files and folders and act on them together rather than one at a time. For anything beyond a handful of items this is worth the extra few seconds of selecting properly.
Large transfers take real time. Kicking off a multi terabyte move and then wondering why it has not finished is a common and avoidable frustration.
Three things worth checking first
Egress charges. Some providers bill for data leaving a region or leaving their network. Moving a large library across providers can carry a bill you did not expect. Check before, not after
Destination permissions. ioMoVo needs write access to where you are sending content. A move that fails halfway is more annoying than one that never starts
What else points at the source. If another system or a set of links expects content at the old path, moving it will break them
What happens to enrichment
Metadata and enrichment stay attached to the asset in ioMoVo, so moving content between storage locations does not mean starting again with indexing.
Related
Moving, copying, or connecting covers when you should do this at all. Bring your own storage lists every supported back end.