Ladder Migration Overview
Ladder Migration brings ladder programs from other vendors into TIA Portal, using the AI Agent and a small helper program (the Ladder Migration MCP server) that does the exact, repeatable parts of the work. There are two paths. Pick the one that matches what you have.
Which path should I use?
Section titled “Which path should I use?”| You have | Use | Result in TIA Portal |
|---|---|---|
| A PDF printout of a ladder program (any vendor) | PDF to SCL | An SCL function block or function, with comments |
An .L5X export from Studio 5000 (Allen-Bradley) of a whole controller project |
Studio 5000 project to native Ladder | Native LAD functions and function blocks, data types, data blocks, tags, technology objects |
An .L5X export of one routine |
Ask the agent to migrate that routine; it uses the same translator as the project path, for a single block | One native LAD function block |
The .L5X path is the more capable one. The export contains the exact structure of every rung (contacts, polarity, branches, outputs), so nothing has to be read from a picture, it needs far less AI usage because a program does the translating, and the result is checked automatically against the source. A PDF has to be read as images, so contact polarity and the extent of branches can be misread, and every result needs a careful review.
What the migration does (both paths)
Section titled “What the migration does (both paths)”- The agent reads the program (from the PDF with vision, or exactly from the
.L5X). - A translator turns it into TIA Portal code. For the
.L5Xpath this is done by program code, not by the AI model, so the same input always gives the same output. - The agent imports the result into TIA Portal, compiles it, and reports compiler errors.
- Anything that cannot be translated is not guessed. It becomes a clearly labelled placeholder (see Reviewing migrated Ladder).
How much is translated
Section titled “How much is translated”It depends on the program. On the real project exports we tested, between roughly two thirds and nine tenths of the rungs became native Ladder. The rest are placeholders that you finish by hand, or ask the agent to finish. Every one of those projects imported into TIA Portal and compiled without errors, and when we exported the imported blocks back out of TIA Portal they matched the rungs they came from.
What is not translated
Section titled “What is not translated”- Instructions that talk to other devices (for example message instructions): the placeholder describes what the original does and which S7 mechanism normally covers it.
- Some motion instructions and cam functions, and the parts of a motion or PID setup that cannot be set from outside (servo gains, PID gains). See Motion and PID.
- GuardLogix safety routines are translated only as reference blocks that are never called. Rebuild safety functions with F-blocks on an F-CPU.
- Routines written in other languages than ladder (function block diagram, structured text, sequential function chart).
Requirements
Section titled “Requirements”- The Ladder Migration MCP server connected (Settings → Connections → Ladder Migration MCP).
- TIA Portal V21 (native Ladder needs V20 Update 4 or later; V21 is what we test) connected, with a PLC in the project, if you want the agent to import the result.
- The input file inside your workspace folder (Settings → AI Agent → Workspace). The agent can only read and write there.