06/17/2026
If you're an OPC Data Logger user, you've probably seen the announcement that OPC Data Logger has reached end-of-life and are starting to evaluate your migration options.
One of the most common questions we hear is:
"How do the concepts I know from OPC Data Logger translate into OPC Router?"
While OPC Router is the recommended migration path, it's more than a direct replacement. It takes the familiar concepts of OPC data logging and expands them into a complete industrial integration platform.
Some examples:
🔹 Logging Task → Connections
🔹 Scheduled Logging → Time Triggers
🔹 Log on Value Change → OPC Data Change Trigger
🔹 Monitored Item → OPC Data Access Tags
🔹 Database/File Logging → Destination Transfer Objects
One of the biggest differences is OPC Router's visual workflow and trigger architecture. Instead of simply deciding when data gets logged, triggers can initiate complete workflows that connect OPC data to databases, MQTT, REST APIs, ERP systems, cloud platforms, and more.
To help existing users make the transition, we've put together a guide that maps familiar OPC Data Logger features and terminology to their OPC Router equivalents.
If you're planning a migration, this guide can help shorten the learning curve and highlight opportunities to go beyond traditional data logging.
Understand how OPC Data Logger components—including logging tasks, monitored items, triggers, and data storage—map to OPC Router's architecture.
