# Moving a device from Loriot to TTN

**URL:** <https://www.thethingsnetwork.org/forum/t/moving-a-device-from-loriot-to-ttn/17295>\
**Category:** End Devices (Nodes)\
**Created:** [August 29, 2018, 2:43pm UTC](https://www.thethingsnetwork.org/forum/t/moving-a-device-from-loriot-to-ttn/17295 "2018-08-29T14:43:45Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![arjanvanb](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/arjanvanb/32/46626_2.png) [@arjanvanb](https://www.thethingsnetwork.org/forum/u/arjanvanb)\
**Post date:** [August 29, 2018, 3:21pm UTC](https://www.thethingsnetwork.org/forum/t/moving-a-device-from-loriot-to-ttn/17295/2 "2018-08-29T15:21:02Z")

</div>

> [@mfalkvidd](#):
>
> moving a device from one network (Loriot in this case) to another (TTN in this case) will require reprogramming of the devices to use new device IDs

Not for OTAA. Assuming the devices have been deleted from Loriot, a new OTAA Join Request will only be handled by TTN, and then TTN will supply new session keys and a new DevAddr (with the proper prefix for the TTN network) in its Join Accept.

However, your problem is: how to make the devices initiate a new OTAA Join.

See also [How can an operational node be triggered to join a different network?](https://www.thethingsnetwork.org/forum/t/how-can-an-operational-node-be-triggered-to-join-a-different-network/1106) but that’s too late for existing devices.

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/moving-a-device-from-loriot-to-ttn/17295)._