A 'normal' profile should be re-scanning the (new) Destination each run, and if your Move was successful, find the same files there it would have found if no move / no re-config. It should thus only propose actions to remedy any differences found, as usual.
The caveats to watch for are if you are using a profile that stores what was where on one or both sides:
- if you are using Fast Backup and not performing a Rescan (thus, the profile is not actually scanning the new Destination (yet)) and you cancel the profile's prompt whether you should also Force Rescan when you edit the Destination. If so, this would means it will think the contents of the Destination are the same as before without checking. This is fine if that is actually the case (if you Moved all the files, and didn't change any). But if you missed or changed any, the profile won't notice unless/until you Rescan.
- something similar can occur if you are using SmartSync (where the profile has a History of what was where last time on each side). If you miss a file, and next run the profile scans the new Right and spots that, it will think it was deleted by a user and replicate that to Left - that is, delete the Left copy. (Or vice versa, whichever orientation applies). The profile will prompt if you want to clear History if you edit the Destination/Right string, and this is why. (And ditto if you change Source/Left string)
The caveats to watch for are if you are using a profile that stores what was where on one or both sides:
- if you are using Fast Backup and not performing a Rescan (thus, the profile is not actually scanning the new Destination (yet)) and you cancel the profile's prompt whether you should also Force Rescan when you edit the Destination. If so, this would means it will think the contents of the Destination are the same as before without checking. This is fine if that is actually the case (if you Moved all the files, and didn't change any). But if you missed or changed any, the profile won't notice unless/until you Rescan.
- something similar can occur if you are using SmartSync (where the profile has a History of what was where last time on each side). If you miss a file, and next run the profile scans the new Right and spots that, it will think it was deleted by a user and replicate that to Left - that is, delete the Left copy. (Or vice versa, whichever orientation applies). The profile will prompt if you want to clear History if you edit the Destination/Right string, and this is why. (And ditto if you change Source/Left string)