Agree. Its a bloody pain in the ar*e. Why not make
A Migrate option?
Also its just poor that the Homey Link is so crap. Ive moved tons of devices over but then bridged many with Homey Link. My “home” treats them as 2 places so there is now no overview of temp/lights on/ activity because homey link wont support that!
Basically the idea of SHS is to rebuild and burn your hold homey pro because its pretty worthless now!
Such a shame.
Why it cant all just be one home and all work in one page.
Homey link i thought was the way to go. This is too a pain to use. Keeps crashing, slow to load devices in and the HP2023 and the SHS are ‘seen’ as 2 different locations.
There is me thinking it would “link” them. Nope. No device overview or presence or anything.
Really poor implementation
Its best off painfully migrating everything over to SHS and use your old homey as a mega over-priced antenna
This is a great step forwards dot get me wrong, but They can do much better - other apps already link multiple hubs into one home.
i imagine the cogs will turn slow with this one!
EDIT
seems to be each time i run the link discovery its finding / repairing devices. Most of my devices are now over and ive even now started to see room status/temp etc which is really nice.
Yes flow migration/link would be amazing now
A export for flows at least would be nice
Why wouldn’t SHS servers support online backups like HP23? I was hoping that I could take a HP23 backup and do a restore to the SHS. Isn’t the HP23 and SHS code base essentially the same? Surely the development team didn’t code an entirely new server, that would be crazy, right? Help me understand, please.
Discussed a few posts back 
Wow big thanks this will make a big difference for my external light flow
What do you mean? I cannot restore my paid backup for Homey 2016 to Homey-SHS?
I have to manually migrate from Homey 2016 and my advanced flows etc to Homey-SHS? 
Nah… right?
This homey bot in the support section gave me the answer I wanted. It’s not true, but it is what I wanted.
”i want to move my zigbee devices from homey 2016 to homey-shs.”
Homey
Got it — you want to move your Zigbee devices from a Homey Pro (2016–2019) to Homey Self-Hosted Server (Homey SHS).
What I understand so far:
Source: Homey Pro (2016–2019)
Destination: Homey Self-Hosted Server (running on your own hardware)
Goal: Migrate Zigbee devices
Based on your setup, here are your options:
Option A — Full migration via backup/restore (if you’ll use Homey Pro hardware or SHS + Homey Bridge for Zigbee)
Create a backup on the old Homey: Homey app > More (…) > Backups > Create a backup.
Power off the old Homey after the backup to avoid Zigbee/Z-Wave mesh conflicts.
Set up your Homey SHS and sign in. During setup, choose to restore from backup.
After restore, log back in to third-party services (Google Assistant, Amazon Alexa, IFTTT).
Repair Zigbee devices: Some Zigbee devices will need a repair to re-bind to the new coordinator.
Mobile app: Device > Settings > Maintenance > Try to Repair
Web app (my.homey.app): Right-click device tile > Repair
Option B — Re-pair devices directly to SHS using Zigbee via Homey Bridge
Install and set up Homey SHS and add a Homey Bridge to provide Zigbee.
On the old Homey, remove or power it off to avoid mesh conflicts.
Reset each Zigbee device (typically a specific power cycle or button sequence) and add it as a new device in SHS.
Recreate any needed Flows. This is clean and avoids any leftover mesh issues.
Before i make a silly time consuming mistake, if i want to add new lights to Hue or Ikea devices or whatever and i want them to bridge via matter to Homey but to my SHS i need to make a new Matter link.
But does that means all devices will link and keep auto discovering?
So ill have duplicate of all my matter devices.
Im almost better starting all over again or can i change this? TIA
If so, supports the need that Homey account should be the “home” regardless of how many hubs or set ups you have.
Hello,
I would also prefer the option to migrate from the HP23 to the HSHS and then continue using the HP23 as a bridge — especially considering that you are charging 149 euros for the license.
The major advantage is that existing hardware, such as a NAS, can continue to be used and often provides even better performance in the long run.
You should also consider enabling the integration of other bridges like Philips Hue, Aqara, or Tado. This would significantly expand the Homey ecosystem and turn it into a truly comprehensive smart‑home platform.
Uwe
Unless I’ve missed something, Uwe:
why wouldn’t it be enabled? If it’s suitable for a Pro, and if it connects per (W)LAN, it should work?
This…And reading all the experiences so far. I think i’ll buy a new Raspberry Pi Compute Module 4 and upgrade my homey pro 2023 myself. It’ll also cost me a €150,- just like the SHS option but i won’t need to get into the black hole with setting up all flows and device (id’s) again.
975 flows overhere😲
I have migrate this weekend (by hand) from my old 2016 1st gen. version to the SHS server with a bridge.
Yes you have right why not a migrate tool, but the setup of the H2016 and the SHS(icw Bridge) is very different in communication.
But thinkg on that, all so a good start to clean up every thing do somthings smater then in the past, I have made from the flows a lot screen shots (and a lot off them or the same only other device’s)
At first I started a dedicated VM on my server (running all ready) and installed Homey SHS. Then installed every app what is only needed for inside and outside communicatie over TCP (IP, Wifi) and out side.
Then I installed my new Homey bridge, and let it run. after that I started to (re)install/connected true the whole house power sockets and other direct connected device (build in dimmers ect) to build on a decedent way my new zigbee network. And let it run for a night.
The other day i started with help off son to reset an reconnect every other zigbee or z wave device’s, yes some times a work but all fresh and on the right place connected to the mesh networks.
totally installed 18 Powersockets, 25 build dimmers and switches, 35 sensors (door/window, IR, motion, temp). all most all or Zigbee. And now some rest to make the mesh stable.
And I started to program the flows, and with help off share off the flows to build them again. A lot is easy then I build in the past so flow become smaller and compact.
So over the last days all necessary and easy to build flows or running all ready, and with the few free days what is coming the rest will be build.
After 9 years off using the homey 2016 1st generation, the new SHS is coming live (will this all so run for 9 years)
Every one a Merry Christmas With Homey SHS
To be honest; my experience was identical.
I did the export thing for the flows (with the ALT button in the menu), and made screenshots. It was pretty easy to recreate and review everything. Added new insights to old flows. The main reason why I accepted this, is because with SHS everything is lightning fast. But, maybe this is different for others, because like you, I came from Homey 2016 to Homey-SHS.
Still have issue with some things, but I would still recommend people using Homey-SHS.
That said; it should have had a migration option.
12 posts were split to a new topic: [Modding] Migrating Homey Pro data to Homey SHS
This deserves a own topic!
Moved to:
As that needs jailbreaking and non standard actions let’s keep the two options as manual migration (This original topic) and the Advanced user Jailbreak (see link) discussed separately.
