DO NOT DELETE IT! Note all the warnings about not being undone - also once deleted the eui for the GW cannot be re-used preventing others registering.
Best practice is likely add new owner as collaborator on the GW Console Settings page then use the transfer ownership option under the GW overview… you can skip the collaborator option but is useful to check user entered correctly and valid
The new owner can then update details (e.g. location) and otherwise manage/update as needed including changing himan readable description etc. on own console view.
For the sake of completeness: it seems to depend on the packet forwarder that is used.
When using a forwarder that enforces a specific gateway id (like based on the MAC address), then indeed one should never delete it. This applies to, e.g., the legacy forwarder, which is also used when registering the TTIG on V2 (though that uses Basic Station). But other forwarders allow for choosing one’s own gateway id. For those, one simply needs to choose a different unique id when deleting and adding it again. From Slack:
Hmmm, I guess my gateways don’t tend to force the eui as the ID - I’ve got both Multitech and RAK gateways that have been added/removed from various TTN Accounts, so YMMV
Same might go for devices: their unique id might be blocked for future usage, but as you can choose whatever you want, that seems fine. Beware:
Thanks for expanding for the wider use cases - I have some more flexible units also similar to Mat, though as Gypo called out the TTIG specifically I just wanted to be direct & clear with such ‘fixed’ devices that avoiding deletion is key point Devices (nodes) seems to be a bit different from the GW’s which is good/more flexible