/ Engineering · Migration
Legacy to modern,
documented end-to-end.
The migration paths TechnoGuru handles repeatedly — protocols, infrastructure, fire, surveillance, power, networking — each with complexity, retrofit implications, caveats and a future-readiness note.
- Migration paths
- 8
- Major migrations
- 3
- Phased migrations
- 4
- Incremental migrations
- 1
/ phased migration
Modbus RTU plant tail → BACnet/IP supervisory
Bringing a legacy RTU plant tail (chillers, AHUs, pumps) into a BACnet/IP supervisory tree via a documented gateway and re-tagging discipline.
Most operating buildings have a Modbus RTU plant tail that was specified at a point when the supervisory BMS layer did not exist. The migration is not the replacement of the RTU devices — they often have ten years of life left — but the addition of a Modbus-to-BACnet gateway and the re-tagging of the points into the BACnet object model. The gateway becomes a documented seam: which Modbus register maps to which BACnet object, which scaling factor applies, which alarm priority is preserved. The discipline is the gateway map, not the gateway hardware. Done well, the migration takes the plant from a polled-only state to an event-driven BACnet supervisory tree without disturbing the underlying mechanical control. Done poorly, the gateway becomes a single point of failure with undocumented mappings that the FM team cannot reproduce. The engineering pack on the migration includes the gateway map, the alarm priority cross-walk and the post-migration trend baseline.
- Drivers
- integration-gap · scalability
- Retrofit
- non-disruptive
- Lifecycle
- operations · retrofit
- Duration
- 8–12 weeks on a 200,000 sq ft corporate fit-out
Operational caveats
- · Polling rate on the gateway must match the slowest RTU device — over-polling causes register glitches.
- · Alarm priority mapping is the single highest-risk artefact during cutover.
Maintenance posture
- · Gateway map becomes a versioned document — every device change updates it.
- · Annual gateway firmware review is added to the AMC.
Future readiness
- · Gateway-mediated tree leaves space for BACnet/SC adoption when the BMS supports it.
- · Re-tagged objects are exportable to Project Haystack tagging downstream.
Sunset guidance
- · Legacy RTU master station is decommissioned only after 90 days of dual-running.
- · RS-485 trunks are documented as legacy but retained for vendor maintenance access.
/ phased migration
Analogue 0–10V or DSI lighting → DALI-2 addressable
Migrating an analogue (0–10V or DSI) lighting estate to a DALI-2 addressable bus that gives per-luminaire control, scene programmability and energy reporting.
Analogue lighting buses are still common in retrofits — 0–10V dim wire, broadcast DSI, or proprietary ballast control. The migration to DALI-2 is rarely a complete drop-in; it is a phased re-cabling and addressing exercise that updates the bus while leaving most luminaire fixtures in place. DALI-2 brings per-luminaire addressing (up to 64 ballasts per segment), bidirectional status, and a published scene catalogue — none of which the analogue bus can offer. The migration touches three engineering artefacts: the wiring update (DALI is polarity-insensitive but topology matters), the addressing map (which ballast is which scene actor) and the scene catalogue (the canonical record of what every keypad press should do). Where a KNX backbone is also being introduced, the migration is bundled with the KNX/DALI gateway commissioning so the building emerges with both the bus and the supervisory logic upgraded in one pass.
- Drivers
- performance · obsolescence · scalability
- Retrofit
- phased-handover
- Lifecycle
- build · operations · retrofit
- Duration
- 6–10 weeks on a 50,000 sq ft hospitality fit-out
Operational caveats
- · Scene rebuild is the highest-risk artefact — every keypad press changes meaning.
- · Energy reporting baseline shifts at cutover; the first month is reported against a re-baseline note.
Maintenance posture
- · Bus segmentation increases AMC site visits in year one; stabilises in year two.
- · Per-luminaire spares pool replaces ballast spares pool.
Future readiness
- · DALI-2 ballasts are software-extensible — colour tuning and emergency reporting can be enabled in firmware.
- · Bus is gateway-ready for KNX, BACnet or future tunable-white control logic.
Sunset guidance
- · Analogue dim wire is left in place but de-energised, labelled at the panel.
- · Old broadcast keypads are removed or repurposed as DALI master cells.
/ phased migration
Cat5e copper estate → Cat6A PoE++ backbone
Re-cabling a Cat5e estate to Cat6A so that IEEE 802.3bt PoE++ devices (PTZ cameras, wireless APs, IP intercoms) get the headroom they need without re-engineering the IDF rooms.
Cat5e was the right specification for the 100-Mbit access edge of its era. The PoE budget it can deliver and the channel headroom it offers are not sufficient for an IEEE 802.3bt (60–90 W) class of devices. Migration to Cat6A is a structured-cabling exercise — drop replacement, IDF patch update and channel certification — rather than a switch replacement, because the switches are typically already PoE++ capable. The discipline here is the certification pack. A migrated channel is only a migrated channel if it is certified to the Cat6A field standard with a documented sweep — return loss, NEXT, PSANEXT, alien crosstalk. Without that, the migration is a cable swap with no measurable improvement. Our engineering pack on this migration includes the per-channel certification, the IDF airflow review (Cat6A bundles run hotter) and the PoE budget recompute against the new device manifest.
- Drivers
- performance · scalability
- Retrofit
- phased-handover · live-cutover
- Lifecycle
- build · operations · retrofit
- Duration
- 10–14 weeks on a 250,000 sq ft enterprise estate
Operational caveats
- · IDF airflow shifts measurably under denser Cat6A bundles — the post-migration baseline is reported.
- · PoE budget recompute can demote some legacy devices to PoE+ pending channel certification.
Maintenance posture
- · Per-channel certification report becomes part of the AMC handover pack.
- · PoE budget is treated as a versioned document, updated at every device add.
Future readiness
- · Cat6A channel certification leaves headroom for 10GBASE-T and 802.3bt PoE++ devices.
- · Future Wi-Fi 7 access points and multi-gig switches drop in without further cabling work.
Sunset guidance
- · Decommissioned Cat5e is left in containment but disconnected at both ends, labelled at the patch panel.
- · Old IDF airflow baseline is archived alongside the new certification report.
/ major migration
Diesel genset + lead-acid UPS → LFP BESS + downsized genset
Replacing a single-source diesel genset and lead-acid UPS with an LFP battery energy storage system (BESS) and a smaller genset, sized for true mission-critical loads.
The genset-first power posture was built for a grid that brown-out-tripped weekly. The grid has matured; the load profile has not. Most facilities now run a genset that is two sizes oversized against the actual operating load, with a lead-acid UPS that is end-of-life every three years. Migration to an LFP BESS resets the posture: BESS handles the seconds-to-minutes ride-through and PQ shaping; the genset is downsized to cover only the true mission-critical load over multi-hour outages. Engineering this transition is a load-and-lifecycle exercise. The load profile is metered for 30 days. The BESS is sized for the energy envelope, not the peak. The genset is re-sized for the energy gap beyond the BESS. The room is re-laid out (LFP has a smaller and quieter footprint). The result is a cleaner power posture, lower lifetime cost and far easier compliance with NFPA 855 for the storage room. The lead-acid UPS is decommissioned along the way.
- Drivers
- operational-cost · obsolescence · compliance
- Retrofit
- shutdown-required · phased-handover
- Lifecycle
- design · build · commissioning · operations
- Duration
- 16–24 weeks including BESS room qualification
Operational caveats
- · Cutover requires a planned ride-through window — the legacy UPS string is offline for 4–8 hours.
- · Genset re-tuning is required against the new load profile.
Maintenance posture
- · Battery health monitoring replaces annual UPS string replacement.
- · Genset run-hours fall sharply; oil change schedule shifts from monthly to quarterly.
Future readiness
- · BESS is grid-services ready — peak shaving, demand response, time-of-use shifting.
- · Solar coupling is a software change, not a panel re-layout.
Sunset guidance
- · Lead-acid UPS is decommissioned and the strings sent to certified recycling.
- · Genset is re-tuned and retained as the long-outage cover.
/ incremental migration
Wi-Fi 6 estate → Wi-Fi 7 (320-MHz) uplift
Migrating a Wi-Fi 6 estate to Wi-Fi 7 — wider channels, MLO, deterministic latency — without disturbing the structured cabling.
Wi-Fi 6 was specified for an era where 80-MHz channels and OFDMA were the differentiators. Wi-Fi 7 brings 320-MHz operation, multi-link operation across the 2.4/5/6-GHz bands and per-flow deterministic latency for AR and unified comms. The migration is largely an access-point swap; the cabling is already Cat6A in most modern fits. The discipline is the channel plan, not the hardware. Wi-Fi 7 channel reuse over 320 MHz requires a careful 6-GHz survey, and existing 5-GHz radar avoidance rules still apply. Where the cabling is not Cat6A, the migration is staged behind a Cat6A pull. The PoE++ uplift is bundled — Wi-Fi 7 access points pull more than 802.3at can deliver, so the switches need to be PoE++ capable. Once landed, the estate has the headroom for 2.5/5-Gbit access, latency-sensitive collaboration and the next two product cycles of mobile devices.
- Drivers
- performance · scalability · lifecycle-end
- Retrofit
- non-disruptive
- Lifecycle
- operations · expansion · retrofit
- Duration
- 4–8 weeks on a 150,000 sq ft enterprise estate
Operational caveats
- · 6-GHz survey is the highest-risk artefact — interferers are still poorly mapped in dense Indian metros.
- · MLO behaviour on legacy clients is a 90-day stabilisation window.
Maintenance posture
- · Annual RF survey is added to the AMC.
- · Wi-Fi 7 access points have a faster firmware cadence than Wi-Fi 6.
Future readiness
- · 320-MHz channel plan is the foundation for AR / collaboration / on-prem AI inferencing.
- · Estate is ready for the Wi-Fi 8 refresh without re-cabling.
Sunset guidance
- · Wi-Fi 6 access points are re-deployed to lower-density spaces or warehoused as spares.
- · Channel plan documents are archived against the survey baseline.
/ major migration
Conventional fire alarm → addressable, peer-to-peer panel
Migrating a zone-based conventional fire alarm system to an addressable, peer-to-peer panel that meets the IS 2189 / EN 54 expectations of a modern building.
Conventional fire alarm systems report at the zone level — the detector that triggered the alarm is known only to the wiring topology. Addressable systems report at the device level and support cause-and-effect logic across panels. Migration is a documented retrofit: the wiring needs to be loop-tested for end-of-line resistance, every device is re-addressed, and the cause-and-effect matrix is re-written against IS 2189 sections and the building's evacuation plan. The hardest engineering work is the cause-and-effect re-write. A zone-based system has implicit cause-and-effect baked into the zone wiring; the addressable system makes it explicit. Every alarm input, every output, every staged evacuation, every smoke-control interlock is documented. The AHJ review on the new system is against the cause-and-effect matrix, not the panel. Our handover pack includes the IS 2189 clause-by-clause sign-off and the matrix.
- Drivers
- compliance · obsolescence
- Retrofit
- live-cutover · phased-handover
- Lifecycle
- build · commissioning · operations · retrofit
- Duration
- 10–16 weeks on a 100,000 sq ft fit-out
Operational caveats
- · Cause-and-effect re-write requires an AHJ walk-through — schedule this with the panel sign-off.
- · Detector spacing review is bundled with the migration.
Maintenance posture
- · Per-device serviceability extends the AMC visit length but reduces site visits.
- · Loop integrity monitoring is now a panel-level alert.
Future readiness
- · Addressable panels integrate cleanly into BMS supervisory views.
- · Cause-and-effect matrix is the basis for any future smoke-control or staged-evacuation extension.
Sunset guidance
- · Conventional zone wiring is retained as the back-up path during a six-month dual-running window.
- · Old panel is decommissioned with formal AHJ closure.
/ major migration
Standalone PA → integrated PA + voice-evacuation (EN 54-16)
Migrating a standalone background-music PA system into an EN 54-16 / IS 14735 voice-evacuation system integrated with the addressable fire panel.
A background-music PA system is not a voice-evacuation system. The migration is a controlled re-engineering: amplifier chains are re-rated, line-supervision is added to every speaker run, message priority is mapped against the fire panel cause-and-effect, and the system is certified against EN 54-16 or IS 14735 clauses. The cabling often survives the migration; the amplifier racks usually do not. The seam between the fire panel and the voice-evacuation panel is the hardest artefact. Both panels need to agree on message priority, alarm staging, and which inputs override which outputs. Our engineering pack on this migration includes the priority cross-walk, the EN 54-16 / IS 14735 clause-by-clause sign-off, and the post-migration full-building drill record.
- Drivers
- compliance · integration-gap
- Retrofit
- phased-handover · shutdown-required
- Lifecycle
- build · commissioning · operations · retrofit
- Duration
- 8–12 weeks on a 80,000 sq ft fit-out
Operational caveats
- · Drill record must be re-baselined post-cutover; site-wide sweep is required.
- · Background music programming is paused for the dual-running window.
Maintenance posture
- · Line-supervision faults move to the panel — AMC focus shifts from amplifier to speaker line.
- · Annual EN 54-16 / IS 14735 audit is added to the AMC.
Future readiness
- · Voice-evacuation system integrates cleanly into future emergency-response orchestration.
- · Message priority map is the basis for future staged-evacuation patterns.
Sunset guidance
- · Old amplifier racks are removed; the back-of-house space is reclaimed.
- · Background-music programming is restored once drill record is signed off.
/ phased migration
Analogue CCTV → ONVIF-compliant IP surveillance
Migrating a coax-and-DVR analogue estate to an ONVIF-compliant IP camera network with edge analytics and centralised VMS.
Analogue CCTV is a fading technology. Most estates have already begun the migration to IP — but mid-migration estates are common, with hybrid encoders feeding a DVR / NVR that the operator does not love. The clean migration retires the coax progressively, lands ONVIF-compliant IP cameras on a properly-sized PoE++ network, and standardises on a single VMS. The discipline is the camera-by-camera survey: lens, mount, IR, mounting integrity, sight-line. None of these survive the migration without a survey. The other discipline is the network. IP cameras need predictable bandwidth and PoE budget. Our engineering pack on this migration includes the per-camera survey, the bandwidth budget, the storage retention compute (motion-triggered vs continuous), and the VMS retention policy. The post-migration estate is a single ONVIF estate with documented analytics policy.
- Drivers
- performance · obsolescence · integration-gap
- Retrofit
- phased-handover
- Lifecycle
- build · operations · retrofit
- Duration
- 8–14 weeks on a 75-camera estate
Operational caveats
- · Storage retention compute may force a NAS sizing change at cutover.
- · Analytics policy must be agreed and documented before cutover.
Maintenance posture
- · Camera firmware cadence shifts AMC focus from cable to device.
- · VMS health monitoring becomes the primary day-two activity.
Future readiness
- · ONVIF compliance keeps VMS choice open across upgrades.
- · Edge analytics ready, retention policy versioned.
Sunset guidance
- · Old DVR / NVR drives are wiped to DPDPA / IS standard and the units retired.
- · Coax is retained as containment but disconnected at both ends.
· Migration · From legacy to modern