# Port Homey Pro 2023 to SHS instead of migration

**URL:** <https://community.homey.app/t/port-homey-pro-2023-to-shs-instead-of-migration/157712>\
**Category:** Homey Self-Hosted Server\
**Created:** [July 29, 2026, 2:13pm UTC](https://community.homey.app/t/port-homey-pro-2023-to-shs-instead-of-migration/157712 "2026-07-29T14:13:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ruurd\_van\_der\_Noord](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ruurd_van_der_noord/32/71093_2.png) [@Ruurd\_van\_der\_Noord](https://community.homey.app/u/Ruurd_van_der_Noord)\
**Post date:** [July 29, 2026, 2:13pm UTC](https://community.homey.app/t/port-homey-pro-2023-to-shs-instead-of-migration/157712/1 "2026-07-29T14:13:34Z")

</div>

I can understand the migration approach, but for me it’s not ideal. I wanted to reuse my flows, scripts, devices, and more, but not as an exact copy. That’s why I built a C# batch replacement tool to map old Homey Pro 2023 IDs to new Pi 5 SHS IDs.

The scripts on the Pro 2023 and the matching scripts on the Pi 5 SHS generate the ID lists needed by this tool. Together with Homey’s Flow Export option, it can be used to create new flows. Variables and devices on the Pi 5 SHS need to be created in advance with a script to obtain the new IDs.

It took a day’s work, but I’m happy with the result. Anyone interested?