### Understanding Umbrel Migration Options
Migrating an Umbrel Home Server (running umbrelOS on dedicated hardware) to a new Home Server involves transferring your apps, data (e.g., Bitcoin/Lightning node state, file storage), and configurations while keeping everything intact—especially sensitive apps like the Alby App (a Lightning wallet integration), which relies on preserved Lightning Network channels and local data to avoid force-closures or re-sync issues. Based on official Umbrel resources and community experiences, the built-in **Migration Assistant** is the most reliable method for this scenario, as it handles the transfer seamlessly without closing channels or requiring manual file tweaks that could break app dependencies.
The Migration Assistant you praised for Raspberry Pi → Umbrel Home works *similarly* for Home → Home migrations, but it's not identical—it's designed for drive-based transfers rather than network syncs. It's *not* the same as a simple "backup and restore" (which can lead to partial restores, channel closures for Lightning apps, or permission errors causing crashes like force-closing). Manual file copying is riskier and often causes the exact issues you mentioned (e.g., Docker volume mismatches breaking apps).
#### Why Migration Assistant is Best
- **Seamless and Low-Risk**: It copies all app data, configs, and node states (including open Lightning channels) in one go, preserving reputations (e.g., on 1ML.com) and avoiding downtime beyond the transfer time. Users report no app crashes post-migration, including for Alby.
- **Handles Apps Like Alby**: Alby's data lives in Umbrel's app volumes; the assistant transfers these intact, preventing re-authentication or wallet sync failures.
- **Official Support**: Introduced in umbrelOS 0.5.4 (2023) and refined since, it's the recommended path for hardware upgrades.
- **Time Estimate**: 30–60 minutes for a typical setup (faster than Pi migrations due to SSD speeds).
- **Drawbacks**: Requires physical access to drives; not ideal if your new Home is already fully set up (it overwrites existing data).
In contrast:
- **Backup Option**: Umbrel's built-in backups (via Settings > Backups) are great for disaster recovery but *not* for full migrations. They create encrypted snapshots of apps and data, but restoring to a new install often requires re-syncing the blockchain (days of wait) and can force-close Lightning channels if not done carefully. This risks Alby issues like wallet mismatches or crashes.
- **Manual File Copy**: Copying `/home/umbrel/` (or app-specific folders like `/home/umbrel/app-data/`) works for simple cases but frequently leads to permission errors (e.g., chown to 'umbrel' user), Docker compose mismatches, or corrupted volumes—causing force-closes in apps like Alby. It's only for experts and not recommended for production nodes.
#### Step-by-Step Guide: Using Migration Assistant (Home → Home)
This assumes both devices use umbrelOS (latest version recommended—update via Settings > Updates). Ensure your old Home is on a stable network and powered off safely before starting. **Backup first** as a precaution (even if not using it for restore).
1. **Prepare the Old Home Server**:
- Log in to your Umbrel dashboard (
http://umbrel.local or IP).
- Go to **Settings > Shutdown** and power off the device.
- Remove the SSD/HDD from the old Home (typically via a USB enclosure or direct SATA if accessible). This drive holds your data at `/home/umbrel/`.
2. **Set Up the New Home Server (If Not Already)**:
- Power on the new Umbrel Home and complete initial setup (create account, connect to network).
- **Important**: Do *not* install apps or migrate data yet—this will be overwritten.
- Update to the latest umbrelOS if needed.
3. **Connect and Start Migration**:
- Plug the old drive into the new Home (via USB port—Umbrel Home supports external SSDs natively).
- Log in to the new dashboard.
- Go to **Settings > Migration Assistant** (it should appear if the drive is detected; if not, restart and check connections).
- Click **Start Migration**. It will scan the drive, show a progress bar, and transfer everything (apps, data, configs).
- Enter your old Umbrel password if prompted for encryption.
4. **Verify and Finish**:
- Once complete (monitor the progress—expect ~1–2 hours for large blockchains), reboot the new Home.
- Log in: All apps (including Alby) should appear as before, with no re-sync needed for Lightning/Bitcoin.
- Test Alby: Open it, check wallet balance/channels—no force-closes if transfer was clean.
- If issues arise (rare), check logs via **Settings > Troubleshooting > Logs** or Umbrel Community forums.
5. **Post-Migration Cleanup**:
- Format the old drive (via another computer) to avoid accidental dual-runs, which could corrupt channels.
- Update your static IP/DNS if needed.
- Re-enable remote access (e.g., Tailscale) if used.
#### Troubleshooting Common Issues
- **No Migration Button**: Ensure the drive is formatted as ext4 and mounted (check via SSH: `lsblk`). Update umbrelOS or replug.
- **App Crashes (e.g., Alby Force-Closing)**: Verify permissions (`sudo chown -R umbrel:umbrel /home/umbrel/app-data/alby` via SSH). Restart the app.
- **Long Transfer**: Large Bitcoin chains (~600GB as of Nov 2025) take time—use a fast enclosure.
- **Channels Closing**: This shouldn't happen with the assistant; if it does, you may have used backup/restore instead—re-migrate from the original drive.
- **Need Help?**: Post on Umbrel Community (community.umbrel.com) with logs, or check official docs at umbrel.com/support.
This method has a high success rate in community reports, with users calling it "silky smooth" for node upgrades. If your setup is non-standard (e.g., custom Ubuntu install), consider manual copy as a last resort—but stick to the assistant for zero headaches. If you run into specifics, share more details!
