Files moved incorrectly or appear missing

#Files aren't at the destination

• Read the run detail in Logs — it lists exactly which files transferred. A success with 0 files usually means the source had nothing new.
• Conflict set to Skip quietly leaves existing same-named files in place — look for a partial-success run and review what was skipped (see conflict handling).
• Right path? Confirm you're looking where the job writes (UNC vs. mapped drive, prefix vs. bucket root).

#Sync/Mirror removed files

This is expected behavior: Sync/Mirror makes the destination match the source, which includes removing destination files that no longer exist in the source. If that surprised you, the mode — or the source/destination direction — was wrong.

• Restore the removed files from Archive (if enabled) or your backup.
• Switch the job to Copy (never deletes at the destination) or Move, as appropriate.
• When in doubt, run in Copy against a scratch destination and compare first. See Sync/Mirror.

#Move emptied the source

Move removes files from the source after copying them — that's by design. If you needed them to stay, use Copy instead, and enable Archive on Move jobs so a recoverable copy is always kept.