— Legacy Migrations

Modernize the head-end. Keep the wiring.

Most controls firms quote a full rip-and-replace because it's easier to sell. It's rarely necessary. Legacy BAS platforms — pneumatic, TAC Xenta, I/A Series, Andover Continuum, LonWorks — can be modernized in phases without pulling wire out of the walls.

— The approach

A phased upgrade. Not a rip-and-replace.

A legacy migration is a phased upgrade of the building automation system. The software front-end goes first — modern EcoStruxure Building Operation or Niagara replaces aging TAC Vista, InSight, or a green-screen operator interface. The field wiring stays where it is.

From there, network controllers and field controllers migrate on their own capital cycles. Twisted-pair migration adapters bridge the legacy field bus to BACnet/IP so old field devices keep talking to the new head-end. Total capital spread over three to five years. No single big-line-item shock. And the building keeps running the whole time.

— The phased pathway

01

Head-end

New EcoStruxure Building Operation or Niagara front-end software. Existing field hardware keeps running. Smallest capital, biggest visibility change.

02

Network controllers

Twisted-pair migration controllers bridge the legacy field bus to BACnet/IP. Rolled out building by building, floor by floor.

03

Field controllers

Zone, AHU, and VAV controllers swap to current Schneider or Niagara hardware. Existing wiring stays in place.

04

Field devices

Sensors and actuators replaced where they need refresh. Some last decades. We replace what is worn — not what works.

— Platforms we migrate

Every legacy line has a documented path.

Athena is directly certified on the destination platforms — Schneider EcoXpert, Tridium Niagara, JCI Facility Explorer ASI. The migration path from each legacy line is documented, not improvised.

Legacy Platform Modern Destination Migration Approach
Pneumatic1950s–1990s compressed air BACnet DDC on Schneider EcoStruxure or Niagara Full electronic conversion over time. Electric-to-pneumatic transducers bridge existing actuators as an interim step. Zone by zone, floor by floor.
TAC XentaSchneider legacy line, Vista front-end Schneider EcoStruxure Building Operation End-of-commercialization. Schneider-published migration path. Same field wiring. New controllers, new front-end. Athena is EcoXpert certified on the destination.
I/A SeriesInvensys / Schneider legacy Schneider EcoStruxure Building Operation or Niagara End-of-commercialization. Replacement controllers only through used-market resellers. Direct upgrade to EBO — or vendor-neutral option through Niagara framework.
Andover ContinuumNow part of Schneider Electric portfolio Schneider EcoStruxure Building Operation End-of-commercialization. Direct Schneider-published migration path. Field wiring retained. Sequences of operation ported and verified against original design.
LonWorksField-bus protocol, twisted pair Two paths — twisted-pair adapter OR full rip-and-replace Path A: LonWorks-to-BACnet adapter keeps field devices in place, head-end goes native BACnet on Niagara. Path B: full field-device replacement when scope, budget, or vendor support drives it. We've done both — the twisted-pair migration ran on our own office building.

— The reality behind every row above

Every line in this table has reached end-of-commercialization. No new controllers from the manufacturer. Replacement parts available only from used-market resellers. Vendor support has ended. That's the reason to migrate — not because the wiring or the field devices have failed, but because the platform behind them is no longer sold.

— Why migrate at all

Legacy vs. modern BAS — where the gap widens.

Dimension
Legacy BAS
Modern BAS
Head-end software
Frozen version. Runs on Windows XP or older. No security patches.
Actively updated. Web-based. Signed updates, MFA, role-based access.
Field controllers
End-of-commercialization. Used-market resellers only. One failure away from a scramble.
Current production. Manufacturer-backed. Replacements from distribution.
Wiring & cabling
Fine. Nothing wrong with it.
Same wiring reused. Twisted-pair adapters bridge legacy field buses to BACnet/IP.
Vendor lock-in
Proprietary tools. Original vendor only. No competitive service quotes.
Open protocols — BACnet, Modbus, Niagara. Multiple qualified service firms.
Cybersecurity
Unpatched OS. Default credentials. No network segmentation.
Patched OS. Certificate-based authentication. IT-friendly network posture.

— How we do it

Five steps, in this order.

01

Site survey

Every pneumatic device, controller, and field wire documented before a single new cable is pulled. Skipping this is the number-one cause of change orders on migration projects.

02

Sequence of operations design

The new SOO goes in writing before installation. Owner reviews. Consulting engineer reviews if there is one. No surprises later.

03

Phased install

One floor at a time, or one system at a time, scheduled around occupancy. Full building shutdowns are rarely necessary. Schools get major work over summer breaks; medical campuses get it on weekend windows.

04

Programming, graphics, commissioning

The new front-end gets built out with real dashboards, alarms, and schedules. Every sequence verified against the design. Nothing gets marked "done" until the point-by-point checkout is signed.

05

Operator training

Half-day for facility teams. Included in the scope, not sold as an add-on. Ongoing refreshers through our service contracts if you want them.

— What owners save

The math against rip-and-replace.

Capital

Migration is typically 30–60% of a full rip-and-replace on comparable buildings. You spread that spend over three to five capital cycles instead of absorbing it in one.

Downtime

The building keeps running. New head-end goes in overnight or on weekend windows. No cold classrooms, no closed wings, no service disruptions to occupants.

Continuity

Same crew inside the panels. If the migration takes three years, the crew that started is the crew that finishes. Sequence knowledge stays in-house.

Platform flexibility

Every destination is either EcoStruxure (with Niagara underneath) or Niagara direct. Vendor-neutral by construction. No lock-in for the next capital cycle.

— Questions we hear

The four questions clients ask most.

How long does a migration take?

A typical migration runs three to five years across all phases, sequenced around your capital cycles. The head-end swap alone is measured in weeks. The building keeps running the whole time.

Which platforms do you migrate to?

Schneider EcoStruxure Building Operation is the primary destination for Schneider legacy lines (TAC Xenta, I/A Series, Andover Continuum). Niagara is the vendor-neutral option. For LonWorks and mixed BACnet field buses, Niagara is often the better fit.

What if we've already replaced part of the system?

Common. Most migrations we walk into have some newer controls mixed in with legacy. The design accounts for what's already there and preserves it.

Can we keep our existing wiring?

Usually yes. Twisted-pair migration controllers let legacy field wiring keep talking to a modern BACnet/IP head-end. Full rewires are only necessary when the wiring itself is failing — and that's uncommon.

— Questions to ask a vendor

The four questions a good vendor welcomes.

01

Which pieces need attention now — and which can wait a capital cycle?

No two components fail at the same rate. A vendor who quotes "everything, now" is quoting for their revenue, not your risk.

02

How does replacing this affect the systems around it?

BAS talks to HVAC, lighting, access, fire. Pulling one out without evaluating the others creates cascading problems the initial quote didn't contemplate.

03

Can the work align with a shutdown, renovation, or capital cycle?

Timing matters. A migration scheduled around a summer break costs less and disrupts less than one forced by a mid-February failure.

04

Who else needs to be at the table?

Facilities. IT. Finance. Your consulting engineer if you have one. The best migration decisions get made before anyone signs.

Aging BAS? Let's talk about a phased migration.

Send us what you're running today and what the head-end looks like. We'll come back with a migration path, a phased cost, and the questions we'd ask on a site walk.