Moving Home Assistant to new hardware is mostly a backup-and-restore job. A few extra steps cover your radios, your network address and a short list of things that don’t restore cleanly. Keep the old system running until the new one is confirmed working.
Short answer
Create a full backup on the old system and download it. Install Home Assistant OS on the new hardware, and choose Restore from backup during onboarding. Then move your radios if you need to, and run the post-restore checks.
Before you start
- Update the old system first, then take the backup. Use the same Home Assistant version on the new system if you can.
- Keep your backup encryption key. Since Home Assistant 2025.1, automatic backups are encrypted. Restoring one needs the key from your emergency kit. Without it, the restore fails.
- Check that your hardware is supported. Home Assistant OS runs on Home Assistant Green or Yellow, a Raspberry Pi 5, or an x86-64 PC or virtual machine with the generic x86-64 image. Check that the new storage has enough space for your current system.
Step 1: Create and download a full backup
- On the old system, go to Settings > System > Backups.
- Select Backup now (or the create option), and give the backup a name.
- Download the backup file to your computer, and note where you saved it.
A full backup includes configuration, add-ons and their data, media, shared folders and the history database.
Step 2: Install Home Assistant on the new device
Flash Home Assistant OS to the new drive or SD card, boot the device, and open its onboarding page in a browser. Don’t finish onboarding as a new system yet. The restore option is on the first screen.
Step 3: Restore at onboarding
At the start of onboarding, choose Restore from backup, upload the backup file, and enter your encryption key if asked. A restore can take from a few minutes to an hour, and larger systems take longer. Excluding the history database speeds up the restore.
Shut down the old system before you bring the new one onto the network under the same identity. Two running instances that use the same radios or locks can conflict.
Step 4: Move your radios and network
- Zigbee: Move the same coordinator stick. Your devices stay paired, so you don’t need to re-pair them. If you switch to a new stick, ZHA can migrate the radio for supported types. Zigbee2MQTT migration is manual.
- Z-Wave: The node data lives on the stick, so move the stick. Keep the S0 and S2 keys from your Z-Wave JS configuration.
- Thread and Matter: Thread and Matter data restore with the backup. A new Thread radio may need to be re-commissioned. Check this against your setup.
- Device paths: Use
/dev/serial/by-id/paths. A path such as/dev/ttyUSB0can change when you plug a stick into a different port. - IP address: After the old system is off, give the new system the old IP address with a DHCP reservation. MQTT clients and firewall rules may point to that address. Some devices take a few minutes to reconnect after an address moves, while network caches clear.
Step 5: Post-restore checks
- Open Settings > Repairs and work through any issues.
- Update your add-ons.
- Test a device from each integration, and run a few key automations.
- Re-sign in to any integration that asks you to, such as cloud accounts.
Common mistakes
- Copying YAML files isn’t a backup. Integrations and entity registries created in the UI live in Home Assistant’s storage files, and a YAML copy misses them.
- Moving the same Zigbee stick doesn’t require re-pairing. Keep the stick, and your devices stay paired.
- Restoring to a Container or Core install brings back configuration only. Add-ons restore only on Home Assistant OS or Supervised installs.
- An encrypted backup without its key can’t be recovered. Store the key somewhere safe before you start.
For how integrations and devices fit together after the move, see adding and managing devices in Home Assistant. If you’re deciding which Zigbee stack to use on the new system, read ZHA vs Zigbee2MQTT.