Cloud Manager Content Sync Enhancements

Cloud Manager’s Content Sync capability is an important tool for keeping lower environments aligned with production. However, in its current form, the process can feel unnecessarily broad in scope and operationally inefficient. I believe there are several enhancements that could make the feature significantly more effective, flexible and performant.

1. Intelligent indexing and comparison
   A valuable improvement would be the introduction of an indexing or comparison mechanism during content sync execution.
   
   At present, the process appears to operate as a full content copy. In scenarios where Production and Pre-Production both contain large volumes of content — for example, 10,000 files in each environment — it would be far more efficient to compare the target environment against the source before initiating the transfer.
   
   Such a mechanism could assess whether each file already exists in the target environment in an identical state. Where no difference is detected, the file could be excluded from the sync. In reality, this may reduce a 10,000-file sync to only the relatively small number of files that are genuinely out of date.
   
   This would reduce unnecessary data movement, improve efficiency, and likely shorten sync durations considerably.
   
   A practical way to introduce this would be as an optional setting within Content Sync, perhaps via a checkbox labelled “Enable Comparison”. If enabled, the sync would perform a comparison-driven transfer; if disabled, it would continue to run the existing full copy behaviour.
    
2. Granular and targeted synchronisation
   Another highly valuable enhancement would be the ability to perform more targeted sync operations.
   
   For example, users could be given the option to select an individual file through a “Browse” function and sync only that file to a lower environment. Similarly, users could select a folder and sync all associated child pages or assets within that structure. In addition a ‘Claim dependencies’ button would be helpful where if it is ticked it also grabs any dependencies such as assets, references or content fragments that are required for the selected page or folder and children of that folder. 
   
   This would provide much greater precision and control, allowing teams to refresh only the content they actually need rather than relying on broader synchronisation tasks.
    
3. Combined Author and Publish execution
   Finally, while the separate Author and Publish options should remain available, it would be beneficial to introduce an additional “Both” option.
   
   This would allow users to initiate a single action that executes both Author and Publish syncs sequentially, removing the need to trigger each process independently and improving the overall user experience.

Thank you for your time and consideration.