Wonderware InTouch to Ignition migration: step by step
Many InTouch applications have run for decades. When licences, Windows or support dates force a decision, Ignition is a common destination. This is how to plan the move.
Migrate InTouch to Ignition by exporting the tag database, mapping tags to Ignition UDTs, rebuilding windows and alarms in Ignition, rewriting InTouch QuickScripts in Ignition Python, testing side by side and cutting over area by area. There is no automated converter for InTouch graphics to Ignition; tags can be exported and transformed. Typical triggers: AVEVA moved new licences of its major software to subscription in 2023, and older InTouch versions are leaving support.
What drives the decision
- Licensing: AVEVA announced in March 2023 that new licences for its major engineering and operations solutions are subscription-only, with perpetual licences tradeable for subscriptions.
- Support: according to AVEVA reseller Factory Software, limited support for InTouch HMI 2020 R2 ends on 3 January 2026, and InTouch 2023 has full support until 28 July 2027. Check the dates for your version with AVEVA.
- Windows: Windows 10 support ended on 14 October 2025, and many old InTouch nodes still run older Windows versions.
What moves where
| InTouch | Ignition | What to watch |
|---|---|---|
| Tagname dictionary (export it to CSV) | Ignition tags and UDTs | Group by equipment; many InTouch apps have flat tag lists |
| Access names / I/O servers | Ignition device connections or OPC UA | Check which drivers or OPC servers you need |
| Windows and symbols | Perspective views or Vision windows, templates | No automated graphics converter; rebuild |
| Alarms | Tag alarms, pipelines, journal | Review priorities |
| Historical logging | Ignition tag history | Keep the old history read-only or backfill |
| QuickScripts | Ignition Python scripting | Rewrite with intent, not line by line |
InTouch applications that are part of AVEVA System Platform (ArchestrA objects, Galaxy) need a deeper analysis: the object model has to be mapped to Ignition UDTs and scripts.
The steps
- Inventory. Export the tag database and list windows, alarms, history and scripts.
- Connect. Connect Ignition to the controllers, read-only at first.
- Tags and UDTs. Transform the tag export and build UDTs for repeated equipment.
- Rebuild and test. Rebuild windows from templates, run both systems side by side.
- Cut over. Area by area, with InTouch as fallback.
Where AI helps
AI reads the tag export and scripts, proposes the UDT structure, explains old QuickScripts and drafts Ignition views. An engineer finishes and tests. See SCADA to Ignition conversion tools and our AI toolkit.
Questions we get
Is there a tool to convert InTouch windows to Ignition?
Not an automated one according to Inductive Automation's forum. Windows are rebuilt; AI can draft them for an engineer to finish.
Can we keep our PLCs?
Yes. Ignition connects to the existing controllers through its drivers or OPC UA.
What about AVEVA System Platform?
It is a larger migration because of its object model. Start with an inventory of the Galaxy and decide what to rebuild as Ignition UDTs.
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