# Migrate from Hubitat to Homey Bridge (Z-Wave Devices)

**URL:** <https://community.homey.app/t/migrate-from-hubitat-to-homey-bridge-z-wave-devices/61432>\
**Category:** Questions & Help\
**Tags:** z-wave, homey-bridge\
**Created:** [March 7, 2022, 3:14pm UTC](https://community.homey.app/t/migrate-from-hubitat-to-homey-bridge-z-wave-devices/61432 "2022-03-07T15:14:47Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joseph\_Betty](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joseph_betty/32/52660_2.png) [@Joseph\_Betty](https://community.homey.app/u/Joseph_Betty)\
**Post date:** [March 7, 2022, 3:14pm UTC](https://community.homey.app/t/migrate-from-hubitat-to-homey-bridge-z-wave-devices/61432/1 "2022-03-07T15:14:47Z")

</div>

Hello! New user to Homey here. I have the Homey Bridge associated with my new Home definition. I am migrating from a very unstable Hubitat Evolution device containing all of my Z-Wave devices (it’s the current Master Controller) to Homey. I would like to use an automated Z-Wave transfer/re-assignment method for all of my devices rather than having to reset and re-pair each device manually (painful). I know how to initiate the transfer in Hubitat, but I don’t see an equivalent receive/master re-assignment capability in the Homey android app to essentially transfer my decides to my new Homey Bridge. I would really appreciate any help you can provide, even if only to point me to knowledge information that I may have overlooked.  
Thank you in advance!

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [March 7, 2022, 3:33pm UTC](https://community.homey.app/t/migrate-from-hubitat-to-homey-bridge-z-wave-devices/61432/2 "2022-03-07T15:33:55Z")

</div>

AFAIK, Homey doesn’t have such a function. So re-pairing is the only way.

---

<div class="post-metadata">

**Author:** ![Joseph\_Betty](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joseph_betty/32/52660_2.png) [@Joseph\_Betty](https://community.homey.app/u/Joseph_Betty)\
**Post date:** [March 7, 2022, 4:23pm UTC](https://community.homey.app/t/migrate-from-hubitat-to-homey-bridge-z-wave-devices/61432/3 "2022-03-07T16:23:41Z")

</div>

That’s disappointing. Does Homey assume its target market is only new home automation consumers? People with a large number of z-wave devices will find this very tedious and potentially a barrier to considering the technology. Z-Wave master/primary re-assignment is a valuable tool during migration. ☹

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [March 7, 2022, 4:34pm UTC](https://community.homey.app/t/migrate-from-hubitat-to-homey-bridge-z-wave-devices/61432/4 "2022-03-07T16:34:58Z")

</div>

> [@Joseph\_Betty](#):
>
> Does Homey assume its target market is only new home automation consumers?

No. But from what I’m reading about controller re-assignment, it’s far from standardized within the Z-Wave protocol, and fraught with issues (especially cross-brand). So perhaps that’s the answer why Homey doesn’t support it.