Identify your scenario for an eDNA to PI migration

The workflow for an eDNA to PI migration depends on your particular scenario.

Scenario 1: Pre-existing Data Archive with no incoming data

Scenario 1 workflow is for customers who have a configured Data Archive with no incoming data. First, you will use the eDNA to PI Migration Utility to generate a mapping file, review and update the mapping file if needed, and then use PI Builder and the mapping file to create new tags on the target Data Archive. Finally, you will run the eDNA to PI Migration Utility to migrate your eDNA data to the target Data Archive.

Scenario 2: Pre-existing Data Archive with incoming, live data

This scenario involves setting up a second Data Archive that acts as a temporary holding space for the migrated data. Scenario 2 applies if you can guarantee out-of-order (OOO) data or late arriving data or if you are able to ignore out-of-order or late arriving data within the course of the migration timeframe. If following this scenario, you do not need to merge archive data from the temporary server to the target server, which simplifies the post-migration process.

Scenario 3: Pre-existing Data Archive with incoming, live data and out-of-order data

Follow the Scenario 3 workflow if you have a pre-existing Data Archive that is receiving live data and you also need to preserve out-of-order events. In this scenario, you will also be required to set up a second Data Archive to act as a temporary holding space for migrated data.