# Trouble with migration a RPi ic880A GW to V3

**URL:** <https://www.thethingsnetwork.org/forum/t/trouble-with-migration-a-rpi-ic880a-gw-to-v3/44373>\
**Category:** Migrating Gateways to V3\
**Created:** [February 16, 2021, 4:38pm UTC](https://www.thethingsnetwork.org/forum/t/trouble-with-migration-a-rpi-ic880a-gw-to-v3/44373 "2021-02-16T16:38:14Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![pe1mew](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/pe1mew/32/48520_2.png) [@pe1mew](https://www.thethingsnetwork.org/forum/u/pe1mew)\
**Post date:** [February 20, 2021, 8:37am UTC](https://www.thethingsnetwork.org/forum/t/trouble-with-migration-a-rpi-ic880a-gw-to-v3/44373/15 "2021-02-20T08:37:40Z")

</div>

Hi all. The solution i propose will not answer the question for your situation but will add more flexibility to your gateway trough remote management as well as a solution to connect the gateway to both V2 and V3.

Read this thread and install the balena solution @jpmeijers created: [Howto connect a Balena gateway to V2 and V3 - #5 by kersing](https://www.thethingsnetwork.org/forum/t/howto-connect-a-balena-gateway-to-v2-and-v3/44542/5)

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/trouble-with-migration-a-rpi-ic880a-gw-to-v3/44373)._