When a PLC model is discontinued, the clock starts ticking. Spares become harder to find, prices rise and, eventually, a failure can stop production for days. Replacing the PLC before that happens is sensible — but a successful migration depends on checking a few things first.
1. Can you access the existing program?
This is the most important question. The program contains the machine's sequences, interlocks and years of adjustments.
- Is there an up-to-date backup?
- Is the program password-protected, and do you have the password?
- Do you have the programming software and a way to connect to the controller?
If the program exists only inside an ageing CPU, back it up now — before a failure makes recovery much harder.
2. What is the current I/O?
List every input and output: type (digital, analogue), signal range and what it connects to. Compare this with the original drawings. Undocumented changes are common on older machines and need to be found before migration, not during it.
3. Which devices communicate with the PLC?
Older PLCs often use communication protocols that newer platforms handle differently. Identify all connected devices — HMIs, drives, other PLCs, SCADA, meters — and how they communicate. Some may need gateways or replacement as part of the project.
4. Is there room in the panel?
New PLC hardware has a different footprint. Check panel space, mounting, power supply capacity and heat dissipation. Sometimes a new sub-panel or a rebuilt panel is the cleaner solution.
5. Can the field wiring be reused?
Reusing existing field wiring saves time and money. Interface adapters or careful re-termination can make this possible, but the condition of old cables and terminals should be checked.
6. How will the program be migrated?
Options include:
- Automated conversion using vendor tools, followed by review and testing
- Rewrite based on the existing logic and a functional description
- A combination — converting the core and rewriting problem areas
Whatever the approach, the new program should be tested against the original behaviour.
7. What downtime is acceptable?
Plan the migration around shutdown windows. Preparing hardware and software off-site, with a detailed cut-over plan and a fallback option, keeps downtime predictable.
8. Is now the time to improve?
A PLC migration is a good moment to add features that were missing — better diagnostics, an HMI, data logging, or SCADA integration. Weigh these against the extra scope and risk.
Pre-migration checklist
- Program backed up and accessible
- I/O list verified against site
- Connected devices and protocols listed
- Panel space and power checked
- Field wiring condition assessed
- Migration method chosen
- Downtime window and fallback planned
Need help?
Sparsh Automation offers obsolete product support for urgent sourcing and replacement, PLC programming for program migration, and complete retrofit and upgrade projects. Send us your PLC model and we will help you plan the next step.
This article provides general technical information. Always follow equipment manufacturers' instructions, applicable standards and your site's safety procedures.