Duplicate files - how to preserve folder structure when moving them?

Hi.
I know I've had a similar conversation before, but I can't figure this out.

When searching for duplicate files (which Dopus is good at), I want to move them to a backup location, not delete them.
But often the duplicate files are found in subfolders, and I want to keep that folder structure when moving the files.
But how?
I know I can flatten the duplicate file collection view by setting grouping to None, and then select the files I want to move more easily, but when I try to move or copy those files, the folder structure is not presevered.

Any tips is much appreciated!

Thanks.

Create a button which runs this:

Copy MOVE {filepath$} CREATEFOLDER {filepath$|..|subdir}

It will move the selected folders in the source side into the destination folder, creating subdirectories which mirror their full paths.

Details about "subdir" here. See also "noroot".

1 Like

This did the trick
Thank you very much

Is it possible to cut some path segments from the left besides the drive letter with noroot?
For example, I want to move all .exe files from

  • D:\MainBackup\App\... (a bunch of subfolders with exe files)
  • D:\Alt2Backup\App\

while preserving their paths
The trick mentioned above allows me to move everything under
D:\AltBackup\App\Backup\App\... without the extra D;\
But I'd also like to avoid the extra step of then having to move everything two levels up. There is currently a way to move up the tree, but is there a way to move down the tree?

Could be done with scripting but i don't think there is a more simple thing like "subdir" for it.

Maybe we could add a "sourcerel" or something which made paths relative to the source path.

Think this could work, though would this work for collections?
Because in the workflow mentioned above I use an *.exe search to create a collection of all exe files and then the source path is he path of the last tab that I was in before such a collection was created, not the virtual source path of the collection itself

Collections would complicate things, and might not always have a common root.

With your example, I would probably use a script that looks at the source path of each selected item and replaces D:\MainBackup\ with D:\Alt2Backup\ to get the path to copy it to.