Whether the cross-reference actually holds
A paper match can still differ in signal type, scan behaviour, instruction set or mounting. The question is what changes when you fit it.

For · System integrators
A migration is more than a part-number match. Automation Liberty helps integrators identify candidate hardware, software dependencies, wiring changes and commissioning boundaries before the work is quoted.

A paper match can still differ in signal type, scan behaviour, instruction set or mounting. The question is what changes when you fit it.
Platform-specific logic, drivers and safety interfaces do not carry across. Knowing that share before quoting is the difference between margin and loss.
Supply, re-implementation, panel changes and acceptance are four scopes. Quoting them as one is how migrations overrun.
Competitor part numbers are mapped to candidate replacements — subject to engineering review of electrical, mechanical, software and safety constraints.
Projects from TIA Portal, GX Works, Sysmac or other ecosystems are reviewed for explicit logic, library and I/O re-implementation in the target environment.
Terminal layout, signal type, I/O map, communications and EMC considerations are checked against the available drawings and application.
Remote guidance or site work is included only when its access, deliverables and responsibilities are explicitly scoped and confirmed at quotation.
Send the current program, drawings, I/O list, device list and machine acceptance requirements that are available.
Engineering identifies platform-specific logic, drivers, protocols, safety interfaces and undocumented assumptions.
The proposal states what carries over, what is re-implemented and what must be validated at bench or machine level.
Deliverables, access, quotation, availability and scheduling are confirmed after the technical boundary is understood.
Automation Liberty works in three ways. These are the ones that normally apply to you.
Competitor part numbers mapped to candidate replacements, with the mismatches stated rather than hidden.
OpenWhat carries over from the source project and what has to be revalidated in the target system.
OpenLogic re-implementation scoped from your existing program rather than machine-translated.
OpenStart from what the machine does: I/O and signal types, fieldbus and protocol devices, motion, safety scheme and the existing program. A candidate is identified against those with its differences listed — and stays subject to engineering review.
It depends on how much of the program is platform-specific. Standard logic usually re-implements cleanly; vendor libraries, motion blocks, drivers and safety configuration are rebuilt with explicit I/O mapping. The audit separates the two before quoting.
No — automatic conversion carries platform assumptions into a different runtime, where they fail at commissioning. Logic is re-implemented in the target environment with a stated I/O map.
Remote guidance is the normal route and can be scoped with the programming work. On-site attendance is quoted separately, with access, deliverables and responsibilities agreed in writing first.
Send the source project and available machine documentation so the conversion boundary can be reviewed.