{"id":35748,"date":"2026-01-11T17:30:43","date_gmt":"2026-01-11T10:30:43","guid":{"rendered":"https:\/\/dps.media\/giai-phong-du-lieu-huong-dan-di-doi-metabase-docker-volume-sang-vps-moi-2026\/"},"modified":"2026-01-11T17:33:43","modified_gmt":"2026-01-11T10:33:43","slug":"liberate-data-guide-to-migrating-metabase-docker-volume-to-new-vps-2026","status":"publish","type":"post","link":"https:\/\/dps.media\/en\/liberate-data-guide-to-migrating-metabase-docker-volume-to-new-vps-2026\/","title":{"rendered":"Data Liberation: Guide to Migrating Metabase (Docker Volume) to New VPS 2026"},"content":{"rendered":"

Have you ever moved a complex Supabase system, and now it's time to face the next challenge: Metabase<\/strong>. While Supabase stores data clearly in bind-mount folders, Metabase by default hides data deeply in Docker Volumes<\/strong> invisible ones. This makes backup or migration to a new VPS more \u201cchallenging\u201d for non-experts.<\/p>\n\n\n\n

In this article, we will solve the problem: How to \u201cextract\u201d all Metabase data (Charts, Dashboard, Users) from a deeply hidden Docker Volume on the old VPS to a brand new VPS, and especially convert it to Folder (Bind Mount) format for easy management forever after.<\/p>\n\n\n\n

Problem: \u201cInvisible\u201d Data (Docker Volumes)<\/h2>\n\n\n\n

When you install Metabase with the command docker run<\/code> or sample compose files online, data is often stored in Docker Volume (Managed Volume). You won't see it when ls \/opt<\/code> or ls \/home<\/code>. It lies deep in \/var\/lib\/docker\/volumes\/...<\/code>.<\/p>\n\n\n

\n
\"Convert
Strategy: Switch from closed Volume to open Folder<\/figcaption><\/figure>\n<\/div>\n\n\n

This causes difficulty when you want to backup (must use specific volume backup command) or edit config directly. Our strategy today is: Release the data<\/strong>.<\/p>\n\n\n\n

Step 1: \u201cDetective\u201d Docker \u2013 Find Data & Password<\/h2>\n\n\n\n

Before migrating, you must know where the data is and the key (password) to unlock it. Many cases after migration forget the old database password, leading to the new Metabase unable to read the data.<\/p>\n\n\n

At Old VPS<\/strong>, use the command docker inspect<\/code> to inspect the information:<\/p>\n\n\n

\n
\"Use
Find the hidden Database password in environment variables<\/figcaption><\/figure>\n<\/div>\n\n\n
# 1. Find Database password (Most important!)\ndocker inspect -f '{{range .Config.Env}}{{println .}}{{end}}' metabase_container_name | grep MB_DB_PASS\n\n# 2. Determine exact Volume path\ndocker inspect -f '{{ json .Mounts }}' metabase_db_container_name<\/code><\/pre>\n\n\n\n
Please note the password string (e.g.: ExAmPlE_P@ssw0rd...<\/code>) and the source volume path (e.g.: \/var\/lib\/docker\/volumes\/metabase_data\/_data<\/code>). We will need them in the next step.<\/p>\n\n\n\n
Step 2: Rsync \u2013 Data Migration<\/h2>\n\n\n\n
After determining the \u201chome address\u201d of the data on the old VPS, we will use rsync<\/code> to transfer it directly to the new VPS. On the new VPS, we will create a proper folder to receive it.<\/p>\n\n\n\n
On New VPS:<\/strong><\/p>\n\n\n
mkdir -p \/opt\/metabase\/pgdata<\/code><\/pre>\n\n\n\n
On Old VPS (Run rsync command):<\/strong><\/p>\n\n\n
# Note: source path taken from step 1\n# IP_VPS_NEW: Replace with new server IP\n\nrsync -avzP \/var\/lib\/docker\/volumes\/metabase_data\/_data\/ root@IP_VPS_NEW:\/opt\/metabase\/pgdata\/<\/code><\/pre>\n\n\n\n
At this point, all your precious data is safely in the folder \/opt\/metabase\/pgdata<\/code> on the new server. It has become physical files that you can see, copy, and backup easily!<\/p>\n\n\n\n
Step 3: Build New House (Docker Compose Clean Setup)<\/h2>\n\n\n\n
Instead of reusing the old messy configuration, we will write a new file docker-compose.yml<\/code> clean, beautiful, and more standard. This file will connect the Metabase Application to the Database data we just transferred.<\/p>\n\n\n
\n
\"New
Connection model: App -> Database -> Local Folder<\/figcaption><\/figure>\n<\/div>\n\n\n
Create file \/opt\/metabase\/docker-compose.yml<\/code> with the following content (Remember to replace PASSWORD with the pass you found in Step 1):<\/p>\n\n\n\n
version: '3.9'\nservices:\n  metabase:\n    image: metabase\/metabase:latest\n    container_name: metabase\n    restart: unless-stopped\n    ports:\n      - \"3000:3000\"\n    environment:\n      MB_DB_TYPE: postgres\n      MB_DB_DBNAME: metabase\n      MB_DB_PORT: 5432\n      MB_DB_USER: metabase\n      MB_DB_PASS: YOUR_SECRET_PASSWORD_HERE\n      MB_DB_HOST: metabase-db\n    depends_on:\n      - metabase-db\n\n  metabase-db:\n    image: postgres:15\n    container_name: metabase-db\n    restart: unless-stopped\n    environment:\n      POSTGRES_USER: metabase\n      POSTGRES_DB: metabase\n      POSTGRES_PASSWORD: YOUR_SECRET_PASSWORD_HERE\n    volumes:\n      # MOST IMPORTANT CONNECTION:\n      # Mount the rsynced data folder into the database\n      - .\/pgdata:\/var\/lib\/postgresql\/data<\/code><\/pre>\n\n\n\n
Then start it:<\/p>\n\n\n
docker compose up -d<\/code><\/pre>\n\n\n\n
Step 4: Domain & SSL Configuration<\/h2>\n\n\n\n
Using Nginx Proxy Manager<\/strong> (which you installed in the previous guide) to expose Metabase to the internet securely.<\/p>\n\n\n\n
    \n
  • Domain:<\/strong> data.your-domain.com<\/code><\/li>\n
  • Forward IP:<\/strong> 172.17.0.1<\/code><\/li>\n
  • Forward Port:<\/strong> 3000<\/code><\/li>\n
  • SSL:<\/strong> Let\u2019s Encrypt (Force SSL)<\/li>\n<\/ul>\n\n\n
    \n
    \"Metabase
    The system works perfectly, dashboard data remains intact<\/figcaption><\/figure>\n<\/div>\n\n\n
    Conclusion<\/h2>\n\n\n\n
    Converting from Docker Managed Volume to Bind Mount (Folder) not only helps you migrate successfully but is also a major upgrade for system administration. From now on, backing up Metabase data is as simple as copying the folder \/opt\/metabase\/pgdata<\/code>.<\/p>\n\n\n\n
    Wishing you a powerful and stable Business Intelligence system in your new home!<\/p>\n