The job/task is configured to move new files only ("Collect Only New Files" is checked/enabled). However, there are files that are moving multiple times and the timestamp is changing on the destination server. The time stamp on the Amazon S3 source remains the same, so it should not be getting transferred again.

Windows folder paths are case-insensitive, but Linux paths are case-sensitive.

In the source host (Amazon S3 or Linux server), there is more than one folder with the same name and differences in casing (for example, one folder is called "Folder A" and another is called "FOLDER A"). Even though there are two folders with different casing, MOVEit Automation does not treat them as separate folders for the timestamp used in the "Collect Only New Files" feature. It refers to a single path and timestamp entry for both paths. This can cause unexpected behavior like files being transferred multiple times.

Until the fix is available, use the workaround below.

1. In the source (Amazon S3 or some Linux host), rename one of the duplicate folders. For the example of "Folder A" and "FOLDER A", the first folder could be renamed to "Folder A_1". To prevent the files in that folder from being migrated again, follow the rest of the steps.
2. Log into the Web Admin and open the task.
3. On the source line, click the ... icon > Edit Source Timestamps.
4. Click Add Timestamp, then populate the fields:
   1. Paste in the full path for the newly renamed folder
   2. Enter the appropriate file mask (if the task looks for all files in the folder, enter *.*)
   3. Enter the timestamp (ex. 2025-03-03 00:00:00)
5. It should look something like this:
   1. 

References to Other Documentation:

Editing Source Timestamps - https://docs.progress.com/bundle/moveit-automation-web-admin-help-2024/page/Editing-Source-Timestamps_2.html

Progress Article(s):

Old files are transferred when the collect only new files option is selected