Migrating from Legacy SCADA to Ignition
Key Takeaway
A practical guide to migrating from legacy SCADA platforms (FactoryTalk, WonderWare, GE iFIX) to Ignition — planning, tag conversion, screen migration, and phased cutover strategies.
Quick Answer
Migrating from legacy SCADA to Ignition involves tag database conversion, screen redesign in Perspective or Vision, historian data migration, alarm pipeline reconfiguration, and a phased cutover strategy that minimizes operational disruption. The effort varies significantly depending on the source platform, system complexity, and whether you're doing a lift-and-shift or a modernization redesign.
When to Consider Migration
Common triggers for legacy-to-Ignition migration include escalating per-tag/per-client license costs, end-of-life vendor support, difficulty finding engineers with legacy platform skills, desire for web-based mobile access (Perspective), and consolidation of multiple SCADA systems onto one platform.
Planning Phase
- Inventory: Document all tags, screens, alarms, reports, and integrations on the legacy system
- Gap analysis: Identify features that exist in legacy but need different approaches in Ignition
- Architecture design: Plan Ignition gateway placement, database selection, redundancy, and network requirements
- Phased cutover plan: Define which systems migrate first and how both platforms coexist during transition
Tag Migration
Ignition supports bulk tag import via JSON and CSV. For large systems, NFM develops automated conversion scripts that translate legacy tag databases into Ignition tag configurations, preserving engineering units, alarm limits, historian settings, and scaling parameters.
Screen Redesign
Legacy SCADA screens rarely translate directly to Perspective's web-based component model. Migration is an opportunity to modernize operator interfaces with responsive layouts, touch-friendly controls, and mobile access. NFM's managed Ignition SCADA services include Perspective development as part of our ongoing support retainer.
Historian Data Migration
Historical data from legacy historians can be migrated to Ignition's SQL-based Tag Historian using ETL scripts. The level of effort depends on the source historian format and the volume of data. NFM recommends migrating the most recent 2–5 years of data and archiving older data in its native format for reference.
Parallel Operation and Cutover
Best practice is to run Ignition in parallel with the legacy system during migration. This allows operators to validate data accuracy, alarm behavior, and screen functionality before cutting over. NFM's managed SCADA services provide support throughout the transition period.
Frequently Asked Questions
Migration timelines vary widely based on system complexity. A simple single-site migration might take 2–4 months. A large multi-site migration with hundreds of screens and thousands of tags can take 6–18 months with phased cutover.
Yes. Historical data from most legacy platforms can be migrated to Ignition's SQL-based historian using ETL scripts. NFM recommends migrating the most recent 2–5 years and archiving older data for reference.
Yes, but the learning curve is generally short. Ignition Perspective's web-based interface is intuitive for operators familiar with modern web applications. NFM provides operator training as part of migration projects.