You can only set a SmartSync profile to detect moved files, because only a SmartSync profile (after run-1) has the requisite state-databases on each side to try and figure out potential move-candidates. The process also requires hashing the files (using XCRC on an FTP server), which your server may not support (very many FTP servers do not). This hashing (content-comparison) is to try to ensure the two files' contents are exactly the same between the new location on Left/Source and the old location on Right/Destination. (It therefore follows that it absolutely will not work for files that have been moved and also edited, because their contents obviously will be different, so this check will fail)
Note that SmartSync relies on the FTP server storing the attributes of the files so that they match the corresponding local files exactly. Many do not. Check out our Knowledge Base (also, the Help, and this forum) on potential problems with FTP.
Note that SmartSync relies on the FTP server storing the attributes of the files so that they match the corresponding local files exactly. Many do not. Check out our Knowledge Base (also, the Help, and this forum) on potential problems with FTP.