Skip Newer Files During Synchronization

Syncrify will synchronize files by default if the file size or the last modified date (LMD) differs between the source and destination. However, consider the following scenario when you would not want to perform synchronization based on the LMD of the file.

  • You transfer files from a source computer (Syncrify Client) to a destination (Syncrify Server).
  • Once these files come to their destination, you run a program to perform some business logic that changes the data within the file. This will change the LMD of the file on the destination to a newer value.
  • Since the file on the destination is newer, you do not want to run another synchronization that would typically replace it again with the version on the source machine.
  • There is where the Skip newer files option comes in handy.

An Example

  • You create a file on the source called DataOne.csv on the source. The LMD for this file is Jan 01 at 10:00 AM.
  • A synchronization job with direction client-to-server is run around 11:00 AM. This copies the source file to the destination machine with the same LMD.
  • You run a program at 1:00 PM that modifies this file. Now the LMD of this file on the destination is 1:00 PM.
  • You run another synchronization job on Jan 02 at 11:00 AM. The LMD of DataOne.csv on the source machine is 10:00 AM and 11:00 AM on the destination.
  • If this option is checked, Syncrify will not transfer the file again since a newer file exists on the destination.


The value for Direction play an important role when this setting is enabled.

  • Client-to-Server - Files are skipped if the LMD is newer on Syncrify Server
  • Server-to-Client - Files are skipped if the LMD is newer on Syncrify Client
  • Two-way-sync - This setting is ignored

How To Enable

  • Start Syncrify Client
  • Click Additional Options
  • Chck Skip newer files


Social Media

Powered by