# Can't migrate applications from V2 to V3 with ttn-lw-migrate tool

**URL:** <https://www.thethingsnetwork.org/forum/t/cant-migrate-applications-from-v2-to-v3-with-ttn-lw-migrate-tool/51169>\
**Category:** Migrating Devices to V3\
**Created:** [August 31, 2021, 8:30am UTC](https://www.thethingsnetwork.org/forum/t/cant-migrate-applications-from-v2-to-v3-with-ttn-lw-migrate-tool/51169 "2021-08-31T08:30:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jfauger](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/jfauger/32/37736_2.png) [@jfauger](https://www.thethingsnetwork.org/forum/u/jfauger)\
**Post date:** [August 31, 2021, 8:30am UTC](https://www.thethingsnetwork.org/forum/t/cant-migrate-applications-from-v2-to-v3-with-ttn-lw-migrate-tool/51169/1 "2021-08-31T08:30:08Z")

</div>

I try to export my devices from V2 application with ttn-lw-migrate.exe application

`ttn-lw-migrate.exe application --source ttnv2 --ttnv2.with-session=false --verbose > devices.json`

but nothing happens, the application waits forever

```
 DEBUG [core]parsed scheme: ""
 DEBUG [core]scheme "" not registered, fallback to default scheme
 DEBUG [core]ccResolverWrapper: sending update to cc: {[{discovery.thethings.network:1900 <nil> 0 <nil>}] <nil> <nil>}
 DEBUG [core]ClientConn switching balancer to "pick_first"
 DEBUG [core]Channel switches to new LB policy "pick_first"
 DEBUG [core]Subchannel Connectivity change to CONNECTING
 DEBUG [core]Subchannel picks a new address "discovery.thethings.network:1900" to connect
 DEBUG [core]pickfirstBalancer: UpdateSubConnState: 0xc000847c10, {CONNECTING <nil>}
 DEBUG [core]Channel Connectivity change to CONNECTING
 DEBUG [core]Subchannel Connectivity change to READY
 DEBUG [core]pickfirstBalancer: UpdateSubConnState: 0xc000847c10, {READY <nil>}
 DEBUG [core]Channel Connectivity change to READY
 DEBUG rpc-client: call done auth-type=key duration=436.1557ms method=/discovery.Discovery/GetByAppID service-name=ttn-lw-migrate service-version=2.x.x
 DEBUG [core]parsed scheme: ""
 DEBUG [core]scheme "" not registered, fallback to default scheme
 DEBUG [core]ccResolverWrapper: sending update to cc: {[{eu.thethings.network:1904 <nil> 0 <nil>}] <nil> <nil>}
 DEBUG [core]ClientConn switching balancer to "pick_first"
 DEBUG [core]Channel switches to new LB policy "pick_first"
 DEBUG [core]Subchannel Connectivity change to CONNECTING
 DEBUG [core]Subchannel picks a new address "eu.thethings.network:1904" to connect
 DEBUG [core]pickfirstBalancer: UpdateSubConnState: 0xc0000f2f10, {CONNECTING <nil>}
 DEBUG [core]Channel Connectivity change to CONNECTING
 DEBUG [core]Subchannel Connectivity change to READY
 DEBUG [core]pickfirstBalancer: UpdateSubConnState: 0xc0000f2f10, {READY <nil>}
 DEBUG [core]Channel Connectivity change to READY
 DEBUG [core]Subchannel Connectivity change to CONNECTING
 DEBUG [transport]transport: loopyWriter.run returning. connection error: desc = "transport is closing"
 DEBUG [core]pickfirstBalancer: UpdateSubConnState: 0xc0000f2f10, {CONNECTING <nil>}
 DEBUG [core]Channel Connectivity change to CONNECTING
 DEBUG [core]Subchannel picks a new address "eu.thethings.network:1904" to connect
 DEBUG [core]Subchannel Connectivity change to READY
 DEBUG [core]pickfirstBalancer: UpdateSubConnState: 0xc0000f2f10, {READY <nil>}
 DEBUG [core]Channel Connectivity change to READY
 DEBUG [core]Subchannel Connectivity change to CONNECTING
 DEBUG [transport]transport: loopyWriter.run returning. connection error: desc = "transport is closing"
 DEBUG [core]pickfirstBalancer: UpdateSubConnState: 0xc0000f2f10, {CONNECTING <nil>}
 DEBUG [core]Channel Connectivity change to CONNECTING
 DEBUG [core]Subchannel picks a new address "eu.thethings.network:1904" to connect
 DEBUG [core]Subchannel Connectivity change to READY
 DEBUG [core]pickfirstBalancer: UpdateSubConnState: 0xc0000f2f10, {READY <nil>}

```

`  
Yesterday, with another id and application key, I managed to perform the operation. Today whatever appId I try is without success.

I try on a Windows and Ubuntu computers same problem.

thank for your help

---

<div class="post-metadata">

**Author:** ![snejra](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/snejra/32/45256_2.png) [@snejra](https://www.thethingsnetwork.org/forum/u/snejra)\
**Post date:** [September 10, 2021, 11:23am UTC](https://www.thethingsnetwork.org/forum/t/cant-migrate-applications-from-v2-to-v3-with-ttn-lw-migrate-tool/51169/2 "2021-09-10T11:23:21Z")

</div>

I think there is already a thread about this: [Ttn-lw-migrate error - #3](https://www.thethingsnetwork.org/forum/t/ttn-lw-migrate-error/51194/3). Are you sure it’s not just your internet connection?

---

<div class="post-metadata">

**Author:** ![DavidTaylor\_DPI](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/davidtaylor_dpi/32/35697_2.png) [@DavidTaylor\_DPI](https://www.thethingsnetwork.org/forum/u/DavidTaylor_DPI)\
**Post date:** [September 10, 2021, 11:16pm UTC](https://www.thethingsnetwork.org/forum/t/cant-migrate-applications-from-v2-to-v3-with-ttn-lw-migrate-tool/51169/3 "2021-09-10T23:16:42Z")

</div>

I would get something similar because the firewall was blocking outgoing ssh connections.

---

<div class="post-metadata">

**Author:** ![system](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/6/2/6250ea44fd2b0d6259489e1a92748df681e1f970.png) [@system](https://www.thethingsnetwork.org/forum/u/system)\
**Post date:** [November 12, 2021, 7:20am UTC](https://www.thethingsnetwork.org/forum/t/cant-migrate-applications-from-v2-to-v3-with-ttn-lw-migrate-tool/51169/4 "2021-11-12T07:20:02Z")

</div>

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.