What you are trying to do is not easy. Zwavejs and de zwave stick work together but also not… zwave info (network) is stored on stick, not homeassistant. Shifting controller and suc sis is very hard from a homeassistant perspective. Maybe this is of some help:
But as I said before… you need to use the aeotec software or maybe some other 3rd party controllers having “deeper” control of the stick (network). (I do not know of any atm).
Edit, think I meant this link
Has anybody managed to upgrade from a 5 to a 7? I would like to get a 7, but I can’t do a re-pair. I have most of my devices in my tenants’ part of the house, and I can’t run around there and exclude and include, they are very private people.
You can use zwavejs2mqtt to backup the 500 and restore it to a 700. Currently it is not recommended to upgrade to a 700 controller: Alerts – Home Assistant
OK, thanks a lot! Then I know I can do it when the time comes. 
Suggest also follow similar discussion on same topic in node-zwave-js discussions on GitHub here:
https://github.com/zwave-js/node-zwave-js/discussions/2927
Experimental way to migrate Z-Wave 500 series to Z-Wave 700 series included in zwavejs2mqtt 6.3.0:
https://github.com/zwave-js/node-zwave-js/issues/3906#issuecomment-997484466
SL dropped an updated firmware (.17) for the 700 sticks today that may contain a fix. Some are already beginning to test.
Did this ever get resolved? I Just got a 7 series as a gift, and would love to migrate. This caught my attention though.
Latest firmware should be good as far as that issue is concerned.
Personally, There’s still some weirdness for me where I still have a node pop up dead on occasion but it’s WAY better. Enough so that I permanently moved back to my 700 stick.
Great to hear. I have node issues on my 5 series. As many of my devices are 7 series compatible (Zooz heavy here), I am hoping for some optimizations from it. Also, I have repeaters so the signal distance issues are not a big concern of mine.
Out of curiosity, how did you approach the migration from 5->7?
Backup and restore tool inside Zwavejs2mqtt… Er The ZwaveJS UI… Took a grand total of 20 minutes.
Supports transitioning between 500 <>700
(they added downgrade support earlier this summer specifically because of that issue)
Up until about a month ago (3-4 weeks) I was getting near-daily dead nodes with the latest .17, but since then none that I’ve noticed.
These past weeks have been the most stable Z-Wave has been since I switched to the Zooz 700 stick in late spring.
Something’s afoot, I just wish I knew what it was. 
Can i migrate from a UZB.me stick to aeotec gen7 without any problems? Or does it need to migrate from
Aeotec to aeotec
HI,
Having problem when trying to migrate from Aeotec Gen5 to Aeotec Z-stick 7 under ZwaveJS UI.
First i update the both sticks firmware and then:
1 - I did backup of Gen5 NVM in Zwave JS UI
2 - shut down the ZwaveJS UI
3 - changed the sticks (plugged in Z-stick7)
4 - started ZwaveJS and changed path to the new stick
5 - restored the NVM to z-stick 7
The nodes appeared in UI but all listed as dead. Re-interview or heal doesnt help. Any idea why is that ?
Make sure your controller’s region is set properly. You can change it from the control panel, under the controller node’s entry.
I cant do it because every time it goes back to Undefined. Tried to do it manualy by exporting the NVM, converting it to json and editing - then flashing again. No luck. I’m out of ideas. I think i read every forum and found no working solution
What version of firmware did you upgrade to?
Z-stick 7 → 7.18.1
Im atttempting the same thing and get the same problems.
Please find these logs, if it helps?
2022-12-08 15:39:06.834 INFO Z-WAVE: Calling api setRFRegion with args: [ 0, [length]: 1 ]
2022-12-08T15:39:06.871Z CNTRLR The controller response indicated failure after 1/3 attempts. Scheduling next
try in 100 ms.
2022-12-08T15:39:06.984Z CNTRLR The controller response indicated failure after 2/3 attempts. Scheduling next
try in 1100 ms.
2022-12-08 15:39:08.145 INFO Z-WAVE: Success zwave api call setRFRegion false
I Finaly migrated my ZWAVE Aeotec z-stick 5 to the Aeotec z-stick 7
I tried it several times without any succes, until yesterday!
Yesterday it suddenly all worked…
I took following steps…
1 created a FULL backup of homeassistant.
zwave-js-ui: 8.10.1
zwave-js: 10.11.1
2 updated the firmware to FW: v7.19.1 SDK: v7.19.1
3 added the 7 stick to my raspberry next to the 5
4 created a NVM backup of the ZWAVE network
5 disabled WS-server under options → homeassistant (ZWAVE JS UI)
6 switched to the 7 stick in ZWAVE JS UI
7 restored the NVM backup from step 4 to the 7 stick
8 All my nodes came back and were still allive…
9 Monitored the system that everyting worked…
10 Under debug you can see the nodes that use lots of traffic, under the options of the specific device
i changed the energy report of those devices to report not so much which helps allot in traffic.
11 Enabled WS-server under options → homeassistant (ZWAVE JS UI)
Has been a day now and still works pretty good, NO dead nodes sofar and running smoothly. Watching the traffic and all looks still oke. Best I’ve had with the 7 stick…
Just for your info.
Just migrated my Zstick 5 to 7 by first migrating from ZWJS to ZWJS-UI (using this article: Switching Z-Wave JS Addons with Minimal Downtime! Z-Wave JS (Official) to Z-Wave JS UI (Community) ) and then following this message to migrate stick 5 to stick 7. Worked like a charm from the 1-st attempt. Thanks a lot for your info!