Switching smart home ecosystems without starting over

Start with an inventory

Before you buy anything for the new ecosystem, list every device and note how each one connects. Spend 30 minutes on this and the rest becomes a short list instead of a rebuild.

For each device, write down its name, room, connection type, whether it has the Matter logo and where its setup code is. Take photos of the code stickers.

Check the new ecosystem before you commit

• Controller and hubs. Which of your speakers, displays and streaming boxes act as hubs? See Alexa and Matter, Google Home and Matter hubs and Apple Home hub requirements.
• Supported device types. Apple lists categories such as lights, locks, thermostats, outlets, blinds and several sensors. Google lists 31 supported Matter device types and says other types are not officially supported in Google Home. Compare these lists with your inventory.
• Phones in the household. Apple Home needs iPhones; check that everyone who needs control can use the new app. If you are choosing between platforms, see Alexa vs Google Home and Apple Home vs Google Home.
• Thread. If you have Thread devices, confirm a Thread border router in the new ecosystem. Home Assistant’s documentation notes that each vendor tends to create its own Thread network and that networks with different credentials cannot share devices. See Thread border router explained.

The migration order that keeps things working

1. Set up the new controller first. Add the speaker, display or hub, create the home and invite family members.
2. Move Matter devices by sharing, not removing. In the old app open each Matter device, choose to share it, and add it in the new app with the code. Both ecosystems control it during the transition. Apple notes an accessory already paired with another app can be moved to a Matter-compatible app by selecting the existing accessory; Home Assistant offers the same through its “already in use” option.
3. Link hubs and accounts. Connect your Zigbee or Z-Wave hub and your Wi-Fi device makers’ accounts to the new ecosystem.
4. Recreate rooms and names. Use the same names so voice commands carry over.
5. Rebuild automations, starting with the five you use every day. Routines do not transfer between ecosystems.
6. Run both for one to two weeks. Disable the old automations one at a time as the new ones prove reliable, so two systems do not fight over a device.
7. Retire the old controller last. Before you unplug an old speaker or display that serves as the Thread border router, confirm the new ecosystem has one and that your Thread devices still respond. If they do not, expect to re-pair them.

What does not move

• Routines and automations. Rebuild them in the new app.
• Voice names and shortcuts. Names often carry over if you reuse them, but custom phrases do not.
• Permissions and family members. Invite them again.
• History and energy data. Stays in the old ecosystem; export first if you need it.
• Maker-only features. Special light effects, detailed lock logs or camera features may remain in the maker’s own app.

Removing devices from the old ecosystem

Wait until the new setup is stable. Apple notes that removing an accessory can mean removing it from one service or from all of them, so confirm what the app is about to remove. Do not factory reset a Matter device just because you changed platforms: a reset clears all pairings and sends you back to setup. For devices you retire or sell, remove them from every ecosystem and reset them, and disconnect old devices you no longer use, as the FTC advises. The moving-out checklist covers resets.

Buy only what the move requires

If a device cannot move, replace it with a Matter version rather than another proprietary one. If you only need one hub to bridge Zigbee devices, a bridge costs far less than replacing 20 sensors. Not sure how large the move will be? Start with how to start a smart home to map what you actually use.