Migration from C7 to C8 Pro failed. No Z-wave devices and Webcore

[etsvilik]

Migrated using cloud backup to C8-Pro. Both were on the latest FW
2.4.2.160.
No Z-wave devices in the Settings. Zigbee is OK. When I click on Webcore app - just loads an animation forever.
Made sure to check boxes for Z-wave, Zigbee, Files etc. Webcore pistons were disabled before migration. Tried to shut down and unplug for 30 sec. Tightened the antennas. New hub is in the same spot as the old one.

[jtp10181]

What are you using for power on the new hub? Use the original supplied power block and cord to do the migration. Other power sources sometimes cause issues with z-wave. I would just try the migration a second time, run a new backup and restore again. I think you can just load the cloud backup again from the main UI in the backup section. If not, use the diagnostic tool on the new hub to do a soft reset.

[etsvilik]

Thank you. Reimporting the backup resolved the issues with Z-Wave. The Webcore app loads, but I'm unable to open any pistons in the dashboard.

[jtp10181]

I believe some people possibly had to restore the pistons from a backup to get them to work again after migration? I do not use webCore so I am not a lot of help.

Might be worth checking these posts I found:

Webcore not loading after migrating to new hub

Ok so I did a cloud migrating from a C8 to a C8-Pro, But now I can't open my webcore pistons. I can open webcore and see all my pistons, but when I click on anyone one of them it never loads. They are running as expected, but I need to make changes Note: This is using the system webcore not the user webcore

Webcore failure after C8 Pro migration

Thank you for the info! I AM NOT AMUSED! I too read the manual and only disabled the root WebCORE App. I ran into your exact problem. I was going to try the restore. But the backup does not save global variables nor does it remember what devices were authorized. I figured not to retread your path and quickly gave up and followed your directions to a T. Works like a treat now. It is now December 2024! Please add this information to the documentation!!! If you are another poor soul. Follow @e…

[chrisbvt]

@etsvilik

The Webcore app loads, but I'm unable to open any pistons in the dashboard

That happened to me as well during a migration. I'm pretty sure I paused the Webcore app, as is instructed to pause any internet apps and devices before taking the migration backup. I did not disable each piston individually before taking the backup, and I wondered if that was why they were not working.

I had to restore my pistons from a backup file. I didn't have a recent backup so I actually had to boot up the old hub, save the pistons to a file, then I restored them on the new hub.

[etsvilik]

This was a major pain. There has to be a better way to handle Webcore migration.
After numerous soft resets, reimporting backups, and other troubleshooting efforts, I managed to get the pistons to load. It works now, but in frustration, I lost track of the exact steps it took.
I paused each piston and the app itself before backing up the old Hubitat. ( I tried "Pause All Pistons," but that did not do anything.)
When I tried again to back up pistons on the old hub, the attempt failed because it tried to back up pistons from both the old and new Webcore instances, stopping the backup midway.
How do I "unregister" the old webcore instance from webcore app?