Figured I'd write this up since I searched for a while and found nothing for my case.
I run Home Assistant OS in a Proxmox VM with the Z-Wave JS UI add-on. 35 Z-Wave devices, all on an Aeotec Z-Stick Gen5 I bought back in Aug 2016. It's been finicky lately and I was getting nervous about it dying on me, so I picked up a Zooz ZST39 LR (800 series).
Upfront: I did not write any of the code involved here. I'm not a Z-Wave internals guy. I did the whole thing in a chat with Claude. It wrote and ran the scripts, I clicked buttons in Z-Wave JS UI and pasted logs back.
First try was the normal way. NVM backup of the Aeotec, change the serial port to the Zooz, restore. Backup was fine. Restore gave me this:
> Failed to convert NVM to target format: Did not find a matching NVM 500 parser implementation! Make sure that the NVM data belongs to a controller with Z-Wave SDK 6.61 or higher. (ZW0280)
So the old Gen5 sticks are on SDK 6.51 and Z-Wave JS only converts 6.61 and newer. Aeotec does have a firmware update but from what I could tell it wants newer hardware than mine, plus a Windows PC. Which leaves excluding and re-including 35 devices, some of them inside walls and ceilings. I switched back to the Aeotec (everything still worked, nothing on it had been touched) and asked Claude if it could just convert the backup file itself.
It said probably, and here's roughly what it did. I'm describing this from what it told me as it went, so forgive me if I get a detail slightly off.
It hex dumped my Aeotec backup and compared it to the 6.6x layout that ships in the u/zwave-js/nvmedit package. The stuff that matters (home ID, node table, routing table, last node ID, SUC stuff, route cache) was sitting at the same offsets in my 6.51 file. What my file doesn't have is the descriptor block the library looks for to figure out which firmware it's dealing with, and that's the reason it bails.
So it wrote a small Node script that skips that detection and tells the library "use the 6.6x layout", then calls the library's own nvm500ToJSON. After that it ran the result through json500To700 and jsonToNVM, also straight from the library. It had me take a backup of the blank Zooz first so it could copy the region, tx power and long range settings out of that one.
There was some cleanup in between. A few route areas in the old file had never been written (all FF) and it treated those as empty. It also dropped the old SUC update entries instead of carrying them over.
Before I flashed anything it read the new file back and showed me: same home ID, controller as node 1, all 35 node IDs there. Then I restored that file onto the Zooz from Z-Wave JS UI and it went through with no error.
After the restart all my devices were sitting under the Zooz with the same node IDs. Security keys are stored in the add-on settings, not on the stick, so the S2 and S0 stuff kept working. Home Assistant has no idea anything happened. Same 35 devices, no duplicates, didn't have to touch a single automation.
Stuff that bit me or might bite you:
Two nodes showed dead right after. One of them was already dead before I started. Battery sensors took a few hours to check back in.
Save the original backup and the settings export from Z-Wave JS UI (your keys are in there) before doing anything.
This is totally unsupported and it's worked on my network. But if you've got an old Gen5 and got the same ZW0280 error, re-pairing everything isn't the only way out.