Prerequisites

AVEVA PI System Connector 3 (PSC3) includes a built-in migration utility to help transition existing configurations from PI System Connector 2 (PSC2). The migration utility is available from the Migration tab in the PSC3 user interface and is accessed during connector configuration.

The migration utility automates as much of the migration process as possible while preserving previously exported AF data and PI points. By recognizing data that was already transferred by PSC2, the utility enables PSC3 to continue data transmission without creating duplicate objects, supporting a seamless upgrade experience.

Note: AVEVA recommends installing PSC3 on a new machine. If PSC3 must be installed alongside PSC2, ensure that PSC2 is completely uninstalled after installation and that no residual files remain on the system.

Before migrating, AVEVA recommends the following:

Review PI Server Tuning Parameters

Verify that the PI Server uses optimal tuning parameters. Correct tuning is required for reliable connector performance. For detailed guidance, see the AVEVA™ PI System Topologies for PI Server 2024 R2 documentation.

System Prerequisites and Compatibility

Confirm the hardware, operating system, and network meet PSC3 requirements. Ensure proper back-up strategies are in place.

For details, see System requirements.

Clearing the cache

Prior to migrating from PSC2:

1. Stop the PI System connector. See Stop or start connector data collection for additional information.

2. Wait a minimum of five minutes for the relay cache to finish processing.

If your system is production or business critical, AVEVA recommends waiting an additional fifteen minutes to reduce any risk of incomplete processing.

Proceeding before the relay cache has fully cleared may result in incomplete migration or data inconsistency. If at any time you are unsure whether processing is complete and the cache is clear, do not proceed. Contact AVEVA Customer Support for assistance.

Navigate to the Relay management section within the Data Collection Manager to select the relay and select Stop. This guarantees that no further modifications occur to any of the PSC2 files. PSC3 receives the data exactly as it was left by PSC2.

Prepare system for migration

After your cache is clear, prepare the system by collecting the required configuration files:

Create the migration folder

3. On the machine where you are installing PSC3, create a new folder titled Migration.

4. Use this folder to store the necessary configuration files from your PI System Connector 2 environment.

Copy required files

Depending on how PSC2 was configured, copy the following files into the Migration folder. Some files may not exist in all environments. If a file does not exist, it is not required.

From the PSC2 machine:

When accessing files on the PSC2 machine, verify that the machine in question is host to the same PSC2 that will be migrated.

• Datasource.config.json

  %PIHome64%Connectors\PISystem\Configuration\

• <datasource_id>_ElementGuidMap.xml.gz

  (%programdata%\OSIsoft\Tau\PISystem.ConnectorHost\PISystem Connector\PersistedFiles)

  Note: This only exists on connectors using an AF or Data Archive and AF data source. Additionally, if there are multiple ElementGuidMap files on the connector, copy and place each one into the migration folder.

• PISystemConnectorPointDefinition.xml.gz

  (%programdata%\OSIsoft\Tau\PISystem.ConnectorHost\PISystem Connector\PersistedFiles)

  Note: This only exists on connectors using an Data Archive or Data Archive and AF data source.

From the Data Collection Manager machine:

• NodeMap.config

  (%PIHome64%Data Collection Manager\DataCollectionManager\Configuration)

• DestinationSettingsExtension.config

  (%PIHome64%Data Collection Manager\DataCollectionManager\Configuration)

After completing these steps, open the PSC3 UI and select the Migration tab.