Need
help?Call 1-833-423-3367We answer
Legacy PLC Upgrades and Migrations
Retire the PLC-5 before it retires your line, on a schedule production can live with.
The clock is running on your PLC-5
Rockwell stopped making the PLC-5 years ago. The SLC 500 and MicroLogix families are following the same path, along with controllers of the same generation from other vendors. The hardware still runs, which is exactly the problem. Nothing forces the issue until a processor faults on a Tuesday night and the only replacement is an untested unit from a broker three time zones away.
Age brings specific failure modes. Electrolytic capacitors dry out. Backup batteries die and take the program with them. Communication cards for DH+ and Remote I/O fail with no new stock behind them. And the person who last touched that ladder logic may have retired too.
A migration is not an upgrade project. It is risk removal. The only real question is whether you schedule it, or your oldest processor schedules it for you.
Migration planning that protects production
A migration succeeds or fails in the planning. Before anyone touches a panel, we document what exists: every rack, every I/O point, every DH+ node, every message instruction buried in the ladder.
- I/O mapping. Each 1771 or 1746 point is mapped to its new module and address before cutover, so wiring conflicts show up on paper instead of on the plant floor.
- Code conversion. Conversion tools translate PLC-5 and SLC ladder into Logix, but they do not do it cleanly. Timers, integer files and messaging all need engineering review. We convert, review, and test against simulated I/O before the old processor ever comes out.
- Cutover scheduling. The switchover is planned around your production calendar. Weekend windows, seasonal shutdowns, one line at a time. You pick the window. We build the plan to fit it.
Panels, wiring and code under one roof
Most migrations involve three vendors: an integrator for the code, a panel builder, and an electrical contractor. That means three schedules, three contracts, and three places for scope to fall through the cracks.
Bedford runs it as one job. Our engineers plan the migration and convert the code. The in-house panel shop builds the new panels or backplane retrofits and tests them before they ship. Red Seal industrial electricians handle demolition, wiring and termination during the outage. The same people who mapped the I/O land the wires, so nothing is lost between the drawing and the panel.
The company is engineering led, with a B.Eng on staff, and one team owns design, panels, code, install and support. When a question surfaces at 2 a.m. during cutover, there is no vendor triangle. One call, one team, one answer.
Phased or single outage, always with rollback
There are two honest ways to cut over, and the right one depends on your process.
Phased cutover. The system moves one section at a time. A gateway bridges the old network to the new one, so ControlLogix and PLC-5 run side by side while racks migrate over successive weekends. Downtime per window is small. Total calendar time is longer, and the temporary bridge adds its own complexity.
Single-outage cutover. Everything switches in one planned shutdown. Panels are prebuilt and tested in the shop, conversion wiring is staged, and the outage is choreographed hour by hour. Total disruption is shorter, but the window has to hold.
Either way, every cutover plan includes a rollback. The old processor stays installed and intact, with a decision point defined in advance. If the new system does not prove out by the deadline, the old one goes back online and production runs while we regroup.
Support after the switch flips
The migration is not done when the line restarts. The first weeks on a new platform generate questions, and unfamiliar hardware makes maintenance teams hesitant. We plan for that.
- Documentation. Updated drawings, I/O lists, network diagrams and a commented program that reflects what actually runs, not what ran in 1998.
- Training. Hands-on sessions for your electricians and operators: navigating the new software, forcing I/O safely, pulling diagnostics from the processor, swapping a module.
- Support. The engineers who wrote the code answer the phone afterward, and the emergency line, 1-833-423-3367, is there for the kind of question that shows up on night shift two weeks after cutover.
We program five platforms, Allen-Bradley, Schneider, Omron, Phoenix Contact and Unitronics, so support does not depend on which direction your migration went.
Built for the Maritimes plants
Legacy controllers are everywhere in this region. Seafood processors running lines that were automated once, decades ago, and never touched again. Sawmills and forestry operations with controls that outlived two owners. Manufacturers in industrial parks from Moncton to Halifax carrying a mix of platforms nobody fully documented.
Distance makes obsolescence worse here. When a plant outside Truro or Amherst loses a processor, a specialist flying in from Ontario adds a day before diagnosis even starts. Bedford is based in Dieppe, NB and works across Halifax, Truro, Amherst, Moncton, Saint John and Charlottetown. Getting to you is a drive, not a flight.
A migration assessment starts with an inventory. We list every controller on your floor with its support status and sort the results into three columns: what is fine, what needs a spares plan, and what needs a migration path. What you do with that picture is up to you.
Score your obsolescence risk
Five questions. Honest answers. See how exposed your plant is.
Common questions
More from Programming
Get a migration assessment
Tell us what is running on your floor, get a straight read on what can wait and what cannot, and decide from there.