> For the complete documentation index, see [llms.txt](https://guides.getalby.com/user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.getalby.com/user-guide/alby-hub/faq/how-can-i-migrate-alby-hub-to-a-different-machine.md). # How can I migrate Alby Hub to a different machine? 1. [Self-hosted (Free) -> Self-hosted (Free)](#id-1.-self-hosted-free-greater-than-self-hosted-free-migration) 2. [Self-hosted (Pro) -> Self-hosted (Pro)](#id-2.-self-hosted-pro-greater-than-self-hosted-pro) 3. [Hosted Hub -> Self-hosted (Pro)](#id-3.-hosted-hub-greater-than-self-hosted-pro-migration) ### Important Notice: Please Read Before Continuing You can migrate your Alby Hub to another device while maintaining full access to your funds. Alby Hub is encrypted with the password you chose during setup. Only you can decrypt and access its data even if your Hub is running in the cloud. This also means that only you can perform a migration. #### Scope of This Guide * This guide only refers to migrating Alby Hubs using the embedded lightning node. If you connected an external lightning node (e.g. LND), you can install Alby Hub on any other device and link it again. * Migrations from or to Alby Hubs with an externally connected lightning node (e.g. LND) are not supported currently. #### Before You Start {% hint style="danger" %} * Make sure to have your **12-word recovery phrase** and **unlock password** securely backed up. * During and after the migration, **do not restart your original Alby Hub instance**. Running both instances may cause issues such as force-closing lightning channels. {% endhint %} *** ### 1. Self-hosted (Free) -> Self-hosted (Free) migration **How to migrate your self-hosted Alby Hub (without a subscription) to another device** These steps help you move your self-hosted Alby Hub to another device without a subscription, while keeping all channels active. {% embed url="" %} *** ### 2. Self-hosted Pro -> Self-hosted Pro **How to migrate your self-hosted Alby Hub (Pro) to another device** These steps help you move your self-hosted Alby Hub with an active Pro subscription to another device, while keeping all channels active. You will only need to reconnect your apps afterward. #### Before you start * A self-hosted Alby Hub with an active **Pro subscription** * **Dynamic Channels Backup** enabled: Alby Hub → Settings → Backup * Access to your **12-word recovery phrase** #### Migration steps 1. **Shut down your old self-hosted Hub.** > ⚠️ **Important:** Do not start it again. Restarting the old instance may force-close your lightning channels. 2. Install your self-hosted Alby Hub on the new device.\ ⚠️ **Important:** We recommend using a device that is always online (e.g., a cloud server, Start9, or Umbrel). 3. Start your new Alby Hub and go through the onboarding process. 4. During onboarding, connect the Hub to the **same Alby Account** you used previously. This keeps your Pro subscription active — there is no need to unsubscribe or subscribe again. 5. Click **“Advanced Setup”.** 6. Click **"Import Existing Recovery Phrase"**. 7. Choose an **unlock password** (can be the same as your old one, or a new one) and then **enter your 12-word recovery phrase**. **That's it. The migration is done.** 🎉 **Note**, at the moment it is not possible to migrate a self-hosted Alby Hub with a Pro subscription with enabled dynamic channels backup to a self-hosted Alby Hub without a subscription. If you would like this feature, please submit a feature request to our [feedback board](https://feedback.getalby.com/-alby-hub-request-a-feature). *** ### 3. Hosted Hub -> Self-hosted (Pro) migration **How to migrate your Alby Hub from a hosted Hub (Alby Cloud) to a self-hosted setup with a Pro subscription** These steps help you move your Alby Hub from a hosted Hub to a self-hosted device with a Pro subscription, while keeping all channels active. Apps connected via NWC keep working as before. #### **Before you start** 1. **Enable Dynamic Channels Backup**\ In your current Alby Hub, go to: Settings → Backup\ Make sure *Dynamic Channels Backup* is enabled. * If it is not enabled, activate it. * Click the red restart button in the top-right corner. * Unlock your Hub again. * Double-check that Dynamic Channels Backup is now enabled. 2. **Confirm access to your 12-word recovery phrase.** 3. Install Alby Hub on your new device, but **do not go through the onboarding yet**.\ ⚠️ **Important:** We recommend using a device that is always online (e.g., a cloud server, Start9, or Umbrel). #### Migration steps 1. In your **hosted Hub**, go to **Settings → Migrate Alby Hub → Create Migration File**.\ This creates an encrypted backup of your Hub (size dependent on usage - typically around 10 MB) and downloads it to your computer. It takes a few seconds. > ⚠️ **Important:** After creating the migration file, do not use your hosted Hub anymore. Running both instances may force-close your lightning channels. 2. Open the onboarding page of your **new self-hosted Hub** and click **"Advanced Setup"**.
3. Skip connecting to an **Alby Account** (once the migration file is imported you'll be directed to connect again). 4. Click **"Import wallet from migration file"** and select the file you downloaded in step 1. 5. If you run your hub as a system service, or in Umbrel/Start9, your Hub should restart automatically. Otherwise, wait for it to fully exit, and then start it again. 6. Once your Alby Hub is online, you will be asked to connect your Alby Account. — simply log in once more. 7. Enter your **unlock password** to start the node.\ The initial sync can take a while, even on a fast connection — this is expected. Your channels and balances will show up once the sync is complete. #### After the migration > ⚠️ Make sure your new hub is synced and running before continuing. 1. Go to [getalby.com/subscription](https://getalby.com/subscription), click **Cancel Subscription** and confirm the deletion of your hosted Hub deployment. > This permanently deletes your hosted Hub. Your channels and funds are now safely running on your self-hosted Hub. 2. Your self-hosted Hub will now show a warning that your channel data is stored by Alby's Versioned Storage Service, which is a paid feature. Click **Subscribe to Alby Pro** (or go to [getalby.com/subscription/pro](https://getalby.com/subscription/pro)) and subscribe. The warning disappears once the subscription is active. 3. Deleting the hosted Hub unlinks your Hub from your Alby Account. Re-link it from your self-hosted Hub: go to **Connections → Connected Apps** and click **"Link your Alby Account"**. 4. If you installed Alby Hub as a PWA (Progressive Web App) on your phone or computer, remove it and add it again from the new address of your self-hosted Hub. Apps connected via NWC (e.g. Alby Go, the browser extension) keep working as before. **That's it. The migration is done.** 🎉 --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://guides.getalby.com/user-guide/alby-hub/faq/how-can-i-migrate-alby-hub-to-a-different-machine.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.