Niagara AX is legacy. Ongoing development, security updates and driver support are all on N4, and the pool of people and tools that still work comfortably with AX keeps shrinking. Migration is not optional indefinitely — the only real question is whether it happens on your schedule or during an emergency.
We plan and deliver AX-to-N4 migrations as staged projects with a way back at every step, not as a weekend conversion.
What a Migration Actually Involves
- Station and module inventory — exactly what is installed, before anyone commits to a date.
- JACE hardware assessment — some controllers cannot run N4 and must be replaced. Better known at week one than week six.
- Driver and integration validation — every BACnet, Modbus and LonWorks integration confirmed on N4.
- Graphics rework — usually the biggest surprise. Legacy Px graphics often need rebuilding for N4’s HTML5 environment; we scope it explicitly rather than discovering it mid-project.
- Scripting and custom logic review — legacy AX scripting does not always transfer one-to-one.
- Staged cutover — converted and validated in a test environment before production is touched, with the old system recoverable until the new one is proven.
- Point-by-point verification — every input reads, every command works, every schedule and alarm behaves.
Why the Verification Half Matters Most
A migration that looks finished but was never systematically checked is how a comfort complaint becomes a 2am call. We verify the migrated system against the original before anyone depends on it, and we tell you what we found rather than reporting a clean sweep by default.
The reasoning is set out at length in our article on what an AX-to-N4 migration actually involves. The tooling we are building to accelerate the assessment stage is described under solutions in development.
Tell us what you are running today — Niagara version, station count and controller models — and we will assess the path to N4 and what it realistically costs.
Related services
- Niagara Framework Development — Back to the full Niagara Framework development overview.