I am considering upgrading from my Aqara Hub M2 to the new Hub M3. My current setup includes a large number of Zigbee devices, including many safety-related sensors such as water leak detectors.
Before I make the switch, I would like to know if there is any way to migrate all my existing devices and automations from the M2 to the M3 without having to manually reset and re-pair each accessory.
Has anyone successfully performed a hub-to-hub migration in the Aqara ecosystem? Does the Aqara app or any other tool support this kind of seamless transfer? Any tips, experiences, or official guidance would be greatly appreciated.
Thank you in advance.
@stevenmblank Upgrading to the Aqara Hub M3 from the M2 is a great choice, especially with your extensive network of Zigbee devices. The good news is that the Aqara ecosystem does support hub-to-hub migration, which can help you transfer your devices and settings seamlessly.
Here’s how you can do it:
-
Firmware Update: Ensure that both your M2 and M3 hubs are updated to the latest firmware. This is crucial for compatibility during the migration process.
-
Use the Hub Migration Function: The Aqara Home app includes a hub migration feature specifically for this purpose. Navigate to the M3 setting page within the app, select “hub migration,” and then choose your M2 as the “old hub” to be migrated.
-
Migration Process: During the migration, the M3 hub will take over the Zigbee device data, automation, and scene configuration from the M2. This means your Zigbee devices and associated automations should move over to the M3 without needing to be manually re-paired.
-
Retained Configurations: Note that while most configurations will transfer, some automations, especially those configured in third-party apps like Apple Home, may not migrate. Additionally, some features unique to the M2 may not be supported by the M3.
I hope this helps, and I encourage you to share your experience with the migration process with the community! If any issues arise, feel free to reach out for more guidance.
@stevenmblank Great to hear you’re considering the M3 upgrade! Let’s break down the migration process based on official guidance and key points to keep in mind:
First, migration from M2 to M3 is supported via the Aqara app’s hub migration function. To start, go to the M3’s setting page in the Aqara Home app, select “hub migration,” and choose your M2 as the “old hub” . This should allow you to transfer Zigbee devices without manually re-pairing—think of it as “cloning” the M2’s Zigbee network and automations to the M3 .
However, a few things to note:
- Automations and settings: While most automations and scenes will transfer, some may not work if the M3 lacks M2-specific features (e.g., night light functionality or certain third-party app integrations like Apple Home) . These will remain in the app but won’t execute, prompting you to reconfigure them post-migration .
- Firmware and network: Ensure your M2 has the latest firmware before migrating, and both hubs are on the same network .
- Old hub reset: If the M2 is online during migration, it will auto-reset to factory settings; if offline, you’ll need to reset it manually afterward .
Many users have successfully migrated, but experiences can vary based on device count and automation complexity. If you run into issues, double-check the app instructions or ensure both hubs are connected properly.
Feel free to share your experience once you try it—your insights could help others! If you hit a snag, the community might have additional tips, and you can always refer to the app’s step-by-step guide.
Hope this helps—happy migrating!
@stevenmblank Great question! Migrating from the Aqara Hub M2 to M3 is indeed supported, and you can avoid manually re-pairing devices. Here’s what you need to know based on official guidance and common practices:
Migration Feasibility
The [Aqara M3 Hub](https://forum.aqara.com/s?product=aqara-smart-hub-[m3](https://forum.aqara.com/s?product=aqara-smart-hub-m3)) supports migration from the M2 Hub via the “hub migration” function in the Aqara Home app. This allows the M3 to “clone” the M2’s Zigbee device data, automations, and scene configurations, meaning your Zigbee devices (like water leak detectors) will automatically join the M3’s network without re-pairing .
Key Considerations
- Firmware Update: Ensure your M2 Hub has the latest firmware before migrating .
- Automation Retention: Most automations will transfer, but automations set up in third-party apps (e.g., Apple Home) may not be retained .
- Functionality Differences: Some M2 features (e.g., night light settings) might be lost if the M3 doesn’t support them. The retained configurations will be the “intersection” of both hubs’ capabilities .
- Network & Process: Both hubs should be on the same network, and you’ll need to follow the app’s step-by-step instructions carefully .
Post-Migration
After migration, the old M2 Hub may need a factory reset (it will auto-reset if online during migration; manually reset if offline) .
If you run into issues, double-check the network connection and firmware versions. Many users have successfully migrated, so with proper preparation, the transition should be smooth.
Hope this helps—feel free to share your experience once you try it! 