# Migrating Shari-PiHat

**URL:** <https://community.allstarlink.org/t/migrating-shari-pihat/25033>\
**Category:** AllStarLink\
**Tags:** new-users\
**Created:** [October 1, 2026, 4:49am UTC](https://community.allstarlink.org/t/migrating-shari-pihat/25033 "2026-10-01T04:49:27Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![K0AAI](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/b2d939/32.png) [@K0AAI](https://community.allstarlink.org/u/K0AAI)\
**Post date:** [October 1, 2026, 4:49am UTC](https://community.allstarlink.org/t/migrating-shari-pihat/25033/1 "2026-10-01T04:49:27Z")

</div>

I will admit I am pretty new to Allstar and barely literate with linux. I purchased a Shari Pi Hat which was installed on a raspberry pi 4. I was further able to get it imaged and running well with the HamVoip image. I would like to migrate the node over to the Debian based image recommended in the Allstar manual but it seems as the though the instructions in the manual are a little vague after a certain point.

Is there a way I could save the needed settings/files from the HamVoip image (which is working), image the new debian based image and then transfer them those files into the Debian based image with a fully functioning node at the end without having to fight my way through all the settings again ? I was considering using an external drive as the storage device. Is there a detailed set of instructions to do this that a complete noob could follow?

I am almost certain variations of this topic have come up before, and fairly sure it would work. I just need to figure out how to do it.

---

<div class="post-metadata">

**Author:** ![KK6RQ](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kk6rq/32/3511_2.png) [@KK6RQ](https://community.allstarlink.org/u/KK6RQ)\
**Post date:** [October 1, 2026, 5:25am UTC](https://community.allstarlink.org/t/migrating-shari-pihat/25033/2 "2026-10-01T05:25:45Z")

</div>

There's detailed, step-by-step instructions for installing ASL3 on several variants of Shari PiHat in the files section of their [groups.io](http://groups.io) group.  
I have to say, his instructions are among the best I've ever seen.  
Someone else could comment on whether the audio level settings in HamVoIP can transfer to ASL; I have no idea, but I would just follow those directions and start from scratch; there's really not that many variables. You shouldn't have to reprogram the SA818; pretty sure that part's locked in.

And obviously keep the HV SD card intact until ASL is up and running, so you can revert quickly if you get stuck or hung up.

---

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [October 1, 2026, 12:38pm UTC](https://community.allstarlink.org/t/migrating-shari-pihat/25033/3 "2026-10-01T12:38:06Z")

</div>

> [@K0AAI](#):
>
> Is there a way I could save the needed settings/files from the HamVoip image (which is working), image the new debian based image and then transfer them those files into the Debian based image with a fully functioning node at the end without having to fight my way through all the settings again ?

No. HamVOIP's legacy configuration isn't importable into modern Asterisk/app\_rpt. Start clean and use the very user-friendly `asl-menu` script to set it up. You can pick all the SHARI configs right out of the menu and it'll "just work".