Legacy PLC Migration Guide: Repair, Source, or Replace

Three honest paths for an obsolete PLC platform — and how to choose without overspending or stopping production.

Quick diagnosis table

SymptomLikely causeAction
CPU fails, program has no backupTotal loss riskSource tested CPU, upload program first
Same rack fails repeatedlySystematic aging (power supply, backplane)Replace rack, keep I/O where possible
OEM no longer supports platformSpare risk on next failureStanding sourcing agreement as bridge
Expansion needed on full rackPlatform capacity limitPlan migration window, source spares meanwhile
Insurance or audit flags platformCompliance pressureDocumented migration to current platform

Step-by-step procedure

  1. Inventory the rack: CPU model, I/O count, comms modules, power supply — photos of every nameplate.
  2. Get a program backup NOW if none exists — before the next failure makes it impossible. This is the step that saves the migration budget.
  3. Price the repair path first: capacitor, fan and board-level repairs are typically 40-60% of replacement cost.
  4. Price the tested-surplus path: a sourced CPU or module with a 12-month warranty is usually the fastest way back to production.
  5. Price the migration path: platform choice, program conversion effort, panel changes and commissioning — get it quoted by an integrator, not guessed.
  6. Run a bridge strategy: standing sourcing agreement on the legacy platform while the migration is scheduled, so a failure during the transition does not stop the line.

Replacement parts & selection notes

We support all three paths. For repair and sourcing, see our platform pages: Siemens S5, Allen-Bradley PLC-5, SLC 500, Omron C200H, Mitsubishi A series, GE Fanuc 90-30 and Modicon 984/TSX. Send your rack photos for a free compatibility check and a quote within 12 hours.

Frequently asked questions

My legacy PLC has no program backup — what now?

Upload it before anything fails. If the CPU still runs, a technician can extract the program via the legacy programming hardware — we can arrange this before you commit to a path.

Is migrating always the right long-term answer?

Not always. If the machine has 5+ years of life left, a tested surplus CPU plus a bridge sourcing agreement is often cheaper than migration. Migration wins when failures become frequent or the platform blocks production changes.

How much downtime does migration take?

Typically 2-6 weeks for engineering and panel build, with the actual cut-over in a planned outage window. Sourced spares keep the line running during the whole process.

Can you supply the whole obsolete spares list for our plant?

Yes — for plants with a known legacy equipment list we set up standing sourcing agreements with agreed response times and pricing bands.

Related pages