I've written many answers on the Property Transfer (PT) service here on AKS, try searching for them.
PT can move data in any direction between any two OPC items in the address space of a system.
PT is often incorrectly put in focus when it comes to performance. The PT service can not perform better than the destination OPC server's ability to accept asynchronous writes.
Imaging filling up your lawn mower from a petrol can - unless you keep the rate of flow at or below the capacity of the funnel, you will spill. The spill is not the funnel's nor the lawn mower's fault, it is the person holding the petrol can.
As a system's engineer, you need to find out the maximum capacity of your destination OPC server and keep the pace of writes at or below.
A failed write may be retried at the cost of more writes
A cyclic scheduled write (write even if no change) will also add volume of writes.
The maximum capacity is difficult to gauge.
Work with the available settings (Update Rate, Retry Failed, Cyclic Rewrite and Min Time Between Writes) until you see no "Transaction overrun". Remember to test all running conditions (startup, shutdown, failover, etc). The last settings mentioned was added late in the 5.1 era.