# How to Migrate ABP Devices from V2 to V3

**URL:** <https://www.thethingsnetwork.org/forum/t/how-to-migrate-abp-devices-from-v2-to-v3/43705>\
**Category:** Migrating Devices to V3\
**Tags:** guide\
**Created:** [February 3, 2021, 10:32am UTC](https://www.thethingsnetwork.org/forum/t/how-to-migrate-abp-devices-from-v2-to-v3/43705 "2021-02-03T10:32:21Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![htdvisser](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/htdvisser/32/45312_2.png) [@htdvisser](https://www.thethingsnetwork.org/forum/u/htdvisser)\
**Post date:** [February 3, 2021, 11:15am UTC](https://www.thethingsnetwork.org/forum/t/how-to-migrate-abp-devices-from-v2-to-v3/43705/3 "2021-02-03T11:15:43Z")

</div>

This guide is specifically for migrating **existing** devices, not about **new** devices. When creating **new** ABP devices on V3, you can request a DevAddr from the Network Server, and Packet Broker routing (at least of uplinks) will work fine. If the firmware of your ABP device is configured with an **RX1 Delay** of 1 second (which it is, unless you changed it), downlink through Packet Broker may not work (it may not arrive in time for that 1 second window).

People are free to migrate their gateways, or to keep them on v2. We do ask people to coordinate the migration of gateways with their local community.

And I can’t repeat this often enough: We’re asking people to **not use ABP devices** unless they really have a good reason to use ABP.

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/how-to-migrate-abp-devices-from-v2-to-v3/43705)._