Niagara AX is Unsupported: You Must Migrate to N4 Now
Tridium’s Niagara AX platform has been on a managed sunset for years. Niagara 4 (N4) was released in 2015. The ecosystem has been moving steadily toward it since.
If you’re running AX in 2026, you’re running on a platform that no longer receives feature updates. Third-party module support is increasingly N4-only. The security posture is materially behind current expectations.
The migration is usually less painful than people fear. However, only if you plan it. So here’s what to expect.
Niagara Hardware
AX runs on legacy JACE-2, JACE-3, JACE-6, and JACE-7 hardware. N4 runs on JACE-8000 and the newer JACE-9000 platforms. Older hardware cannot run N4.
As a result, you will replace the JACE hardware as part of the migration. This is unavoidable. The good news: the new hardware is faster, has more memory, and runs N4’s modern architecture comfortably.
Niagara Station conversion
Tridium provides a station conversion tool that adapts AX stations to N4 stations. For typical building automation stations — graphics, schedules, alarms, point histories, BACnet drivers — the conversion is straightforward.
Also, the Fox protocol (Niagara’s native inter-station communication) is compatible between AX and N4. This means you can run a mixed environment during the transition window.
Niagara Module compatibility
Third-party modules and custom Java code from the AX era do not automatically run on N4. They need to be ported, recompiled, and in some cases rewritten by the module developer.
Before scheduling the migration, inventory every third-party module in your station. Then verify N4 versions exist. If a module is from a vendor who’s no longer active, you need a replacement strategy.
Niagara Graphics
AX graphics built in the Px editor convert reasonably well. However, they were designed for the AX rendering engine. The N4 rendering engine is HTML5-based, supports modern browsers without plug-ins, and has substantially better mobile rendering.
Most clients use the migration as an opportunity to refresh graphics rather than carry forward 10-year-old screens designed for Internet Explorer.
Niagara Security model
This is the biggest functional change. N4 is secure by default — strong authentication required, certificates managed, encryption on by default for data in motion and at rest.
An AX station migrating to N4 will require an authentication overhaul. Every user account audited. Role-based access redefined. Default passwords retired. Integration credentials regenerated.
If your AX environment has 20 service technicians who have all used the same shared admin password since 2014, you’re going to feel this change. However, the change is overdue.
BACnet/SC
N4 supports BACnet/SC; AX does not. If your roadmap includes BACnet/SC adoption for cybersecurity reasons, the AX-to-N4 migration is a prerequisite.
Time and budget
For a typical campus with 5–10 JACEs and a Supervisor, plan a 3–6 month migration window. Break the project into building-by-building phases.
Budget includes new JACE hardware, N4 licensing for each station, third-party module ports where applicable, Supervisor migration, and integrator labor. Most projects we run come in at $8,000–$15,000 per JACE depending on station complexity and graphics scope. Supervisor migration is on top of that.
The cost of not migrating
AX is functional in 2026 but increasingly stranded. New third-party drivers and modules are N4-only. The security posture is below what most institutional clients will accept on a five-year horizon. Vendor escalation support is deprioritized.
The migration is going to happen eventually. The only question is whether it happens on a planned schedule or in response to a security incident. Read more on our Retrofit & Modernization page.
| Talk to Signet Controls. Planning a BAS install, retrofit, integration, or service contract in California? We work across Los Angeles, Orange County, the Inland Empire, the Central Coast, and Kern County. Reach our team at info@signetcontrols.com or call (877) 874-4638. |