WinCC to Ignition migration: a step-by-step guide
Moving from Siemens WinCC V7 to Ignition is a re-engineering project, not a file conversion. This is how we plan it so the plant keeps running.
Plan a WinCC to Ignition migration in five steps: a read-only scan of the WinCC project, a mapping of tags to Ignition UDTs, a rebuild of screens, alarms, history and scripts on a development gateway, a test against simulation or the real PLCs, and a planned cutover with WinCC kept as a fallback. Ignition is licensed per server with unlimited clients, tags and projects, and Ignition 8.3, released on 16 September 2025, is a long-term support version.
Why plants move, and when they should not
The usual reasons are licensing and access. Inductive Automation licenses Ignition per server, with unlimited clients, sessions, tags and projects, and its Perspective module runs in any browser, including on phones and tablets. Ignition 8.3 added a built-in REST API, Git version control and new historian modules.
Staying with Siemens is also a valid path. Siemens offers upgrade packages from WinCC V7.3, V7.4 and V7.5 to WinCC V8, which it describes as fully compatible with existing projects. If your team is fully Siemens and the system works, an upgrade can be the cheaper choice. See Ignition vs WinCC.
What moves where
| WinCC V7 | Ignition | What to watch |
|---|---|---|
| Tag management, structure types | Tags and UDTs (user-defined types) | Clean up first: unused tags and inconsistent names multiply in the new system |
| Alarm Logging | Alarm configuration on tags, alarm pipelines | Re-check priorities and texts; this is the moment to reduce alarm floods |
| Tag Logging archives | Tag history (historian) | Decide what history you migrate and what stays archived |
| Graphics Designer pictures | Vision windows or Perspective views | Rebuild, do not copy: use templates bound to UDTs |
| VBS and C scripts | Python scripts (Ignition scripting) | Scripts that write PLC tags directly need a design decision |
| User administration | Users, roles and security levels | Align with your IT directory where possible |
The five steps
- Read-only scan. We read the WinCC project with our own tooling: tags, structure types, alarms, archives, pictures, scripts and connections, plus cross-references. The result is a report of what is used, unused, broken or written directly by scripts.
- Mapping. We map the tags to a clean UDT structure for motors, valves, analog inputs and so on, agreed with your engineers.
- Rebuild on a development gateway. Screens, alarms, history and scripts are built on a separate Ignition gateway, never on the running plant.
- Test. Against PLC simulation where possible, then against the real controllers in an agreed window, screen by screen and alarm by alarm.
- Cutover. A planned switch with WinCC ready as a fallback, followed by the handover and training.
Where AI speeds this up
Our Engineering Assistant reads the WinCC project, finds where each tag is used, drafts the UDT mapping and drafts Ignition views bound to those UDTs. It also flags scripts that write to the PLC. An engineer reviews every screen, binding and script before it goes near production.
Questions we get
How long does a WinCC to Ignition migration take?
That depends on the number of pictures, scripts and tags and on how clean the project is. The read-only scan in step 1 gives a clear picture, and we base the plan and the price on it.
Can WinCC and Ignition run side by side?
Yes, during testing both can read the same controllers. Writing from two systems at the same time needs clear rules, so we agree which system is in control at each stage.
Do we have to change the PLC program?
Usually not for the migration itself. We check in the scan how each PLC will be connected and whether tags or data blocks need small changes.
Vision or Perspective?
Perspective runs in browsers and on mobile devices; Vision is a desktop client. For new projects we usually choose Perspective, unless your operators need specific desktop features.
Sources
A new line, an upgrade, or AI for your plant?
Tell us about your project and we will set up a technical call.
2800 Mechelen, Belgium E-mail: info@simsolutions.be Enterprise no. / VAT: BE 0680.932.773