Move a smart home without turning migration day into demolition day.

Migration begins with evidence, not factory resets

An existing system contains useful clues even when it is frustrating. Model labels, app assignments, network addresses and current behaviour show which devices can be integrated, recommissioned or safely left alone. Resetting everything first can destroy that evidence and remove working control before the replacement path is ready.

We first identify what each room depends on and who owns the relevant accounts. Access, essential lighting and climate controls receive a different migration sequence from a decorative lamp or non-critical sensor.

Open does not have to mean all-new

Some Zigbee devices can move to a suitable coordinator. Some vendor hubs can remain as local bridges. Cloud-only Wi-Fi products may stay temporarily or be replaced when their risk and value justify it. Conventional loads can often remain while only the controlling module changes.

The useful target is a supportable home with clear ownership, not a collection of products that all carry the same protocol badge.

• Keep sound devices that still fit the ownership goal
• Bridge stable systems where the interface is documented
• Re-pair compatible devices only after the new mesh is ready
• Replace unsupported dependencies in a planned order

The endpoint still needs a maintainer

Home Assistant can reduce platform lock-in and consolidate control, but it introduces a host, backups and software ownership. A migration is incomplete if the new system depends on another personal account or an undocumented computer under the television.

The handover records where services run, how they recover, which integrations remain cloud-dependent and who is responsible for future changes.