Skip to content
Discuss sourcing

FOR OVERSEAS BUYERS

PLC Migration Checklist

Updated · Written by HAM

The converted PLC program has no errors, but the machine still has HMI tags, network data and restart behaviour to verify. A successful conversion is one part of migration. Before cutover, connect every retained function to an acceptance test.

Freeze the as-built baseline before designing the target

Collect hardware, rack and slot layout, I/O, wiring, networks, addresses, HMI and SCADA links, drives, robots, vision, safety, recipes, data, external handshakes, programs, libraries, parameters, firmware, alarms, diagnostics, software, licences and backups. Compare documents with the live machine under authorised procedures. Mark discrepancies rather than silently updating one source.

Record behaviour code alone may not explain: sequences, permissives, interlocks, startup, recovery, manual modes, fault handling, timing, retained data, workarounds, quality checks and maintenance practice. Decide what must remain, what will change, and who approves each change.

Illustrative example / schematic

Migration extends beyond the converted program

What to examineExample informationWhat to establish next
ControllerI/O, retained data and startup logicCompare behaviour with the original system
Connected equipmentHMI, drives and supervisory linksTest addresses, data and alarms
CutoverWiring, available downtime and restorationPrepare stop conditions and rollback

The schematic shows the investigation boundary, not network wiring. Safety functions require their applicable design and validation process rather than an ordinary production run alone.

Convert with a discrepancy register

Map old constructs to the target and record every automatic conversion, manual rewrite, unsupported instruction, data-type or address change, timing assumption, communication change, alarm change and deliberate improvement. Link each discrepancy to an owner, resolution, test and approval. Do not bury unresolved messages inside a conversion report.

Protect scope. Mandatory migration work, as-built correction, reliability improvement and new feature are different categories. Combining them can be valid, but each needs a reason and test. The goal is controlled behaviour, not identical source text.

Mitsubishi Electric’s MELSEC-A renewal examples describe tools for reusing specified terminal blocks and wiring. Retaining existing equipment can therefore still require matching interfaces and conversion parts. These examples do not establish modification-free replacement for every model.

Mitsubishi Electric — MELSEC-A renewal examples ↗

Design rollback before cutover

Plan enough time to complete rollback within the available shutdown window. Identify the last decision point, old hardware and backups, wiring reversibility, data restoration, network changes, authority, remaining outage window, and tests after restoration. Some panel changes make full rollback impractical; state fallback stages honestly.

Define who can continue after a failed test, what defect forces rollback, which temporary workaround is prohibited, and who informs production, quality and maintenance. Log outage decisions with time, evidence, approver and consequence.

Migration workstream map

The controller sits at the centre of connected systems and accountable work.

Hardware and I/O

physical path

Power, racks, modules, wiring, panels, terminals, field devices and spares

Logic and motion

machine behaviour

Programs, timing, sequences, parameters, drives and robots

Networks and data

information flow

Networks, HMI, SCADA, historians, MES, remote access and time

Safety and compliance

independent acceptance

Risk assessment, safety functions, validation and change approval

Cutover and operations

controlled transition

Test, outage, rollback, production trial, training and support

Accepted control systemRequired behaviour demonstrated with traceable evidence
Readiness means dependencies are owned, not that teams completed isolated checklists.

Close with operational evidence

Archive released programs, parameters, configuration, firmware, drawings, network records, tests, deviations, safety validation, licences, recovery media and history in the controlled repository. Confirm maintenance can connect, diagnose, back up and restore. Define early-life support and defect ownership after production resumes.

Share the approved component list and migration schedule with HAM. We can help look for Japanese suppliers for the specified items. Confirm the conversion, testing, rollback and site acceptance arrangements with your controls engineer before the changeover.

Frequently asked questions
Can this checklist replace an engineering plan?
No. It exposes workstreams and evidence. Design, risk assessment, test cases, procedures and acceptance must be specific to the machine and site.
Should new features be included?
Only when separately scoped, owned and tested. Mixing features into mandatory conversion increases diagnosis and rollback difficulty.
What makes rollback credible?
A decision time, retained hardware and backups, reversible interfaces or fallback, authorised people, sufficient window, and a tested restoration procedure.

Sources and further reading

CONTACT

Contact us

Please contact us with questions about any of our businesses, or about collaboration and media.