A legacy PLC migration should be triggered by spares and software risk, not controller age: the Rockwell PLC-5 and SLC 500/1746 lines are discontinued, and Siemens formally announced the SIMATIC S7-300 and ET 200M phase-out in October 2023, with standard deliveries ending on 1 October 2025 and spares support running roughly a decade beyond [S4].
On a live plant the three viable strategies are full replacement, processor swap with retained I/O, and staged migration, while a bridge or overlay module lets the new controller sit beside the old one, read its tags, and push data to SCADA, MES, or historians without touching the running program [S4][S6].
When a Bridge or Overlay Beats a Hard Cutover
Bridge modules typically connect to the legacy controller in 2 to 4 weeks without hardware replacement, delivering immediate data visibility while a hardware migration is planned and funded [S6]. This is the practical path when the programming software only runs on one ageing laptop and only one person can recover the application, because a bridge keeps the original code untouched and recoverable until the new controller is fully proven [S4].
Overlay goes a step further: the new PLC executes in parallel, shadowing I/O and validating outputs against the legacy CPU before any handover, which is the safer pattern for safety-class interlocks where a bad first scan cannot be tolerated. For non-safety telemetry, a bridge alone is usually enough; for control logic that must be bit-exact on day one, an overlay with a side-by-side compare window is the lower-risk pattern [S3][S6].
Replace When Spares, Software, or Network Are the Constraint
Full replacement is the right call when all three of these are true: spare cards are sourced from the grey market, the programming software will not run on a supported operating system, and the legacy network (DH+, DH-485, PROFIBUS DP) blocks any modern SCADA, HMI, or IIoT integration [S4]. A full replacement also pulls the network forward, which is the natural moment to segment the control network and design secure remote access, rather than leaving OT hardening as a separate later project [S4].
Processor swap with retained I/O fits tight outage windows where the field side is healthy. For Rockwell migrations, swing-arm wiring conversion modules and pre-wired conversion cables in the 1492 conversion system land existing 1771 and 1746 field wiring directly onto 1756 ControlLogix I/O, so re-termination is the dominant variable in shutdown length, not rack replacement [S4].
Selection Criteria Mapped to the Three Options
The decision collapses to four axes: outage window, spares risk, network modernization need, and safety-class scope. A full replacement scores best on spares risk and network modernization, worst on outage window; a processor swap with retained I/O inverts that profile, which is why it dominates water and wastewater sites where zero-downtime is contractually required [S1][S4]. A bridge or overlay scores best on outage window and capital phasing, but it leaves the legacy CPU in place, so it does not solve spares risk on its own and must be paired with a planned hardware cutover [S6][S7].
For sites running Allen-Bradley PLC-5 or SLC 500, Rockwell publishes structured migration paths toward ControlLogix and CompactLogix, which sets the replacement baseline for the western North American and Australian installed base [S4]. For S5 and S7-300 sites, the clock is defined but long: spares and repair support run for roughly a decade after the October 2025 standard-deliveries cutoff, so a bridge or overlay is a defensible interim step while the full replacement is scoped and budgeted [S4].
Use Cases, Limits, and Failure Modes
Bridge and overlay modules are most common in brownfield packaging, material handling, and water or wastewater plants where the line cannot stop but the operators need real-time data; in those settings, a bridge typically exposes tag data within 2 to 4 weeks while the legacy program remains the authority on control [S1][S6]. They are a poor fit where the legacy CPU itself is the failure source, where the I/O backplane is failing, or where the field wiring is so undocumented that a translator cannot be safely mapped, because a bridge inherits every weakness of the hardware it sits beside [S5][S7].
Common failure modes during a replace strategy are well known: documentation drift, lost patches, and code that was never directly portable between vendors in the first place, so the IEC 61131 language standards give a common syntactic target but not a cross-vendor compiler, and reverse engineering the original control strategy is often part of the scope [S1][S3]. The migration ends when the last PLC-5 is decommissioned and the bridge module is removed, which is the milestone a staged project should plan backwards from [S7].
Standards, Safety, and Documentation Discipline
Modernization projects in 2026 are typically justified against updated safety standards such as NFPA 70E for electrical safety in the cabinet, and against the OEM end-of-support clock rather than against a generic "PLC age" rule, which is why a 15-year-old controller with healthy spares may be lower risk than a 10-year-old one whose software only runs on Windows 7 [S3][S4]. A bridge or overlay does not by itself close those gaps; it defers them, and the project plan should name the date the legacy CPU is removed, not leave it open-ended.
For safety-instrumented functions, a safety PLC migration needs a separate hazard analysis and proof test plan; bridging a non-safety bridge into a safety loop is not acceptable, and any overlay of safety logic must follow the same validation regime as a greenfield install, including independent proof of the new code path before the legacy path is disabled. For the broader control scope, the migration of a standard PLC program, the wiring conversion, and the network move are three coupled work packages that should be scoped, scheduled, and resourced together, since pulling one without the other is what turns a planned migration into an emergency replacement [S1][S4][S8].
Decision Rule in One Line
Pick full replacement when spares are grey-market, software is fragile, and the network blocks modern integration; pick a processor swap with retained I/O when the outage window is short and the field side is healthy; pick a bridge or overlay when the line cannot stop but needs data, modern I/O integration, or a phased budget, and write the decommission date of the legacy CPU into the project plan on day one [S4][S6][S7].
The next trackable signal is the Siemens SIMATIC S7-300 spares pricing curve after the October 2025 standard-deliveries cutoff, and the second is the Rockwell 1746 I/O grey-market lead time for sites still holding PLC-5 or SLC 500 spares, since both curves drive the bridge-versus-replace decision for sites that have not yet started scoping [S4]. Related reading: Type 2 vs Type 4 safety light curtains for guarding new cells around a migration and PV module line automation throughput when a legacy line is upgraded in place.
Detailed specification references: plc control.