Migration service
Move to Home Assistant with a measured migration plan
Bring existing smart devices and routines into a system with clearer control, documentation and future flexibility.
Device apps
Legacy hub
Cloud routines
→
Unified Home Assistant
Dashboards · automations · documentation
Existing-system assessment
Understand the estate before moving it
Devices, hubs, routines, networks and cloud dependencies are catalogued before a migration path is recommended.
Apps
Hubs
Cloud services
Network
Compatibility matrix
Retain, bridge, replace or leave dependent
| Decision | When it applies | What is documented |
|---|---|---|
| Retain | Compatible and useful | Integration path |
| Bridge | A stable bridge is appropriate | Dependencies |
| Replace | No suitable path remains | Replacement rationale |
| Cloud-dependent | Local control is unavailable | Service dependency |
Migration flow
A controlled path, not a sudden cutover
01
Audit
02
Prioritise
03
Pilot
04
Migrate
05
Stabilise
After migration
A clearer baseline for future work
The completed setup can include an appropriate handover, record of key dependencies and next steps for support or expansion.
Migration record
- Retained systems
- New integrations
- Known dependencies
- Backup considerations
Migration FAQ