A production line can still be productive, reliable and profitable while its PLC is approaching the end of its service life.
That creates a difficult situation for many Canadian manufacturers. The machine itself may still have years of useful life, but the controller may be obsolete, difficult to support or no longer compatible with current software and hardware. Replacing the entire line can then create a much larger project than the original control problem.
A better starting point is to assess the control system before deciding that the machinery needs to go.
A carefully planned PLC migration can allow a manufacturer to replace an obsolete controller, preserve proven machine behaviour, retain useful equipment and prepare the control system for future automation work. Schneider Electric Canada also identifies PLC migration as a way to preserve existing investment while reducing downtime and operational disruption.
For manufacturers considering this type of project, working with an experienced PLC programming company can help turn an ageing control system into a manageable engineering project rather than an unnecessary production line replacement.
The PLC may be obsolete. The machine may not be
This distinction is often the first thing a plant should establish.
An older PLC does not automatically mean that the complete production asset has reached the end of its useful life. Motors, pumps, valves, cylinders, sensors, conveyors, mechanical assemblies and other equipment may still perform as required. The production process may also be well proven.
The problem can sit inside the control layer.
An obsolete PLC can create difficulties with spare parts, programming software, technical support, communication hardware and future expansion. A failure can become more difficult to recover from when the original controller and programming environment are no longer readily supported.
That is why PLC migration should begin with an engineering assessment rather than a decision to replace the complete production line.
Start with the condition of the existing control system
Before selecting a new PLC, document what the existing system actually does.
This sounds straightforward, but older industrial systems often contain years of modifications. Electrical drawings may not perfectly match the installed equipment. The PLC program may have been changed without the latest source file being archived. HMI screens may contain tags that no longer follow the original naming structure.
A proper assessment should look at the controller, I/O modules, power supply, communication networks, HMI, drives, field devices, electrical drawings and available software files as one control system.
The assessment should establish four things:
Area | What needs to be established |
|---|---|
PLC hardware | Controller model, CPU, I/O modules, memory and availability |
PLC program | Available source code, current program and documented changes |
Field equipment | Sensors, actuators, drives, valves, motors and other connected devices |
Documentation | Electrical drawings, I/O lists, network information and operating documentation |
This information provides the technical baseline for the migration.
PRO TIP
Do not start programming the replacement PLC before establishing what is actually running on the existing controller
A migration project becomes much safer when the engineering team knows the existing system before changing it.
Retrieve the original PLC logic before making major changes
One of the most valuable assets in an older control system can be the program already inside the PLC.
The original source file may not be available in the plant’s current engineering system. In some cases, the only reliable version of the control logic may still reside inside the PLC itself.
ControlSoft Canada has dealt with this exact type of situation.
For a National Research Council Canada project in Ottawa, ControlSoft Canada was brought in to replace an old Omron PLC CPU and upgrade the ladder logic. The project included establishing communication with the old PLC, retrieving the original ladder logic, selecting a newer Omron PLC and I/O modules, upgrading the program, reconfiguring I/O tags, updating electrical drawings, completing factory testing and I/O testing, then carrying out site commissioning and testing.
That project demonstrates an important principle:
The existing control logic can be an engineering asset, even when the PLC hardware is obsolete
Instead of treating the old machine as an unknown system, engineers can use the existing program, drawings and machine behaviour as reference points for the migration.
Build the migration around the existing machine
Once the existing system has been documented, the next task is to create a clear relationship between the old PLC and the proposed controller.
The I/O structure is particularly important.
Inputs and outputs connect the PLC to the physical process. A migration can therefore involve much more than copying program instructions from one software environment to another.
The engineering team needs to know:
- Which input controls each process function
- Which output operates each device
- Which signals are analogue
- Which signals are digital
- Which I/O points are safety related
- Which devices communicate over a network
- Which HMI tags depend on existing addresses
- Which drives or motion devices exchange data with the PLC
A detailed I/O map creates a practical bridge between the existing control system and the replacement system.
It also provides a useful document for testing and commissioning.
Preserve proven machine behaviour where it makes sense
A PLC migration is not the right time to rewrite every part of a production process simply because new software is available.
The existing sequence may represent years of production experience.
Operators may know exactly how the machine starts, stops, faults, recovers and changes between operating modes. Maintenance personnel may also understand small details that are not obvious from the PLC program alone.
That knowledge should be protected during the migration.
The new PLC program can improve structure, diagnostics and maintainability while preserving the control behaviour that the production team already relies on.
This approach reduces unnecessary changes and gives the commissioning team a clearer reference point.
Decide what should be reused and what should change
Not every component needs the same treatment.
Some equipment may remain in service. Other components may need replacement because they are obsolete, unsupported or incompatible with the new PLC platform.
A practical assessment can divide the system into three groups:
Existing component | Possible approach |
|---|---|
Reliable and supported equipment | Keep in service |
Functional but approaching obsolescence | Review for future replacement |
Obsolete or unsupported equipment | Replace as part of the migration |
This can prevent a common problem in automation projects: replacing useful equipment simply because one component has reached the end of its support life.
The goal is not to preserve every old component. The goal is to make technically sound decisions about the components that still provide value.
Plan the migration around production
The engineering work is only one part of a successful PLC migration.
Production planning matters just as much.
A manufacturer needs to know when the machine can be taken offline, which activities can be completed before the shutdown, which work must happen on site and how the commissioning team will verify the system before production resumes.
A strong project plan separates work that can happen before the production shutdown from work that requires access to the live machine.
Work that can often happen before shutdown
- PLC program development
- I/O documentation
- HMI development
- Control logic review
- Electrical drawing preparation
- Hardware preparation
- Simulation and software testing
- Test procedures
- Backup preparation
Work that normally requires the machine
- Physical installation
- Wiring changes
- I/O verification
- Device communication testing
- Motor and drive checks
- Machine sequence testing
- Safety verification
- Production commissioning
This division can reduce the amount of engineering work required during the production outage.
Schneider Electric Canada similarly highlights installation speed, software conversion and project planning as important parts of reducing disruption during PLC upgrades.
A phased migration can reduce unnecessary disruption
A large control system does not always need to change in one uncontrolled step.
A phased approach can provide more manageable checkpoints.
For example:
Phase 1: Assess the existing PLC and control system
Phase 2: Retrieve and document the existing program
Phase 3: Develop the replacement PLC application
Phase 4: Complete I/O and control system preparation
Phase 5: Test the software and hardware
Phase 6: Install and commission the new controller
Phase 7: Validate production operation
Phase 8: Document the completed system
The exact sequence depends on the machine, PLC platform, I/O architecture and production requirements.
The important point is that the migration should have defined technical checkpoints rather than becoming a single large change made during a shutdown.
Test the replacement PLC before it controls production
Commissioning should not be the first time anyone discovers that a piece of logic does not behave as expected.
Testing should start before the replacement PLC takes control of the machine.
The test plan can cover:
Test area | Purpose |
|---|---|
PLC logic | Confirm sequences and control functions |
I/O | Verify signals and device relationships |
HMI | Confirm operator controls, status and alarms |
Communications | Confirm data exchange with connected equipment |
Drives | Verify commands, status and feedback |
Fault handling | Confirm expected responses to abnormal conditions |
Production sequence | Verify the complete operating cycle |
ControlSoft Canada’s NRC Ottawa project included software FAT, I/O testing with control hardware, and site commissioning and testing. That provides a useful real world example of how testing can be built into a PLC migration rather than left until the final stage.
Do not treat the HMI as an afterthought
The PLC may be the central controller, but operators interact with the machine through the HMI.
A PLC migration can therefore affect:
- Start and stop commands
- Machine status
- Alarm messages
- Setpoints
- Production counters
- Manual controls
- Fault displays
- Operator permissions
- Process information
The HMI should be reviewed alongside the PLC program.
A migration that successfully starts the machine but leaves operators with confusing screens, missing alarms or incorrect tags is not a complete control system upgrade.
Check drives, networks and connected equipment
Modern PLC systems rarely operate alone.
The controller may communicate with variable frequency drives, remote I/O, HMIs, barcode systems, sensors, robots, SCADA platforms and other industrial devices.
That means the migration assessment needs to look beyond the PLC rack.
Industrial communication can also become a major source of unexpected commissioning problems. The replacement PLC may use a different communication architecture, addressing method or network configuration.
ControlSoft Canada lists industrial communication network design among its PLC services and supports technologies including Industrial Ethernet, Modbus, DeviceNet, ControlNet, Data Highway and other industrial communication systems.
The communication layer should therefore form part of the migration plan from the beginning.
Safety functions require their own engineering review
A PLC migration should never assume that safety related functions can simply be copied into the replacement controller without review.
Emergency stops, safety interlocks, guarding, safety relays, safety PLC functions and other protective systems need to be assessed against the applicable machine requirements and the actual installation.
The safety system should be documented separately and tested as part of commissioning.
This is one area where production pressure should never replace proper engineering verification.
Use the migration to make future maintenance easier
A legacy PLC migration creates an opportunity to improve the information available to the maintenance team.
The completed project should leave the plant with more than a new controller.
Useful handover documentation can include:
- Final PLC program
- HMI application
- I/O list
- Electrical drawings
- Network documentation
- Hardware list
- PLC configuration
- Drive configuration
- Backup files
- Alarm information
- Commissioning records
- Maintenance notes
The objective is simple.
The next engineer should be able to understand the system without starting from scratch.
The business case is larger than the PLC itself
The cost of a PLC migration should not be viewed only as the price of a new controller.
There can also be costs associated with:
- Unplanned production downtime
- Emergency engineering support
- Obsolete spare parts
- Unsupported programming software
- Difficult fault diagnosis
- Lost machine knowledge
- Production delays during future repairs
- Difficulty integrating newer automation technology
At the same time, replacing the entire production line may involve significantly larger capital expenditure and a much greater operational impact.
Statistics Canada reported in March 2026 that 47.9% of Canadian businesses had adopted new technologies during the previous three years. It also reported that 35.1% of businesses had difficulty finding candidates with the skills needed for their roles over the previous 12 months.
For manufacturers, this makes the knowledge and maintainability of industrial control systems increasingly important. A properly documented PLC migration can reduce dependence on undocumented legacy knowledge while creating a more supportable control platform.
When should a manufacturer bring in a PLC Programming Company?
A PLC migration becomes more complex when the existing system contains undocumented changes, multiple connected devices, obsolete software or a large amount of production critical logic.
Professional support becomes particularly useful when the plant needs to:
Situation | Engineering requirement |
|---|---|
Obsolete PLC hardware | Hardware assessment and migration planning |
Missing PLC source code | Program retrieval and validation |
Unknown I/O relationships | I/O mapping and field verification |
Old HMI system | HMI assessment and tag migration |
Multiple industrial networks | Communication architecture review |
Limited shutdown time | Detailed pre shutdown preparation |
Complex production sequence | Logic analysis and controlled testing |
No internal PLC specialist | External programming and commissioning support |
A PLC programming company should do more than write new ladder logic. The right engineering partner should be able to assess the existing control system, develop a migration plan, work with PLC hardware and software, support testing and commissioning, and leave the plant with usable documentation.
ControlSoft Canada states that its PLC services include evaluation of existing PLC control systems, PLC solution evaluation, hardware procurement, factory and site acceptance support, performance recommendations, PLC obsolescence migration planning, industrial communication network design and electrical and instrumentation design.
That broader capability matters because legacy PLC migration is a control system project, not simply a programming task.
A practical legacy PLC migration checklist
Before approving a migration project, the engineering and production teams should be able to answer these questions:
- Is the existing machine mechanically productive?
- What exactly is obsolete in the current control system?
- Can the existing PLC program be retrieved and validated?
- Are the electrical drawings current?
- Has every important I/O point been mapped?
- Which HMI, drive and network connections depend on the existing PLC?
- Which components can remain in service?
- What must be replaced?
- Which work can be completed before the production shutdown?
- How will the replacement system be tested?
- What documentation will be handed back to the maintenance team?
- Who will provide support after commissioning?
Clear answers to these questions can prevent expensive surprises during the migration.
What a successful PLC migration should leave behind
A successful project should produce more than a newer PLC.
The plant should have a control system that maintenance personnel can work with, engineers can support and production teams can rely on.
The finished system should have:
- A supported PLC platform
- Verified control logic
- Accurate I/O documentation
- Reliable communication with connected devices
- Functional HMI operation
- Tested alarms and fault handling
- Updated electrical documentation
- Secure program backups
- Clear commissioning records
- A defined support path
This is where the difference between replacing hardware and properly migrating a control system becomes clear.
ControlSoft Canada can help assess the migration before you replace the line
ControlSoft Canada has more than 15 years of experience in PLC programming, SCADA and industrial automation, with nearly 100 successful projects and more than 15 automation engineers. Its published services include support for existing legacy automation systems, PLC control system design and programming, control panel upgrades, system integration and SCADA solutions.
Its NRC Ottawa project also shows practical experience with an old Omron PLC where the original ladder logic was retrieved, the PLC and I/O were upgraded, I/O tags were reconfigured, drawings were updated and the new system was tested and commissioned.
That type of experience is valuable when the objective is to protect productive machinery while upgrading the control system.
Need to modernise an obsolete PLC?
Before replacing an entire production line, start with a control system assessment.
A qualified PLC programming company can review the existing PLC hardware, retrieve and assess the control logic, map the I/O, identify migration requirements and develop a practical programming and commissioning plan.
