A PLC migration checklist covers five stages: audit the old system, capture the logic, design the new hardware, test before the shutdown, and cut over with a tested fallback. Skipping the audit causes most overruns. Twenty checks across these stages, listed below, take a plant from an unknown legacy controller to a verified running replacement.
What you receive: send your I/O list, P&IDs or a functional description and we return a written migration proposal within one working day. Request a quotation
By Eng. Junaid Ali, KSA Industrial Automation Company. Published October 2026.
What belongs on a PLC migration checklist?
The list works on any platform, whether the old controller is a Siemens S7-300, an Allen-Bradley PLC-5 or SLC 500, or an older Modicon. Each check has an output you can file, so the project record shows what was verified and by whom.
| Stage | Checks | Output to file |
|---|---|---|
| 1. Audit | Inventory racks, modules, firmware; confirm field wiring against drawings; list networks and third-party links | Asset register, redlined drawings |
| 2. Capture | Back up programs; document logic by function; list forced bits, hidden timers and manual overrides | Verified backups, functional description |
| 3. Design | Map every I/O address; choose the platform; size memory, scan time, power and cabinet space | I/O map, hardware design |
| 4. Test | Build the new program; simulate against the old logic; factory test with the I/O list | Test sheets, deviation log |
| 5. Cut-over | Isolate, swap, re-test each loop, run the sequence, keep the fallback ready | Signed completion, as-builts |
How do you audit a legacy PLC before replacing it?
Start with what is physically in the cabinet, not what the drawings say. Drawings from the original build are often out of date after years of modifications.
- Record every module's article number, slot and firmware version.
- Trace each field wire on a sample of channels and compare with the drawing.
- List every communication link: HMI, drives, other PLCs, SCADA, gateways, printers.
- Check the backup. Open it on a clean laptop and compare the online program with the saved one.
- Note the power supply voltage and the earthing condition, because migration is a good time to correct both.
Ask operators which functions they use that the drawings never mention. Manual overrides and temporary jumpers are the usual surprises. Photograph each cabinet door-open, with terminal numbers readable, before anything is disconnected. Those photographs settle arguments later about what was where, and they help the technician who re-terminates the field wiring during the shutdown.
How do you capture the logic you cannot read?
Document by function, not by line of code. Automated converters translate instructions, but they cannot tell you why a rung exists. Write a one-page description of each machine or area: start conditions, permissives, interlocks, alarms, sequences and failure behaviour. Then review it with the operator and the maintenance lead. This document becomes the test basis later.
Do not skip the review step, because the operators know how the machine really behaves on a hot afternoon with a worn sensor, and that behaviour is what they expect from the new controller. Three items need special attention:
- Retentive memory: values that must survive a power cycle, such as counters and recipes.
- Timing: scan-time-dependent logic that behaves differently on a faster CPU.
- Hidden hardware behaviour: fast counters, high-speed inputs and analogue scaling done in module settings.
Worked example: mapping an I/O list for a pump skid
This is an example to show the method; your list will differ. A pump skid has twelve digital inputs, five digital outputs and three 4–20 mA analogue inputs. Every old address gets a new tag, a description and a test line.
| Old address | Signal | New tag | Test method |
|---|---|---|---|
| I 0.0 | Pump 1 running feedback | P101_RUN_FB | Start motor locally, confirm HMI state |
| I 0.1 | Pump 1 overload trip | P101_TRIP | Trip simulated at the starter |
| Q 4.0 | Pump 1 start command | P101_START | Force output, confirm contactor pulls in |
| IW 256 | Discharge pressure 0–10 bar | PT101_PV | Inject 4, 12, 20 mA; expect 0, 5, 10 bar |
For the pressure channel, 12 mA must read 5.0 bar on the new HMI, because (12 − 4) ÷ 16 × 10 = 5.0. A reading outside the agreed tolerance goes on the deviation log with a name and a date. Repeat this for all 20 signals, then the checklist stage 4 is complete for the skid.
Which PLC migration checklist items protect the cut-over?
Six items decide whether the shutdown finishes on time:
- A dry run of the cut-over on a test bench, with the actual program and a simulated I/O panel.
- A written step plan with times, owners and a go/no-go point.
- Spare hardware on site, including a loaded spare CPU.
- A fallback plan: how to put the old controller back in service within the same shift.
- Operator sign-off on the new screens before the shutdown, not during it.
- A drawing update schedule, so the as-built drawings are issued within days, not months.
KSA Industrial Automation Company has delivered work for Saudi Aramco, SABIC and the Royal Commission for Jubail and Yanbu. The PLC retrofit and upgrade service applies this sequence to whole control systems, and the S7-300 to S7-1500 migration page covers the Siemens route in detail. The site tests at the end are covered under control system commissioning.
Common questions about PLC migration
How long does a PLC migration take?
Most migrations take 3–8 weeks per system, with the cut-over done in planned shutdowns. Rack count, program size and the quality of existing drawings move the figure. A complete, verified I/O list is the single biggest time saver.
What does PLC migration cost?
Cost depends on the I/O count, the number of controllers, how much logic needs rewriting, the hardware chosen, the testing depth and the length of the shutdown. A proposal built on your I/O list prices each of these separately, so you can see where the money goes.
Can I migrate a PLC without stopping production?
Rarely for the final swap, because field wiring must move to the new I/O. You can do the engineering, bench testing and panel preparation while the plant runs, which keeps the shutdown to the minimum needed for wiring and checks.
Should I convert the old code automatically?
Automatic conversion saves typing but carries old structure forward, including hidden dependencies. For simple machines it is acceptable if followed by full testing. For critical processes, rewriting from the functional description gives cleaner, supportable code.
What documents should I receive at the end?
You should receive as-built drawings, the final program and a backup, the I/O map, signed test sheets, the deviation log with closures, and an operator handover note. These let the next engineer maintain the system without guessing.
Ready to turn this PLC migration checklist into a plan? Send your I/O list, P&IDs or backups and get a quotation within one working day. Email: inquiry@ksaindustrialautomation.com | Request a quotation