# Serial number issue when migrating self-hosted server to other computer

**URL:** <https://community.homey.app/t/serial-number-issue-when-migrating-self-hosted-server-to-other-computer/158065>\
**Category:** Homey Self-Hosted Server\
**Created:** [August 9, 2026, 8:50am UTC](https://community.homey.app/t/serial-number-issue-when-migrating-self-hosted-server-to-other-computer/158065 "2026-08-09T08:50:32Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![janaerts](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/janaerts/32/171507_2.png) [@janaerts](https://community.homey.app/u/janaerts)\
**Post date:** [August 9, 2026, 8:50am UTC](https://community.homey.app/t/serial-number-issue-when-migrating-self-hosted-server-to-other-computer/158065/1 "2026-08-09T08:50:32Z")

</div>

I have homey SHS running on an old fedora machine but want to migrate it to my raspberry pi. Installed homey, copied over the data directory and started it up (using docker). Didn’t realise that there may be an issue with 2 servers running, and got a `Server Invalid Serial Number, uninitialized Homey` on the raspberry pi.  
Stopping the server on the fedora machine does not fix the issue.

Saw afterwards that the homey docs mention “Make sure only one Homey Self-Hosted Server instance is running at a time. Using the same data on multiple instances can lead to unexpected behavior or data issues.” Too late now…

Anyone any idea how I can fix this?

Thank you!

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [August 9, 2026, 9:54am UTC](https://community.homey.app/t/serial-number-issue-when-migrating-self-hosted-server-to-other-computer/158065/2 "2026-08-09T09:54:25Z")

</div>

Have you tried rebooting the Raspberry Pi?

---

<div class="post-metadata">

**Author:** ![janaerts](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/janaerts/32/171507_2.png) [@janaerts](https://community.homey.app/u/janaerts)\
**Post date:** [August 9, 2026, 10:14am UTC](https://community.homey.app/t/serial-number-issue-when-migrating-self-hosted-server-to-other-computer/158065/3 "2026-08-09T10:14:03Z")

</div>

That didn’t help, I’m afraid…

---

<div class="post-metadata">

**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\
**Post date:** [August 9, 2026, 11:10am UTC](https://community.homey.app/t/serial-number-issue-when-migrating-self-hosted-server-to-other-computer/158065/4 "2026-08-09T11:10:07Z")

</div>

Are both SHS instance affected?  
Maybe restore the backup you made and only start one SHS instance.

Have you read [[Modding] Migrating Homey Pro data to Homey SHS](https://community.homey.app/t/modding-migrating-homey-pro-data-to-homey-shs/148852)

It described everything about the sn between HomeyPro and the SHS version.

---

<div class="post-metadata">

**Author:** ![janaerts](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/janaerts/32/171507_2.png) [@janaerts](https://community.homey.app/u/janaerts)\
**Post date:** [August 9, 2026, 7:14pm UTC](https://community.homey.app/t/serial-number-issue-when-migrating-self-hosted-server-to-other-computer/158065/5 "2026-08-09T19:14:49Z")

</div>

Thanks for the link for migration to SHS from Pro. Didn’t help, I think…

I can still go to my original fedora machine and run homey. But after shutting that down (`docker compose down`) and trying to start the installation on the raspberry pi I have the issue again.

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [August 9, 2026, 7:29pm UTC](https://community.homey.app/t/serial-number-issue-when-migrating-self-hosted-server-to-other-computer/158065/6 "2026-08-09T19:29:47Z")

</div>

Maybe the DB of your new installation got corrupted. Have you tried wiping the Raspberry Pi’s SD and reinstalling (and copying the folder from your old server again)?

---

<div class="post-metadata">

**Author:** ![janaerts](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/janaerts/32/171507_2.png) [@janaerts](https://community.homey.app/u/janaerts)\
**Post date:** [August 10, 2026, 6:38am UTC](https://community.homey.app/t/serial-number-issue-when-migrating-self-hosted-server-to-other-computer/158065/7 "2026-08-10T06:38:52Z")

</div>

@smarthomesven Just tried that, but no luck again…

I really hope I don’t need to reinstall from scratch, cancel my current subscription and start a new one… This may be something that needs to be done on the homey server side. Anyone any idea where/how to contact them?

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [August 10, 2026, 6:40am UTC](https://community.homey.app/t/serial-number-issue-when-migrating-self-hosted-server-to-other-computer/158065/8 "2026-08-10T06:40:32Z")

</div>

You can contact Athom support here:

> **[Support | Homey](https://homey.app/en-us/support/)**

Choose “My Homey isn’t listed”, otherwise you won’t be able to create a ticket

---

<div class="post-metadata">

**Author:** ![janaerts](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/janaerts/32/171507_2.png) [@janaerts](https://community.homey.app/u/janaerts)\
**Post date:** [August 10, 2026, 7:22am UTC](https://community.homey.app/t/serial-number-issue-when-migrating-self-hosted-server-to-other-computer/158065/9 "2026-08-10T07:22:10Z")

</div>

Thank you! I tried before, but not “my homey isn’t listed”.
