As stated, use (create) a SmartSync profile (there's an option to do exactly that in the New Profile wizard, for example). Remember it has to have run at least once before it can try to detect Moves or Renames, though you can switch the optional settings to do so 'on' straight away (on the enhanced version of the Decisions-Files page that a SmartSync profile uses). If it doesn't have a state History yet, it simply won't try (yet).
As per the contextual Help on that enhanced Decisions-Files page (press F1), if it finds potential candidates, it will then hash them (provided your devices/services support hashing) to make sure they are the exact-same file. If hashing fails (for example, the file has been moved and edited...) or is not possible at all, it will fall back to delete-and-recopy. Remember that hashing takes time, so it may be slow...sometimes as slow or slower than delete-and-recopy might have been (generally depending on the devices/services)
As per the contextual Help on that enhanced Decisions-Files page (press F1), if it finds potential candidates, it will then hash them (provided your devices/services support hashing) to make sure they are the exact-same file. If hashing fails (for example, the file has been moved and edited...) or is not possible at all, it will fall back to delete-and-recopy. Remember that hashing takes time, so it may be slow...sometimes as slow or slower than delete-and-recopy might have been (generally depending on the devices/services)