OMRON PLC Migration in Thailand: A Practical CJ2-to-NX Guide

An OMRON PLC migration is rarely just a CPU replacement. I/O, communications, HMI screens, safety interfaces, drives, recipes, data collection, and maintenance practices can all change. For a Thai factory with a short shutdown window, the project must combine an installed-base audit, gap analysis, offline testing, FAT/SAT, and a workable rollback plan. This guide helps production engineering, maintenance, quality, and purchasing teams specify and accept a migration from CJ/CS/CP platforms to NX/NJ or another supported architecture.

Treat an OMRON PLC update as a production-risk project

The objective is not to make a new controller run. It is to maintain production, quality, safety, traceability, and recoverability while reducing dependence on aging assets. A CPU model alone does not reveal migration complexity. Racks, I/O modules, special units, networks, HMI applications, motion, inverters, safety circuits, and host systems form an interdependent control system.

At project launch, agree on five points:

1. The business driver: failure exposure, spare-part availability, capacity, data integration, safety improvement, or standardization.
2. The replacement boundary: CPU, panel, machine, cell, or line.
3. Functions that must remain unchanged: machine sequence, quality parameters, operator workflow, and upstream/downstream interfaces.
4. The maximum shutdown window: normal weekend, long holiday, inventory buffer, or backup line.
5. The fallback: which old hardware, wiring, software, HMI, and network configuration can be restored, and by what deadline.

Without these decisions, bids are not comparable. One supplier may quote CPU conversion only, while another includes panel rewiring, simulation, FAT, on-site SAT, training, and source delivery.

Convert “old equipment” into measurable risk

Build a risk case from recovery time and production impact. Record the lead time for a replacement part, whether a verified program backup exists, whether a special module has a compatible replacement, who can troubleshoot the system, and the estimated loss per hour of downtime.

OMRON provides a Product Lifecycle Status tool that classifies product status. Check the official record for every exact part number at the time of the decision. Do not infer an end-of-life date from a family name or from another region. This article intentionally makes no prediction about discontinuation dates for specific CJ2, CS, CP, NX, or NJ products.

Audit the installed base before selecting the target PLC

Create four linked inventories: hardware, software, interfaces, and operations. Separate data that can be collected during production from checks that require a controlled stop.

Hardware inventory

• Full model and serial details for CPU, power supply, base, expansion racks, and every I/O module
• High-speed counter, positioning, analog, temperature, serial, and other special units
• Remote I/O, couplers, terminators, switches, and media converters
• HMI, industrial PC, servo, inverter, robot, vision, barcode, and test equipment
• Safety PLC or relay, emergency stops, guard switches, and light curtains
• Panel space, supply capacity, heat, grounding, terminals, and duct space
• On-site spares, repaired units, and common parts shared with other machines

Photograph the complete panel, module labels, terminal numbers, network routes, and nameplates. Then reconcile the photographs and live hardware with drawings. A photograph is evidence of configuration, not proof that a circuit matches its documentation.

Software inventory

• Editable PLC source, comments, symbols, data types, tasks, interrupts, and instructions
• Scan time, retentive areas, initialization, timers, counters, and clock functions
• HMI screens, alarms, recipes, logs, and access levels
• Motion parameters, homing, electronic cams, and correction values
• Routes, node numbers, tags, messages, timeouts, and reconnect logic
• Libraries, function blocks, external dependencies, licenses, and versions
• Backups and tested restoration procedures for PLC, HMI, drives, safety, and network devices

A file is not a verified backup until it opens, matches the online controller, includes all dependencies, and can be restored using an available engineering environment. Capture an online comparison and resolve discrepancies between the running PLC and the stored master before migration design begins.

Interface inventory

If the audit or software work will be contracted out, define editable-source delivery, responsibility boundaries, evidence, and acceptance before requesting quotations. See how to outsource PLC program development in Thailand for a practical contracting framework.

Assess CJ2-to-NX/NJ migration feature by feature

A CJ2-to-NX/NJ migration cannot be assumed to be a drop-in replacement simply because the products share a manufacturer. Program representation, memory concepts, variables, task execution, instructions, modules, networks, and the engineering environment may differ. After gap analysis, classify each function as automatically converted, manually corrected, redesigned, or retained on the existing system.

OMRON’s NX1P2 information describes built-in EtherCAT and EtherNet/IP and support for up to eight servo axes—four motion axes plus four single-axis positioning axes. OMRON also describes data links with CJ PLCs over EtherNet/IP. These capabilities may support staged migration, but they do not guarantee that every existing program, network, or device will work without change. Verify exact controller, unit, partner device, connection count, data size, and update-cycle requirements.

Migration architecture comparison

Why program conversion is not a performance guarantee

Import or conversion tools can reduce engineering effort, but compiled code is not proof of behavioral equivalence. Review instruction semantics, signed and unsigned values, BCD handling, integer widths, overflow, timer bases, floating-point behavior, indirect addressing, retentive data, startup initialization, scan order, interrupts, and communications completion timing.

IEC 61131-3:2025 defines syntax and semantics for programmable-controller languages such as Structured Text, Ladder Diagram, and Function Block Diagram. Use of standardized languages does not automatically make vendor-specific instructions, execution behavior, libraries, or hardware functions interchangeable.

Test each important sequence with controlled inputs. Compare state transitions, outputs, alarms, and timing against the legacy controller or against an approved new functional specification.

Control the Sysmac Studio environment

Sysmac Studio is OMRON’s integrated engineering environment for NJ/NX and related control, motion, safety, and vision functions. OMRON’s update page lists, for example, Version 1.67 in July 2026. The newest available version is not automatically the right project version. Check compatibility with the selected controller firmware, NX units, servo, safety controller, libraries, operating system, license, and the factory’s maintenance standard.

The RFP should define:

• Sysmac Studio version and the reason for selecting it
• Controller, unit, drive, and safety firmware versions
• Development, delivery, and future maintenance versions
• Library dependencies and any items that must not be upgraded
• Editable projects, comments, variable tables, and cross-references
• Passwords, roles, licenses, and all information needed for restoration
• Rules for online changes, approvals, version control, and backups

Engineer I/O, communications, and HMI differences

An equal I/O count does not prove equivalence. Terminal layouts, commons, voltage ratings, response, filters, diagnostics, and fail states can differ. If conversion adapters are used, verify rating, wiring logic, maintainability, and future replacement—not just pin alignment.

Build a point-by-point I/O reconciliation

For every signal, record the legacy address, new variable, terminal, field name, normal state, electrical specification, filter, fail state, and test method. The table should trace the complete path from field device to terminal, PLC logic, output, and actuator.

Test normally static signals, pulses, encoders, analog values, thermocouples, load cells, and high-speed counters with actual equipment or calibrated simulators. These signals are easily missed by a simple lamp-box test.

Test communication failures, not only connection success

Include these scenarios in FAT or SAT:

• Partner device stopped, cable removed, switch rebooted, duplicate IP
• Delayed response, timeout, packet loss, and reconnection
• PLC, HMI, or host-server restart
• Data type, byte order, scale, and character encoding
• Stale data, retransmission, duplicates, and clock offset
• Safe machine behavior while disconnected and controlled restart after recovery

Even where EtherNet/IP data links with CJ controllers are supported, verify tag design, data areas, update cycle, bandwidth, connection limits, and the exact partner devices. A protocol logo alone does not establish application compatibility.

Validate HMI behavior rather than copying screens

Similar-looking screens can behave differently. Verify button permissives, numerical ranges, units, recipes, permissions, alarm history, and data retention. Convert the complete screen list into test cases covering operation, setup, maintenance, quality, and administration.

In Thailand, confirm required English and Thai terminology, fonts, character rendering, and alarm searchability. Align HMI terms with training material and actual shop-floor language.

Include safety in the control-migration scope

Retaining an existing safety relay or safety PLC does not eliminate safety impact. Changes to standard outputs, contactors, valves, servos, resets, or operating modes may affect a safety function.

ISO 13849-1:2023 provides a methodology for designing and integrating safety-related parts of control systems. It does not automatically assign the required performance level, or PLr, to a machine. The risk assessment identifies safety functions and the necessary PLr; the design then addresses architecture, component reliability, diagnostics, common-cause failure, and software.

IEC 60204-1:2016+AMD1:2021 provides general requirements for the electrical equipment of machines, including protective measures, control circuits, emergency functions, documentation, and verification. Applicable law, customer standards, and other safety standards must be confirmed for the actual machine and location.

Safety checks for a PLC migration

• Stopping scope for emergency stops, guards, and presence-sensing devices
• Interaction between standard and safety outputs
• Prevention of unexpected restart and location of manual reset
• Mode selection, setup mode, limited speed, and limited power
• Contactor EDM, valve monitoring, and servo safety functions
• Safe state after power loss, communications loss, and controller fault
• Updated safety requirements, calculations, validation, and change record

Do not carry a critical safety defect into production as a routine punch-list item.

Put measurable requirements in the migration RFP

“Change CJ2 to NX” is not a sufficient specification. Give each bidder the same boundary, operating conditions, tests, and shutdown constraints.

1. Scope and responsibility

• Machines, panels, PLCs, I/O, HMI, drives, and networks included
• Items retained, replaced, or decided after survey
• Documents supplied by the buyer and surveys performed by the supplier
• Owners for mechanics, electrical, software, safety, and host integration
• Site access, languages, holiday work, transport, and permits

2. Survey and gap analysis

• Inventory of models, firmware, and engineering-software versions
• Online comparison and restoration check for all backups
• Instruction, memory, task, communications, and library differences
• Point-by-point I/O reconciliation and drawing discrepancies
• Evidence for items that cannot be converted or must be redesigned

3. Functional and performance requirements

• Cycle time, response, positioning, scan, and data-update limits
• Automatic, manual, setup, maintenance, abnormal, and recovery modes
• Alarms, history, recipes, and access control
• Behavior on power loss, communications loss, and sensor failure
• Legacy quality requirements and separately approved improvements

4. Cutover and rollback

• Durations for prefabrication, panel work, wiring, and downloads
• Production handover condition and test material
• Go/no-go criteria, decision time, and authorized approvers
• Rollback trigger, restoration method, and required duration
• Retention period for old parts, wiring, software, and backups

5. Testing and acceptance

• Design review, code review, FAT, SAT, and production observation
• Test cases, sample counts, acceptance limits, and evidence
• Fault injection, communications loss, power failure, restore, and rollback tests
• Correction, retest, extra shutdown, and cost responsibility

6. Handover and support

• Editable source, libraries, licenses, and controlled password transfer
• Drawings, I/O list, network map, parameters, and bill of materials
• Backups, restoration instructions, versions, and change history
• Operator, maintenance, engineering, and quality training
• Warranty, response time, local Thai support, and spare parts

Design the shutdown window minute by minute

“Complete during the weekend” is not a plan. Schedule production handover, final backup, isolation, wiring, panel work, electrical checks, I/O checkout, dry run, product trial, quality approval, management decision, and contingency by owner and by time.

Example cutover gates

These times are illustrative, not a commitment for a real machine. Calculate actual gates from wiring quantity, modification scope, test volume, risk, and contingency.

Reserve time for testing, correction, decisions, and restoration. The supplier’s installation duration is not the same as the factory’s time to stable production.

FAT: remove uncertainty before stopping production

FAT should test software behavior and abnormal recovery, not just panel workmanship. Use the actual PLC and HMI with real I/O where possible, and use validated simulators, communications emulators, or recorded data for unavailable field equipment.

For critical sequences, feed the same input timeline to the legacy and new logic and compare outputs and internal states. Define which behaviors must match exactly and which approved improvements may differ.

SAT: accept the system in the real factory

SAT adds actual power, grounding, wiring, noise, machines, materials, networks, operators, and upstream/downstream equipment. A simulator can be correct while a field contact polarity, analog scale, or partner-device timing is different.

SAT should include:

• As-built panel, grounding, labels, wiring, and drawing reconciliation
• Point-by-point I/O, homing, interlocks, and manual functions
• Automatic operation for every product, changeover, and recipe
• Integration with other machines, HMI, MES/SCADA, printers, and databases
• Emergency stops, guards, resets, power loss, and air loss
• Recovery from alarm, jam, sensor fault, and communications loss
• Sustained operation, stop analysis, cycle time, and quality approval
• Backup and restoration executed by local maintenance personnel

For a cross-vendor project model linking FAT/SAT to quality and traceability acceptance, see our practical guide to Siemens PLC migration in Thailand.

If minor issues remain, record the defect, effect, temporary measure, owner, due date, and retest method. Safety, critical quality, missing source, and inability to roll back should not be casually deferred.

Prove rollback and disaster recovery

Rollback requires more than storing the old CPU. The team needs the old HMI, I/O, wiring, network settings, parameter files, software, licenses, tools, trained people, and enough time. Avoid irreversible removal of legacy terminals until the go/no-go point has passed.

Rollback plan

1. Trigger: define which safety, quality, I/O, cycle-time, or host-system failures require rollback.
2. Decision time: identify the latest point at which rollback can still protect the next production shift.
3. Preserved assets: hardware, wiring, backups, parameters, and engineering environment.
4. Procedure: safe shutdown of the new system through energization of the restored system.
5. Minimum test: safety, critical I/O, manual, automatic, quality, and host links.
6. Approval: named personnel authorize the return to production.

Test recovery before the shutdown. Restore a controller project from a controlled backup using another PC or a clean engineering environment. Verify versions, drivers, license, cable, password, and libraries. Extend the exercise to HMI, drives, vision, switches, and industrial PCs.

Useful disaster-recovery drills include replacing a failed CPU from a spare, rebuilding the maintenance laptop, restoring lost switch configuration, reversing an incorrect download, and verifying safe restart after power loss.

Make training and source delivery acceptance items

Separate training by role. Operators need safe normal recovery. Maintenance needs diagnostics, replacement, and restoration. Controls engineers need approved change and version-control procedures. Quality staff must understand recipes, critical parameters, and product impact.

Provide English and Thai work instructions where needed, using the same terminology as the HMI. Measure training completion by practical demonstration, not attendance alone.

The handover package should contain editable PLC/HMI/motion/safety projects; libraries and dependencies; parameters; I/O, tag, IP, and node lists; drawings and bill of materials; development and firmware versions; FAT/SAT evidence; change history; and tested backup, restoration, rollback, and disaster-recovery instructions.

Build the financial case and verify BOI eligibility

Compare total ownership cost, including survey, design, panel work, software, tests, downtime, training, spares, and support. Full modernization may cost more initially but reduce spare varieties, recovery time, and future integration cost. A staged approach may be more rational for a low-utilization machine or a product near end of production.

As an illustrative estimate only, assume a total project cost of THB 6 million, annual avoided downtime and maintenance/quality benefit of THB 1.8 million, and additional annual support of THB 0.3 million. The simple payback would be:

6.0 ÷ (1.8 - 0.3) = 4.0 years

This is not a quotation. Use base, downside, and upside cases for failure probability, downtime cost, parts, exchange rate, tax, and cost of capital.

Thailand BOI’s Smart and Sustainable Industry materials describe conditions including a minimum investment of THB 1 million excluding land and working capital. For qualifying machinery and automation investment, the published framework describes a three-year corporate income tax exemption capped at 50% of eligible investment. The cap rises to 100% when the value of machinery linked with the domestic automation industry is at least 30% of the total value of machinery, automation systems, and robots used or upgraded in the project. Eligibility, activity, timing, equipment, calculation, and interaction with existing privileges require case-specific confirmation before ordering.

BOI reported 132 Smart and Sustainable Industry applications totaling approximately THB 17.2 billion in the first half of 2026. This indicates program activity; it does not guarantee approval or identical incentives for a PLC migration.

Compare suppliers on scope and proof

Place responsibility and evidence beside price. Ask:

• Is the full hardware, software, and communications audit included?
• When and how will unsupported instructions and units be identified?
• What input cases will be used for regression comparison?
• Who tests every I/O, fault, disconnect, power loss, and recovery?
• Who owns overtime, extra shutdown, and rollback execution?
• Are editable source, libraries, passwords, and licenses delivered?
• What Thai-based response time, spare support, and language capability apply?
• When does warranty start, and how are post-SAT items controlled?

Normalize proposals to a work breakdown structure and an exclusions list. A low initial price can be outweighed by site debugging, prolonged downtime, or missing source.

Common migration failures and how to avoid them

Leaving backup verification until the shutdown

Perform the online comparison and restoration check during the survey. If the running master cannot be identified after work has begun, the team loses both a reliable gap-analysis baseline and a credible rollback path.

Assuming equal I/O count means compatibility

Compare electrical characteristics, response, filters, diagnostics, and fail states, then test every point. Special units such as high-speed, analog, temperature, and motion interfaces require separate bench or hardware verification.

Declaring success when converted code compiles

A successful build is the beginning of validation. Regression-test state transitions, timing, fault handling, restart behavior, communications, and retentive data against the approved legacy behavior or new specification.

Skipping FAT and debugging during the site shutdown

This consumes the shutdown window with software corrections and leaves too little time for acceptance and rollback. Complete every test that does not require the real machine during FAT, and list the genuinely site-dependent tests before cutover.

Disposing of legacy parts immediately

Label and preserve old controllers, HMI hardware, units, terminals, and verified backups until SAT and the agreed stabilization period are complete. Assign a formal disposal date and approver.

Negotiating source delivery after acceptance

Put editable file formats, dependent libraries, passwords, licenses, firmware versions, and tested restoration instructions in the RFP and contract. Compiled runtime files alone are not a maintainable handover.

FAQ

Can a CJ2 program be converted automatically to NX/NJ?

There is no universal guarantee. Import or conversion may help, but instructions, memory, tasks, special modules, networks, safety, HMI, and libraries require individual review and hardware testing. Specify behavioral acceptance, not a promised conversion percentage.

Can existing I/O remain during a CJ2-to-NX migration?

It depends on the exact architecture. Confirm supported couplers and modules, electrical characteristics, diagnostics, timing, and maintainability. Reuse may reduce shutdown time but creates an old/new boundary that must have a clear owner.

Should a Sysmac Studio migration always use the newest release?

No. OMRON’s update information lists releases including Version 1.67 in July 2026, but compatibility with controller firmware, units, libraries, OS, license, and factory standards must be verified before fixing the project version.

What is the difference between PLC migration FAT and SAT?

FAT reduces software, panel, HMI, communications, and recovery risk before the site shutdown. SAT accepts actual field wiring, materials, networks, adjacent equipment, operators, and safety functions. FAT approval does not automatically mean SAT approval.

How should the shutdown window be estimated?

Add preservation, isolation, modification, electrical inspection, point I/O checks, dry run, product trials, quality approval, decision time, and rollback—not just installation labor. Include contingency based on unresolved risks.

Does ISO 13849-1 determine PLr automatically?

No. ISO 13849-1:2023 provides a design and integration methodology for safety-related control parts. The required safety functions and PLr come from the machine-specific risk assessment.

Can BOI incentives apply to a PLC modernization?

They may, but eligibility is not automatic. Confirm the investment, promoted activity, equipment, application timing, and the domestic-linkage ratio measured against the project’s total value of machinery, automation systems, and robots with BOI and qualified advisers before commitment.

Conclusion: use PLC migration to build a recoverable factory

An OMRON PLC migration is a revalidation of the machine’s assets, I/O, communications, HMI, safety, data, and maintenance process. Do not assume automatic equivalence when moving from CJ2 to NX/NJ. Establish requirements and responsibility in the RFP; reduce uncertainty through FAT; protect the shutdown with timed gates, SAT, rollback, and restoration tests; and require editable source and practical training.

TOMAS TECH can support the early audit, CJ2/NX/NJ migration concept, RFP review, shutdown planning, and FAT/SAT design for factories in Thailand. You can start while the replacement boundary and budget are still being evaluated. Contact us through the English inquiry page.

Sources

• OMRON, NX1P2 CPU Units: https://www.ia.omron.com/products/family/3650/
• OMRON, NX1P2 Catalog Downloads: https://www.ia.omron.com/products/family/3650/download/catalog.html
• OMRON, CJ2 Programmable Controllers: https://www.ia.omron.com/products/category/automation-systems/programmable-controllers/cj2/index.html
• OMRON Automation, Product Lifecycle Status: https://automation.omron.com/en/us/products/product-lifecycle-status
• OMRON, Sysmac Studio update information: https://www.ia.omron.com/product/tool/454/sysmac-studio/e1_doc.html
• IEC, IEC 61131-3:2025: https://webstore.iec.ch/en/publication/68533
• ISO, ISO 13849-1:2023: https://www.iso.org/standard/73481.html
• IEC, IEC 60204-1:2016+AMD1:2021: https://webstore.iec.ch/en/publication/26037
• Thailand BOI, Smart and Sustainable Industry: https://www.boi.go.th/index.php?language=en&page=smart_sustainable
• Thailand BOI/OSOS, First-half 2026 investment announcement: https://osos.boi.go.th/EN/news/2430/Thailand-Secures-43-6bn-1H-2026-Investment-Surge-as-Big-Tec/

*Compatibility, lifecycle status, software releases, safety requirements, and BOI conditions can change. Verify official information and the exact installed configuration immediately before the decision.*