Switching from one smart home controller to another can be smooth if you understand how Zigbee stores pairings and network trust.
This guide explains how to move Zigbee devices to new hub, what to reset first, and how to avoid the most common migration mistakes.
What Zigbee Migration Actually Means
Zigbee is a low-power mesh protocol used by brands like Philips Hue, Aqara, Sonoff, IKEA, and many others.
When you move devices to a new hub, you are not just changing an app; you are moving each device from one Zigbee coordinator to another, which usually requires a rejoin or re-pair process.
In practical terms, the old hub acts as the current network owner, and the new hub must become the trusted coordinator.
Some devices can remember their previous network, but most consumer Zigbee products are easiest to transfer by removing them from the old network and pairing them again on the new one.
Before You Start: Check Compatibility
Not every hub supports the same Zigbee behavior, device types, or pairing workflow.
Before you begin, confirm that the new hub supports your specific bulbs, sensors, switches, plugs, and locks.
- Confirm Zigbee version support: Most hubs support Zigbee 3.0, but some older devices rely on legacy profiles.
- Review ecosystem limits: Apple Home, Amazon Alexa, Google Home, SmartThings, Home Assistant, and Hubitat each handle Zigbee devices differently.
- Check supported device classes: Some hubs support lighting and sensors but not thermostats, buttons, or security devices.
- Update the new hub first: Install the latest firmware before adding devices.
If your new hub includes migration tools, export options, or device backups, read that documentation first.
Native transfer support is uncommon, but when available it can save time.
Back Up Your Current Setup
Before removing anything, document your current smart home configuration.
Zigbee migration often involves rebuilding automations, room assignments, and device names after the move.
- Take screenshots of device names and rooms.
- Record automations, scenes, and trigger conditions.
- Note any device-specific settings such as brightness defaults or power-on behavior.
- List battery devices separately so you can prioritize them during re-pairing.
If your old hub also controls other radios such as Wi-Fi, Thread, or Bluetooth, separate those devices from your Zigbee inventory so you do not reset the wrong equipment.
How to Move Zigbee Devices to a New Hub
The safest method is to remove each device from the old hub, reset it if necessary, and pair it to the new hub one at a time.
This reduces confusion and helps the new hub build a clean mesh network from the start.
1. Move the Hub First
Power up and fully configure the new hub before touching any devices.
Give it a stable internet connection, complete firmware updates, and set up your home, rooms, and user accounts.
If the hub has a Zigbee channel setting, choose it carefully.
In dense apartment environments, a different channel can reduce interference from Wi-Fi networks operating on overlapping frequencies.
2. Remove Devices From the Old Hub
Whenever possible, use the old hub’s app or interface to delete or unpair each device.
This tells the coordinator to release the device and reduces the chance of duplicate entries later.
Some battery devices, especially sensors, may not offer a clean remove option once they have gone offline.
In those cases, a factory reset is the next step.
3. Factory Reset the Device if Needed
Most Zigbee devices need a hardware reset or a long-button press to enter pairing mode.
The exact procedure varies by manufacturer, so check the model instructions before you begin.
- Bulbs: Often require on/off cycles or a power toggle sequence.
- Plugs: Usually reset with a button hold or repeated power cycling.
- Sensors: Commonly reset with a pinhole button or battery removal plus a press.
- Switches and remotes: May need a long press until an LED blinks.
If a device is stubborn, give it a full reset rather than repeatedly trying to pair it while still linked to the old network.
4. Pair to the New Hub One Device at a Time
Put the new hub into pairing mode and add one device at a time.
Keeping the process sequential makes troubleshooting easier and helps you identify weak signals or incompatible devices quickly.
For mains-powered Zigbee routers such as plugs, bulbs, and in-wall modules, pair a few of them early because they help extend the mesh.
That improved routing can make it easier to add battery-powered sensors later.
Order Matters: Build the Mesh in the Right Sequence
Zigbee networks rely on routers and end devices.
Routers are usually mains-powered devices that relay traffic, while end devices are typically battery-powered and do not forward messages for others.
A practical migration order is:
- Hub and software setup
- Always-on routers such as smart plugs and bulbs
- Room-critical devices such as switches and dimmers
- Battery sensors, contact sensors, and motion detectors
- Specialty devices such as locks or thermostats
This sequence helps the mesh stabilize before the most sensitive devices join.
If your home is large, place the new hub near the center of the space during setup to improve initial pairing success.
What If a Device Will Not Join?
Pairing failures are usually caused by one of a few issues: the device was not fully reset, the hub is too far away, interference is high, or the device is still associated with another Zigbee coordinator.
- Retry the reset: Many devices only enter pairing mode for a short window.
- Move the hub closer: Temporary proximity can help during initial joining.
- Reduce interference: Keep the hub away from Wi-Fi routers, USB 3.0 hubs, and metal enclosures.
- Use a known-good router: Pair a nearby Zigbee plug or bulb first to strengthen the mesh.
If a device was previously part of another ecosystem, a full factory reset is often the fastest path to success.
Some devices also retain a “ghost” record for a short time after removal, so waiting a few minutes before re-pairing can help.
How to Keep Automations Working After the Move
Device migration is only half the job; automations and scenes usually need to be rebuilt or re-linked.
Names may not carry over exactly, especially if you are moving between ecosystems like SmartThings and Home Assistant.
To minimize disruption:
- Use consistent device names before and after the move.
- Recreate key automations first, such as lighting schedules and motion triggers.
- Test device states, such as on/off, dimming, temperature readings, and battery status.
- Verify cloud integrations with Alexa, Google Home, or Apple Home if you depend on voice control.
For advanced platforms like Home Assistant, Zigbee2MQTT, or ZHA, migration may involve re-adding entities, repairing device triggers, and restoring dashboards after the coordinator change.
Special Cases: Hue, Aqara, and Locks
Some brands deserve special attention because they do not behave like generic Zigbee devices.
Philips Hue
Hue bulbs and accessories often work best with the Hue Bridge.
If you move them to another hub, you may lose some brand-specific effects or dimming behavior.
Check whether the new hub supports Hue lighting features before migrating.
Aqara
Aqara sensors are known for strong battery life but can be sensitive to hub compatibility.
Some models pair more reliably with Aqara hubs than with generic coordinators, especially when using older firmware.
Smart Locks and Security Devices
Locks and security-related devices should be migrated carefully.
Confirm that the new hub supports secure pairing, local control, and access logs before you reset anything.
If the lock is part of a monitored security system, schedule the migration during a low-risk period.
Common Mistakes to Avoid
Many migration problems come from skipping the preparation phase.
Avoid these errors to save time.
- Resetting every device before documenting the old setup.
- Adding battery devices before establishing a stable Zigbee mesh.
- Assuming all Zigbee hubs support the same devices.
- Using the same name for multiple devices during setup.
- Ignoring firmware updates on the new hub and the devices themselves.
A careful, device-by-device approach is slower at first, but it is usually faster overall because it reduces failed joins and automation cleanup later.
When You Can Skip a Full Reset
In some enterprise or advanced DIY cases, it may be possible to transfer Zigbee network data directly between coordinators using a backup and restore process.
This is more common in Home Assistant, Zigbee2MQTT, and some advanced coordinator adapters, where the network key and device database can be preserved.
Even then, compatibility is not guaranteed.
If you are moving between branded consumer hubs, assume you will need to re-pair the devices unless the manufacturer explicitly documents migration support.
Final Setup Checks
After all devices are added, verify the basics:
- Each device appears in the correct room.
- Motion, contact, and temperature sensors report correctly.
- Switches and buttons trigger the intended actions.
- Battery levels are visible where supported.
- Automations fire at the right time and in the right order.
Walk through the home and test devices at the edge of the mesh, since those are the most likely to reveal signal or routing problems after a hub change.
