diff --git a/.vitepress/config.mts b/.vitepress/config.mts
index b226c93..6a85435 100644
--- a/.vitepress/config.mts
+++ b/.vitepress/config.mts
@@ -247,6 +247,14 @@ export default withMermaid({
               { text: 'Pelican', link: '/docs/advanced/migrating/pelican' },
             ],
           },
+          {
+            text: 'Migrating to another Instance',
+            collapsed: true,
+            items: [
+              { text: 'Docker', link: '/docs/advanced/migrating/instances/docker' },
+              { text: 'Standalone', link: '/docs/advanced/migrating/instances/standalone' },
+            ],
+          },
           { text: 'Reverse Proxies', link: '/docs/advanced/reverse-proxies' },
           { text: 'Exposing Wings in a Homelab', link: '/docs/advanced/exposing-wings-in-a-homelab' },
           { text: 'Generating SSL Certificates', link: '/docs/advanced/generate-ssl' },
diff --git a/web/docs/advanced/migrating/instances/calagopus-dockerized.md b/web/docs/advanced/migrating/instances/calagopus-dockerized.md
new file mode 100644
index 0000000..b0296df
--- /dev/null
+++ b/web/docs/advanced/migrating/instances/calagopus-dockerized.md
@@ -0,0 +1,206 @@
+---
+prev: false
+next: false
+---
+
+# Migrating from Standalone to Docker Compose
+
+This guide walks you through migrating an existing Calagopus standalone (binary) installation to a Docker Compose stack. The process involves three things: copying your encryption key, exporting your PostgreSQL database and importing it into the new Docker-managed database.
+
+No data transformation is required. The schema is identical between installations.
+
+::: info
+This guide covers the standalone panel compose setup only. If you want to migrate to an All-in-One setup instead, follow the [Docker installation guide](../../../panel/installation/docker.md) first, then return here for the database migration steps.
+:::
+
+
+## Overview
+Here's what you'll be doing at a high level:
+
+- Grab your `APP_ENCRYPTION_KEY` and database password from your existing installation
+- Create the Docker Compose file and plug in those values
+- Start the database container
+- Dump the existing database and restore it into Docker
+- Start the full stack and verify everything works
+
+
+## Before You Start
+Make sure you have:
+
+- A working standalone Calagopus installation
+- Docker and Docker Compose installed on the target host
+- Access to `/etc/calagopus/.env` on your standalone system
+- `pg_dump` available on your standalone system (it should already be there if PostgreSQL is installed)
+
+
+## Collect values from your existing installation
+Open your existing configuration file:
+
+```bash
+cat /etc/calagopus/.env
+```
+
+You need two values from this file:
+
+**`APP_ENCRYPTION_KEY`** a 16-character alphanumeric string that was generated during initial setup:
+```txt
+APP_ENCRYPTION_KEY=Ab3xZ9qR2mKp7vLw
+```
+
+**The database password** found in `DATABASE_URL`:
+```txt
+DATABASE_URL="postgresql://calagopus:yourPassword@localhost:5432/panel"
+```
+The password is the segment between the second `:` and the `@` in the example above, that's `yourPassword`.
+
+::: warning
+The `APP_ENCRYPTION_KEY` must be copied exactly as-is. It is used to decrypt sensitive data stored in your database. If it is wrong or missing, that data cannot be recovered.
+:::
+
+Keep both values handy. You'll need them in the next step.
+
+
+## Set up your Docker directory
+Create a directory to hold your Compose file and persistent data:
+
+```bash
+mkdir -p /opt/calagopus
+cd /opt/calagopus
+```
+
+
+## Create the Docker Compose file
+Create `/opt/calagopus/docker-compose.yml` with the following content. **Before saving, replace the placeholder values** marked with comments:
+
+```yaml
+services:
+  web:
+    image: ghcr.io/calagopus/panel:latest
+    restart: unless-stopped
+    environment:
+      - TZ=Europe/Berlin
+      - REDIS_URL=redis://cache
+      - DATABASE_URL=postgresql://panel:YOUR_DB_PASSWORD@db/panel # enter your db password
+      - DATABASE_MIGRATE=true
+      - PORT=8000
+      - APP_DEBUG=false
+      - APP_LOG_DIRECTORY=/var/log/calagopus
+      - APP_PRIMARY=true
+      - APP_ENABLE_WINGS_PROXY=true
+      - APP_ENCRYPTION_KEY=YOUR_ENCRYPTION_KEY  # paste your key from above
+      - APP_USE_DECRYPTION_CACHE=true
+      - APP_USE_INTERNAL_CACHE=true
+    volumes:
+      - ./data:/var/lib/calagopus
+      - ./logs:/var/log/calagopus
+    ports:
+      - 8000:8000
+    extra_hosts:
+      - "host.docker.internal:host-gateway"
+    depends_on:
+      - db
+      - cache
+
+  db:
+    image: ghcr.io/calagopus/pgautoupgrade:18-alpine
+    restart: unless-stopped
+    environment:
+      - TZ=Europe/Berlin
+      - POSTGRES_USER=panel
+      - POSTGRES_PASSWORD=YOUR_DB_PASSWORD  # use the same password as above
+      - POSTGRES_DB=panel
+      - PGDATA=/data
+    volumes:
+      - ./postgres:/data
+
+  cache:
+    image: ghcr.io/calagopus/valkey:latest
+    restart: unless-stopped
+    command: --protected-mode no --save 60 1
+    environment:
+      TZ: Europe/Berlin
+    volumes:
+      - ./cache:/data
+```
+
+Replace:
+- `YOUR_ENCRYPTION_KEY` the `APP_ENCRYPTION_KEY` value collected above
+- `YOUR_DB_PASSWORD` (both occurrences) you can reuse your old database password, or choose a new one. It just needs to match in both the `web` and `db` service definitions.
+
+
+## Start the database and cache
+Start only the database and cache containers for now. The web container will fail on first boot if the database isn't populated yet.
+
+```bash
+docker compose up -d db cache
+```
+
+Wait a few seconds for the database to finish initializing, then confirm it's running:
+
+```bash
+docker compose ps
+```
+
+Both `db` and `cache` should show as `running`.
+
+
+## Export your existing database
+Run this on your **standalone system** (not inside Docker). Replace `yourPassword` with the password collected earlier:
+
+```bash
+PGPASSWORD="yourPassword" pg_dump \
+  -h 127.0.0.1 \
+  -U calagopus \
+  -d panel \
+  -F c \
+  -f /opt/calagopus/panel.backup
+```
+
+This creates a compressed database dump at `/opt/calagopus/panel.backup`.
+
+> If you're migrating to a different host, copy `panel.backup` to `/opt/calagopus/` on the target machine before continuing.
+
+
+## Import the database into Docker
+From `/opt/calagopus` on your Docker host, run the following:
+
+```bash
+docker exec -i calagopus-db-1 pg_restore \
+  -U panel \
+  -d panel \
+  --no-owner \
+  --clean \
+  --if-exists \
+  < panel.backup
+```
+
+You may see some harmless notices about dropping objects that don't exist yet - that's normal. The restore is successful as long as the command exits without errors.
+
+
+## Start the full stack
+```bash
+docker compose up -d
+```
+
+The web container will run any pending database migrations automatically on first boot (`DATABASE_MIGRATE=true`).
+
+
+## Verify the migration
+Once the stack is up, open Calagopus in your browser and check:
+
+- You can log in with your existing credentials
+- Your servers are visible and intact
+- No setup wizard (OOBE) appears (if it does, the database import likely did not work - see below)
+- Wings nodes are still connected
+
+
+## Troubleshooting
+
+**Setup wizard (OOBE) appears after starting:**
+The database was not imported correctly, or the wrong database was targeted. Stop the stack, double-check the import command used the right container name (`calagopus-db-1`), re-run the import, then restart with `docker compose restart web`.
+
+**Login fails / encrypted data appears corrupted:**
+Your `APP_ENCRYPTION_KEY` in `docker-compose.yml` probably doesn't match the one from your original installation. Stop the stack, correct the key and run `docker compose up -d` again.
+
+**`calagopus-db-1` container not found:**
+The container name is generated from your directory name. Check the actual name with `docker compose ps` and adjust the import command accordingly.
diff --git a/web/docs/advanced/migrating/instances/calagopus-standalone.md b/web/docs/advanced/migrating/instances/calagopus-standalone.md
new file mode 100644
index 0000000..854d323
--- /dev/null
+++ b/web/docs/advanced/migrating/instances/calagopus-standalone.md
@@ -0,0 +1,139 @@
+---
+prev: false
+next: false
+---
+
+# Migrating from Docker Compose to Standalone
+
+This guide walks you through migrating an existing Calagopus Docker Compose installation to a standalone binary install. The process involves copying your encryption key, exporting the PostgreSQL database from Docker, and importing it into the host PostgreSQL instance.
+
+No data transformation is required. The schema is identical between installations.
+
+
+## Before You Start
+Make sure you have:
+
+- A running Calagopus Docker Compose installation
+- Access to your `compose.yml` file
+- PostgreSQL and Valkey installed on the target host (follow the [binary installation guide](/docs/panel/installation/binary) if not)
+- The Calagopus binary installed but not yet configured - you need to land on the OOBE screen and stop there
+
+::: warning Don't click through the OOBE
+![Calagopus Panel OOBE](../../../panel/oobe.webp)
+The binary install needs an empty database to write into on first run. Stop at the OOBE screen and come back here.
+:::
+
+
+## Collect values from your existing installation
+Open your `compose.yml` and find the `web` service environment variables. You need two values:
+
+**`APP_ENCRYPTION_KEY`**:
+```yaml
+- APP_ENCRYPTION_KEY=Ab3xZ9qR2mKp7vLw
+```
+
+**The database password**, found in `POSTGRES_PASSWORD` on the `db` service:
+```yaml
+- POSTGRES_PASSWORD=yourPassword
+```
+
+::: warning
+The `APP_ENCRYPTION_KEY` must be copied exactly as-is. It is used to decrypt sensitive data stored in your database. If it is wrong or missing, that data cannot be recovered.
+:::
+
+Keep both values handy. You'll need them shortly.
+
+
+## Configure the binary installation
+Open `/etc/calagopus/.env` on your target host and set the following values.
+
+Set `APP_ENCRYPTION_KEY` to the value copied above:
+```env
+APP_ENCRYPTION_KEY=Ab3xZ9qR2mKp7vLw
+```
+
+Set `DATABASE_URL` to point at your host PostgreSQL instance. Use the same password from your Docker setup, or a new one if you prefer. Just make sure it matches what you set when creating the database user:
+```env
+DATABASE_URL="postgresql://calagopus:yourPassword@localhost:5432/panel"
+```
+
+
+## Export the database from Docker
+Run this from the directory containing your `compose.yml`. Replace `yourPassword` with the `POSTGRES_PASSWORD` collected earlier:
+
+```bash
+docker exec calagopus-db-1 pg_dump \
+  -U panel \
+  -d panel \
+  -F c \
+  -f /tmp/panel.backup
+
+docker cp calagopus-db-1:/tmp/panel.backup ./panel.backup
+```
+
+This copies the dump out of the container to `./panel.backup` on your host.
+
+::: info
+If you're migrating to a different host, copy `panel.backup` to that machine before continuing.
+:::
+
+
+## Import the database into the host PostgreSQL
+First, make sure the database user and database exist. Connect to PostgreSQL:
+
+```bash
+sudo -u postgres psql
+```
+
+Then create the user and database:
+
+```sql
+CREATE USER calagopus WITH PASSWORD 'yourPassword';
+CREATE DATABASE panel OWNER calagopus;
+GRANT ALL PRIVILEGES ON DATABASE panel TO calagopus;
+exit
+```
+
+Now restore the dump:
+
+```bash
+PGPASSWORD="yourPassword" pg_restore \
+  -h 127.0.0.1 \
+  -U calagopus \
+  -d panel \
+  --no-owner \
+  --clean \
+  --if-exists \
+  panel.backup
+```
+
+You may see some harmless notices about dropping objects that don't exist yet. That's normal. The restore is successful as long as the command exits without errors.
+
+
+## Start the binary
+```bash
+systemctl start calagopus-panel
+```
+
+The panel will run any pending database migrations automatically on first boot.
+
+
+## Verify the migration
+Open Calagopus in your browser and check:
+
+- You can log in with your existing credentials
+- Your servers are visible and intact
+- No setup wizard (OOBE) appears (if it does, the database import likely did not work, see below)
+- Wings nodes are still connected
+
+
+## Troubleshooting
+
+**Setup wizard (OOBE) appears after starting:**
+The database was not imported correctly. Stop the panel with `systemctl stop calagopus-panel`, drop and recreate the database, re-run the import, then start again.
+
+**Login fails / encrypted data appears corrupted:**
+The `APP_ENCRYPTION_KEY` in `/etc/calagopus/.env` does not match the one from your Docker installation. Stop the panel, correct the key, and start it again.
+
+**`calagopus-db-1` container not found:**
+The container name is generated from your compose directory name. Check the actual name with `docker compose ps` and adjust the export command accordingly.
diff --git a/web/docs/advanced/migrating/instances/docker.md b/web/docs/advanced/migrating/instances/docker.md
new file mode 100644
index 0000000..8b03303
--- /dev/null
+++ b/web/docs/advanced/migrating/instances/docker.md
@@ -0,0 +1,32 @@
+---
+prev: false
+next:
+  text: 'Migrating from Standalone to Docker Compose'
+  link: '/docs/advanced/migrating/instances/calagopus-dockerized'
+---
+
+# Migrating to Docker
+
+So you've been running Calagopus as a standalone installation and want to move it into Docker without losing your users, servers, or configuration? This is a straightforward migration.
+
+Both setups use the same database schema, so the process comes down to one thing: moving your existing database into the new Docker environment. Your database already contains everything: users, servers, settings etc. so once it's transferred, your Docker setup will pick up exactly where your standalone install left off.
+
+There's no importer, no data conversion, and no format changes involved. You're just changing how the application is deployed.
+
+### The general flow looks like this:
+
+- Stop your standalone installation
+- Export your database
+- Set up your Docker environment
+- Import the database into the Docker database container
+- Start the full Docker stack
+
+Once completed, your panel should look and behave exactly the same as before.
+
+### This guide assumes:
+
+- You're using the standard standalone installation
+- Your database is running locally (default setup)
+- You're moving to the standard Docker Compose setup
+
+If your setup differs significantly (custom database hosts, unusual configurations), you may need to adapt some steps.
\ No newline at end of file
diff --git a/web/docs/advanced/migrating/instances/standalone.md b/web/docs/advanced/migrating/instances/standalone.md
new file mode 100644
index 0000000..d006d0a
--- /dev/null
+++ b/web/docs/advanced/migrating/instances/standalone.md
@@ -0,0 +1,31 @@
+---
+prev: false
+next:
+  text: 'Migrating from Docker Compose to Standalone'
+  link: '/docs/advanced/migrating/instances/calagopus-standalone'
+---
+
+# Migrating to Standalone
+
+So you've been running Calagopus in Docker and want to move to a standalone installation without losing your users, servers, or configuration? This is a straightforward migration.
+
+Both setups use the same database schema, so the process comes down to one thing: exporting your existing database from Docker and importing it into a fresh standalone installation. Once the data is in place, the panel will pick up exactly where it left off.
+
+There's no importer, no data conversion, and no format changes involved. You're just changing how the application is deployed.
+
+### The general flow looks like this:
+
+- Export the database from your Docker setup
+- Stop your Docker stack
+- Set up a fresh standalone installation
+- Import the database into the standalone database
+- Start the standalone panel
+
+Once completed, your panel should look and behave exactly the same as before.
+
+### This guide assumes:
+
+- You are currently running the standard Docker Compose setup
+- You are installing the standard standalone version of Calagopus
+
+If your setup has been modified (for example, external databases or custom container configurations), you may need to adjust the steps accordingly.
\ No newline at end of file