Renovating a Legacy SCADA: 6 Steps from Planning to Cutover

Your SCADA is 10+ years old, license renewal is expensive, vendor support is weakening. Replace fully or modernize? A 6-step renovation roadmap based on field practice.

Many industrial sites have a SCADA installed between 2010 and 2015, kept alive with minor patches ever since. Operators have memorized the screens, alarms are tuned, reports are standard. But: hardware ages, spare parts get scarce, the vendor stops supporting Windows 7, and annual license renewals grow more expensive every year.

The renovation decision is hard because "it works". Until one day it doesn't — and then there's no luxury of strategic planning. Here's the proven sequence for planned SCADA renovation, based on field experience.

Step 1: Inventory the current system

Most sites have outdated SCADA documentation. Capture reality first:

Hardware: PLC make/model, SCADA server OS, number of HMI panels
Software: SCADA product/version, license type, runtime (Citect, Wonderware, iFix…)
Protocols: which devices use which protocol (Modbus, BACnet, Profibus, OPC-DA…)
Tag count: how many variables are being read/written
Historical data: retention period and database type

Step 2: Mark the pain points

Spend 30 minutes with operators. "What frustrates you most?" gives more than any inventory:

"Can't access from mobile, we have to sit in the office"
"Adding a new building requires another expensive license"
"We download reports to Excel and merge them manually"
"OPC-DA disconnects weekly and we restart it"

Step 3: Design the target architecture

Web-based access — browser, tablet, phone
Vendor-neutral protocols — native Modbus, BACnet, KNX, OPC-UA
Open data layer — REST API, MQTT publish, CSV export
Horizontal scalability — per-tag pricing rather than per-license
Container/VM ready — not locked to a specific Windows version

Step 4: Start with a pilot zone

Don't replace everything at once. Pick one building, one line, or one system (e.g. HVAC). Install the new SCADA and run in parallel with the old one for 4-8 weeks.

Step 5: Migrate historical data

You don't want to lose 10 years of trends. Plan migration from the legacy database (usually SQL Server or proprietary) to the new time-series store (InfluxDB, TimescaleDB, Prometheus).

Tip: Migrating everything isn't always necessary. Last 24 months + annual summaries cover most reporting needs. Archive older data offline.

Step 6: Phased cutover and training

After successful pilot, rollout takes 6-12 months. Each phase:

Operator training (new UI, alarm handling)
Per-shift shadow running (old + new in parallel)
Move old SCADA to read-only, then decommission
Two weeks of on-call support after each phase

NEOVUS experience: At a banking data center we migrated a 14-year-old SCADA to Argus in 9 months. Operator response time dropped 40%, mobile access reduced overnight on-call cost, and annual license renewal went from $14,000 to zero.

If your system is due for renewal, share your inventory — we can produce a realistic roadmap and cost projection within 2-3 weeks.