Ever since I’ve been using two hubs on the same location (and indeed even before that), I’ve been convinced that it was not possible to use the IDE to change the hub a device was installed on. It just didn’t work. I actually needed to delete the device from one hub and pair it to the other (not necessarily in that order) and fix up all the automations for the new device which was really tedious. I thought that until about ten minutes ago …
I was sitting in the garden and saw I had created virtual switches on the wrong hub a while back and I idly changed the hub in the IDE and it worked. Then I tried it with a Zigbee device. That changed too. OK it didn’t actually communicate because the Zigbee pairing was wrong. So I paired it to the correct hub and it worked. No need to change anything else as it was the same device.
Thinking about it, the migration tool does essentially the same thing - it does the ST side of things but still needs you to pair the devices again.
How on earth have I never noticed this before? It speeds up migrating devices no end. No deletion of devices, no reauthorising devices and replacing tiles in ActionTiles, no reauthorising devices and editing pistons in webCoRE. It is a game changer.