If you have a new Hubitat Elevation model C-8 hub and are looking to migrate from a C-5 or C-7, follow the steps below to perform a seamless migration, including Z-Wave and Zigbee devices.
NOTE: Some users are currently experiencing problems migrating from model C-5 to C-8 when using the current platform version, 2.3.6. We are investigating this problem and hope to have it fixed in the next release. See this post for more information: https://community.hubitat.com/t/investigating-migration-failure-from-c-5-to-c-8-platform-version-2-3-6-146/127859
Ensure your current ("old") hub:
On the "old" hub:
Create a cloud backup on the old hub:
Confirm that a cloud backup was created. If you do not see a list of backups at the top of the page, select this hub's only in the Show all or this hub's only heading at the top of the page. Look for cloud or migration (depending on the method used above) under the Type column and the name of the current/old hub under Name to find the backup you just made.
Shut down the old hub from Settings > Shutdown. After the hub is shut down, remove the hub's power supply.
Power on the new hub and connect it to your network (wired preferred but wireless is possible; see Registration and Setup). Continue with the next step when you get to the Welcome to Hubitat Elevation screen the new hub.
On the new hub, select the Migrating from another hub? link (if this link only directs you to this documentation, choose "cloud" under "Restore from local or cloud backup?" instead). Log in to your My Hubitat account when prompted. This must be the same account under which the backup in step 2 was created.
On the cloud backups page that will appear, confirm that you have read all of the instructions in this document. Then, select the Migrate button corresponding to the backup you made in step 2.
When prompted, select the options you'd like to restore (Z-Wave, Zigbee, and/or File Manager). If your old hub was configured with a password for cloud backups, enter that password where prompted. Then select Migrate and confirm the restoration.
NOTE: A restore will reset and overwrite the main hub's database plus one or both radios, depending on the options selected. You cannot combine hub database or radio backups from multiple hubs.
Certain devices and integrations may require some additional action after migration:
Other notes:
Users of the Hubitat mobile app should open the app after migration and choose the new hub under Settings > Select Hub (if the app was associated with the old hub).
If using Hub Mesh, if the other hub(s) do not automatically find the restored hub within a few minutes, use the Settings > Hub Mesh > Update tab to "swap" the old hub with the new hub.
This list refers to built-in apps only. If you use third-party apps or external systems that refer to cloud endpoints (which are unique to each hub), even ones provided by built-in apps, you may need to reconfigure them. This includes cloud endpoint triggers in Rule Machine, Maker API cloud endpoints, Hubitat Dashboard cloud links, and others.
Local systems may or may not be affected, depending on whether they initiate a connection to your hub by IP address and whether your new hub IP address is the same.
Most users do not need two (or more) hubs, so if you do not plan to use your old hub again, simply shut it down and disconnect it from power. If you plan to re-use the old hub and you have verified that the new hub is working properly, then we suggest the following steps:
CAUTION: Do not perform a reset of any kind on the old hub until you have verified that the new hub is working correctly.
If you plan to use Zigbee on the old hub again, besides resetting the radio, the Zigbee channel on the old hub must be set to a different channel from the new hub. (For those who want the technical details: they will share an IEEE address, carried over from migration, even if the PAN ID is different; this will no longer apply if Zigbee on the new hub is ever reset and not migrated.) For Z-Wave, a simple reset, as above, will suffice.