Migrating from legacy SCADA
Inventory the existing system, map its functions, and agree a cutover sequence. Start with one area, compare operation during a parallel run, and establish a fallback for each step.
Catalog the legacy system.
Every PLC/controller, its protocol, and the point list with types, scan rates, and addresses.
Operator views and dashboards, plus which controls on them actually get used.
Which points are historized, at what resolution, and what downstream reports consume them.
Setpoints, priorities, and how operators are notified today.
Recipe tables, production logs, reports — anything reading or writing a database.
Who can see and write what, per area.
Map each item to what ships today.
Identify functions that need coexistence or additional integration, then agree the migration scope and sequence. Review the roadmap separately from available capabilities.
Pilot → parallel → cutover → sunset.
One line or cell. Enable authentication and use project roles without can_write_tags. Rebuild one operator screen, historize the required points, and verify driver behavior and data quality.
Legacy stays authoritative. Thermite SCADA reads the same field data; compare values, history, and screen behavior side by side over real shifts.
Per area: operators move to Thermite SCADA screens. With authentication enabled, grant write permission to the required roles. Retain the area's legacy screens as the agreed fallback.
After every area cuts over and downstream reports read from the new historian, decommission legacy per site.
Running both without crossed wires.
- Keep Thermite SCADA read-only during pilot and parallel — no field writes until an area formally cuts over.
- Confirm each device's session limits and polling load before adding a second client during the pilot.
- Where both systems speak MQTT, the broker is a clean shared read path.
- One project per area keeps cutover units independent — its screens, users, and publish lifecycle move together.
- Keep reviewed project source and configuration templates in Git. Revert and republish project changes; restore gateway settings through their reload or restart procedure. Keep live configuration and credentials in secured recovery backups.
Scope it with us.
Bring the inventory from step 01 to a technical session and we'll map it row by row, including functions that need coexistence or additional integration. Fixed-scope migration engagements are on Services.