Moving from SmartThings to Home Assistant is exciting and a little nerve-racking. Home Assistant gives you local control, deeper customisation, and a huge community, but the fear is always the same: will you have to rebuild years of routines, scenes, and clever little automations from scratch, one by one, late into the night?
The reassuring answer is no — not if you migrate in the right order. You cannot press one button and import every SmartThings routine perfectly, but you can run both systems side by side, move devices gradually, and recreate your best automations with a clear plan. This guide shows you how to migrate automations from SmartThings to Home Assistant without rebuilding everything in a panic.
Quick Answer
To migrate from SmartThings to Home Assistant without rebuilding everything, first list every SmartThings routine, scene, and device, then set up Home Assistant alongside SmartThings and connect the two so you can see and control SmartThings devices from Home Assistant while you transition. Move Zigbee and Z-Wave devices in small groups, rebuild your top routines first using Home Assistant automations, scenes, and blueprints, and test each one before deleting the SmartThings version. Keep SmartThings running as a fallback until every critical automation has worked reliably in Home Assistant for at least a week.
Why a Side-by-Side Migration Works Best
The biggest mistake people make is unplugging SmartThings on day one. A calmer approach treats the migration like moving house: you do not burn the old house down before the new one has heating. Home Assistant can run on a Raspberry Pi, a small mini PC, or Home Assistant Green or Yellow hardware, while your SmartThings hub stays exactly where it is.
During the overlap period you can:
- Confirm Home Assistant is stable on your network before trusting it with locks and lights.
- Learn the Home Assistant way of building automations without pressure.
- Move devices room by room instead of resetting fifty devices in one exhausting weekend.
- Keep family life normal — lights, heating, and alerts keep working in SmartThings until their replacements are proven.
Home Assistant’s official automation documentation explains triggers, conditions, and actions in detail, and it is worth keeping open in a tab throughout your migration.
Step 1: Inventory Everything in SmartThings
You cannot migrate what you cannot see. Many homes have routines created years ago that nobody remembers until they stop working.
- Open the SmartThings app and list every device, grouped by room. Note which are Zigbee, Z-Wave, Wi-Fi, or cloud-connected.
- Open Automations and Scenes and write down each routine: its trigger, its conditions such as time or who is home, and its actions.
- Mark each routine as critical, useful, or forgotten. Critical means security, heating, essential lighting, and leak or smoke alerts.
- Note special cases: automations that use a virtual switch, a SmartThings-specific feature, or a family member’s phone presence.
- Export or screenshot device names and room assignments. Matching names in Home Assistant will make the switch feel familiar for everyone at home.
This inventory becomes your checklist. Tick routines off as they go live in Home Assistant, and you will always know what remains. If you are also rethinking your network for the new hub, our guide to setting up a smart home hub for beginners covers placement, Ethernet, and backup basics that apply neatly to a Home Assistant setup.
Step 2: Set Up Home Assistant and Link SmartThings
- Install Home Assistant, finish the onboarding, set your home location and time zone, and create user accounts for the household.
- Connect Home Assistant to your router with Ethernet if possible, and give it a reserved IP address so its address never changes.
- Add the SmartThings integration in Home Assistant by going to Settings, Devices and Services, and Add Integration. Follow the sign-in steps to link your Samsung account.
- Confirm your SmartThings lights, sensors, and switches appear as entities in Home Assistant and respond when toggled.
- Install the Home Assistant companion app on your phone and enable location and sensor access if you plan to use presence automations.
The SmartThings support pages at SmartThings Support are helpful during this stage if a device is missing or a location will not link, because the fault is sometimes a device that belongs to a different SmartThings location.
Step 3: Understand How Automations Translate
SmartThings Routines and Home Assistant automations share the same logic — when this happens, if these conditions are true, do these actions — but the building blocks have different names.
- Trigger: The event that starts it, such as motion, a door opening, sunset, or a phone arriving home.
- Condition: A check that must pass, such as only after 7 pm or only when nobody is in holiday mode.
- Action: What happens, such as turning on lights, locking a door, or sending a notification.
- Scenes: A saved snapshot of device states in both systems. Recreate your SmartThings scenes early, because many automations simply call a scene.
- Helpers: Home Assistant helpers, like input booleans and timers, replace many SmartThings virtual switches. Recreate those first too.
Look for blueprints before building from zero. Blueprints are ready-made automation templates shared by the community for common jobs like motion lighting. Using a blueprint for five identical hallway automations is far faster than hand-building each one, and it is one of the main reasons the migration feels lighter than expected.
Step 4: Rebuild in Priority Order
- Start with scenes and helpers, because your automations depend on them.
- Rebuild your top five critical automations in Home Assistant, but leave the SmartThings versions paused rather than deleted.
- Test each automation deliberately: trigger the sensor, open the door, or use the Run Actions button and check the trace for errors.
- Once an automation passes, turn off the SmartThings version so the two systems do not fight or double-trigger lights.
- Work down your list room by room — useful autom next, novelty automations last.
- Recreate dashboards only after the automations work. A pretty dashboard over broken logic helps nobody.
Step 5: Move Zigbee and Z-Wave Devices Gradually
Devices controlled through the SmartThings cloud link can stay linked for a while, but Zigbee and Z-Wave devices can only belong to one hub at a time. Moving them is the point of no return for that device, so go slowly.
- Add a Zigbee or Z-Wave coordinator to Home Assistant if your setup needs one, and place it away from USB 3 ports and Wi-Fi routers using a short extension cable.
- Pick one room. Exclude or reset its devices in SmartThings, then pair them to Home Assistant.
- Rename each device exactly as before and assign it to the same room in Home Assistant.
- Fix any automations that used that device and re-test them the same day.
- Leave mains-powered devices, like smart plugs and in-wall switches, to act as repeaters early in the move so your new mesh network is strong.
Common Mistakes to Avoid
- Deleting SmartThings routines too early. Pause them first. Deletion removes your only reference for how the original logic worked.
- Renaming everything at once. New names sound tidy, but they break voice commands and confuse family members. Keep old names during migration.
- Moving battery sensors first. Start with mains-powered devices to build a strong mesh, then add battery devices.
- Skipping backups. Take a Home Assistant backup after every successful stage so you can roll back without starting over.
- Running both systems on the same automation. Two hubs firing the same lights causes flicker, loops, and mystery behaviour. One owner per automation.
Step 6: Cut Over and Decommission Carefully
When your checklist shows every critical and useful automation running in Home Assistant, live with it for a full week. Walk through a normal weekday, a late night, and a time when the house is empty. Only then remove the SmartThings integration from Home Assistant, factory-reset devices you no longer need on SmartThings, and decide whether to keep the SmartThings hub as a spare or retire it. Keep your inventory list — it becomes the first draft of documentation for your new system.
Conclusion
Migrating from SmartThings to Home Assistant does not have to mean rebuilding everything in one stressful leap. Inventory first, run both systems together, recreate scenes and helpers, rebuild automations in priority order, and move radios room by room. With testing at each stage and SmartThings kept as a safety net until the end, you arrive at a faster, more local, more flexible smart home — with your best routines intact and your household still speaking to you.
Frequently Asked Questions
Can Home Assistant import my SmartThings routines automatically?
Not fully. There is no perfect one-click import for routine logic. The SmartThings integration brings devices into Home Assistant, but automations, scenes, and helpers should be recreated manually or with blueprints, which is why an inventory matters.
Will my Zigbee devices work on both hubs at the same time?
No. A Zigbee or Z-Wave device can be paired to only one hub at a time. You must remove or reset it from SmartThings before pairing it to Home Assistant, so move devices in small, planned groups.
How long does a typical migration take?
For a medium home, most people spread it over one to three weekends. A written inventory, a side-by-side setup, and rebuilding critical automations first make it much faster than starting blind.
Do I need to buy extra hardware for Home Assistant?
You need something to run Home Assistant on, and possibly a Zigbee or Z-Wave USB coordinator if your hardware does not include those radios. Many Wi-Fi and cloud devices need no extra hardware at all.
What should I do if an automation behaves differently in Home Assistant?
Open the automation trace in Home Assistant to see which trigger fired and which condition stopped or passed. Compare it line by line with your SmartThings inventory notes and adjust one step at a time.


Leave a Reply