There is no problem to move the files if you configure SW, as TheTick mentioned, with the new paths. Even if some SW file as some reference to a file in an path that don't exist (for example if an assembly calls an hardware part that was moved), it will search those configured paths before error.
The big problem is the inverse. If you make a copy of files to a different folder, for some reason (to make changes, design tests, ...), you must pay attention because SW allways remembers the place of the original file and this is the one that is being changed: not the copy. Example: you copy an assembly and it's components to a test folder. You open the assembly in the test folder and open in the design tree a selected component to modify. When you do this, SW opens the original file and not the copy.
You must break the connection so you don't have surprises (change the config, disconnect from network, change the original folder name so SW do not find it...).
If anyone has better ideas than these, please share them. This is a bit annoying.
Regards