PI and old Wonderware Historian?

AVEVA continues to actively develop and support both AVEVA Historian (formerly branded as "Wonderware Historian") and AVEVA PI. AVEVA Historian is better suited as a supervisory historian that is closely aligned with HMI/SCADA applications since it includes integrated alarm/event history and is well-integrated with AVEVA's HMI/SCADA solutions. AVEVA PI is better suited as an enterprise platform, especially because of the ability that Asset Framework and Asset Analytics give to normalize and contextualize time-series data. 

Starting in Historian 2012 we've had the ability to "replicate" data from one Historian to another to give a consolidated view from across multiple source systems. Over time, we've expanded that to also support replicating to AVEVA Insight and, in the Historian 2023 release, the option to replicate to AVEVA Data Hub and to AVEVA PI.

AVEVA continues to actively develop and support both AVEVA Historian (formerly branded as "Wonderware Historian") and AVEVA PI. AVEVA Historian is better suited as a supervisory historian that is closely aligned with HMI/SCADA applications since it includes integrated alarm/event history and is well-integrated with AVEVA's HMI/SCADA solutions. AVEVA PI is better suited as an enterprise platform, especially because of the ability that Asset Framework and Asset Analytics give to normalize and contextualize time-series data. 

Starting in Historian 2012 we've had the ability to "replicate" data from one Historian to another to give a consolidated view from across multiple source systems. Over time, we've expanded that to also support replicating to AVEVA Insight and, in the Historian 2023 release, the option to replicate to AVEVA Data Hub and to AVEVA PI.

Does the version of Aveva Historian and Aveva PI have to be 1 to 1 or same versions for replication?  Any notes on replicating to PI?  My memory is vague but Aveva Historian replication worked sometimes from older to new Wonderware Historians(not vice versa) but was always recom to be the same rev.

- Found it - MOST AWESOME:

You're correct that for replicating to another AVEVA Historian, the destination system has to be the same or a newer version. However, AVEVA Historian and AVEVA PI have different release cycles and version designations, so they don't have to match. There is a minimum version requirement for the PI Web API to be v1.16.0 or later (no direct requirement for the PI Archive version).