All Articles Protocols

LonWorks in 2026: Is It Time to Migrate?

Assessing whether your LonWorks system still makes sense or if migration is overdue.

January 9, 2026 10 min read Controls NYC
LonWorks in 2026: Is It Time to Migrate?
LonMark Certified Logo LonWorks Protocol Logo

LonWorks was once a leading building automation protocol. If your building runs on LonWorks — particularly if built or renovated between 1995 and 2010 — you're not alone. But the landscape has shifted dramatically.

The Current Reality

📉
Market Share
🔧
Limited Support
👴
Aging Workforce
⚠️
Parts Scarcity
The Hard Truth

BACnet has won. Most new construction specifies BACnet, most new products prioritize BACnet, and the talent pool has shifted accordingly.

LonWorks technicians are retiring, and few new technicians are learning the technology. Service costs are rising.

When to Consider Migration

Difficulty Finding Service

Struggling to find qualified providers, or service costs have increased significantly.

Equipment End-of-Life

If major components need replacement anyway — opportunity to migrate instead of hunting for LonWorks parts.

Integration Requirements

New equipment often speaks BACnet but not LonWorks. Native integration is simpler than gateways.

When to Stay with LonWorks

Migration Isn't Always the Answer
  • System works well — meets operational needs with adequate service support
  • Limited budget — strategic maintenance while planning eventual migration
  • Building sale planned — focus on maintaining functionality until sale
  • Good service relationship — reliable provider who knows your system

Migration Strategies

1
Supervisory Overlay
Lowest initial cost
  • Keep existing LonWorks controllers
  • Add BACnet supervisory layer
  • New equipment connects via BACnet
  • Replace LonWorks as devices fail
2
Phased Replacement
Spread costs over time
  • Start with priority areas
  • Replace in budget-aligned phases
  • Maintain operation throughout
  • Eventually full BACnet
Option 3: Complete Replacement
New BACnet controllers throughout, new supervisory platform, clean break from legacy technology. Higher upfront cost, faster completion. Makes sense when coordinated with other building work.

Cost Expectations

$50-150K
Supervisory Overlay
$150-500K
Phased Migration
Similar
Complete Replace
Varies
By Building Size

Making the Decision

  1. Assess current system health: How functional is your LonWorks system today?
  2. Evaluate service availability: Can you still get qualified, reasonably-priced service?
  3. Consider future requirements: What capabilities will you need?
  4. Review budget capacity: What capital is available, and when?
  5. Plan building lifecycle: What other changes are anticipated?

Getting Expert Advice

At Controls NYC, we have experience with both LonWorks systems and BACnet migration. We can help you assess your current system and plan a migration strategy that makes sense for your building.

Contact us for an honest evaluation of your LonWorks system.

Ready to Discuss Your Building?

Whether you're evaluating an upgrade, dealing with a failing system, or just want a second opinion — we're happy to talk through your options.

Schedule a Free Consultation

Continue Reading