How do you calculate protocol conversion cost?

Multiply the number of legacy devices by the per-device conversion cost and by your clean-conversion rate, then add the fixed engineering adder. With 60 devices at $600 each at an 80% clean rate plus an $18,000 program adder, the variable cost is $28,800 and the total is $46,800.

Why include a clean-conversion rate instead of just device count?

Not every legacy device maps cleanly to the new protocol. Some have undocumented register maps, odd baud rates, or proprietary framing. The clean-conversion rate scales the variable cost to reflect that only a portion convert without extra driver work, giving a more defensible budget.

What is a good clean-conversion rate for a brownfield IIoT project?

Well-documented Modbus or EtherNet/IP fleets often hit 85 to 95 percent. Mixed-vintage serial and proprietary devices can fall to 60 to 75 percent. The 80 percent default sits in the middle for a typical mixed plant.

What does the fixed engineering adder cover?

It captures program-level work that does not scale per device: gateway architecture, OPC UA or Sparkplug namespace design, security hardening, factory acceptance testing, and documentation. In the example it is $18,000 and is the dominant fixed cost on a 60-device job.

Gateway conversion vs full device replacement, which is cheaper?

Conversion via gateways is almost always cheaper per device than replacing field instruments, but it adds a translation layer to maintain. Use this calculator's per-device figure (here $780 effective) against the installed cost of a new native-protocol device to decide.

Why is the effective cost per device higher than the input price?

The headline per-device figure of $780 includes a share of the fixed engineering adder spread across all 60 devices, so it exceeds the $600 raw conversion price. That fully loaded number is what you should quote internally.

IIoT, SCADA & Edge Connectivity calculator

Protocol Conversion Cost Calculator

Protocol conversion cost is the all-in spend to move legacy plant devices off Modbus RTU, DeviceNet, Profibus, or proprietary serial links onto a modern protocol like OPC UA, MQTT Sparkplug, or EtherNet/IP. Controls engineers and IIoT project leads use it to scope brownfield connectivity projects, justify gateway hardware versus full device replacement, and set a realistic line item in a SCADA or edge-modernization budget. It matters because the catalog price of a protocol gateway is the cheap part; engineering, tag mapping, commissioning, and the devices that do not convert cleanly drive the real number. Modeling a clean-conversion rate up front keeps the estimate honest about rework.

What this calculator does

Estimate the loaded cost of legacy protocol conversion (Modbus, DNP3, BACnet, serial) to OPC UA or MQTT from the count of devices to convert, conversion cost per device (gateway hardware plus engineering), the share that converts cleanly without driver custom work, and a fixed program engineering adder.
Use it when an OT integrator is sizing a brownfield protocol conversion project to bring legacy serial or Modbus devices onto OPC UA or MQTT for an MES or unified namespace.
It computes total protocol conversion cost by applying a clean-conversion success rate to per-device cost, then adding a fixed engineering program charge.

Formula used

Variable protocol conversion cost = devices × cost per device × clean-conversion rate
Total protocol conversion cost = variable cost + fixed program engineering adder

Inputs explained

Legacy devices to convert:
Conversion cost per device:
Clean-conversion rate:
Fixed program engineering adder:

How to use the result

Use it when scoping a brownfield IIoT or SCADA connectivity upgrade where legacy field devices must be bridged to a new protocol.
The clean-conversion rate is a planning estimate; devices that fail to convert may need protocol-specific drivers, custom gateways, or outright replacement that a single rate cannot fully capture.

Current U.S. benchmarks

Global copper trades at $13,484 per tonne (IMF via FRED, May 2026), up 41.5% in a year, and U.S. industrial electricity averages 8.66 cents per kWh. Both feed electrified-hardware unit economics.

Common questions

How do you calculate protocol conversion cost? Multiply the number of legacy devices by the per-device conversion cost and by your clean-conversion rate, then add the fixed engineering adder. With 60 devices at $600 each at an 80% clean rate plus an $18,000 program adder, the variable cost is $28,800 and the total is $46,800.
Why include a clean-conversion rate instead of just device count? Not every legacy device maps cleanly to the new protocol. Some have undocumented register maps, odd baud rates, or proprietary framing. The clean-conversion rate scales the variable cost to reflect that only a portion convert without extra driver work, giving a more defensible budget.
What is a good clean-conversion rate for a brownfield IIoT project? Well-documented Modbus or EtherNet/IP fleets often hit 85 to 95 percent. Mixed-vintage serial and proprietary devices can fall to 60 to 75 percent. The 80 percent default sits in the middle for a typical mixed plant.
What does the fixed engineering adder cover? It captures program-level work that does not scale per device: gateway architecture, OPC UA or Sparkplug namespace design, security hardening, factory acceptance testing, and documentation. In the example it is $18,000 and is the dominant fixed cost on a 60-device job.
Gateway conversion vs full device replacement, which is cheaper? Conversion via gateways is almost always cheaper per device than replacing field instruments, but it adds a translation layer to maintain. Use this calculator's per-device figure (here $780 effective) against the installed cost of a new native-protocol device to decide.

Last reviewed 2026-05-12.