🚚 Self-Transferring OpenClaw Bot — ย้าย AI Agent ข้ามเครื่องแบบไม่พลาด🚚 The Self-Transferring OpenClaw Bot — Move an AI Agent Between Machines Without Losing a Thing

# SSH เข้าเครื่องเก่า
ssh user@your-vps-ip

# หยุด gateway
openclaw gateway stop

# ยืนยันว่าหยุดแล้ว
openclaw gateway status
# ควรเห็น: Gateway is not running

# ดูขนาดทั้งหมด
du -sh ~/.openclaw

# ดูรายละเอียดแต่ละโฟลเดอร์
du -sh ~/.openclaw/*/

# ตัวอย่างผลลัพธ์:
# 12M   ~/.openclaw/workspace/
# 4.0K  ~/.openclaw/credentials/
# 256K  ~/.openclaw/agents/
# 2.1M  ~/.openclaw/telegram/
# 80K   ~/.openclaw/cron/

# สร้าง backup พร้อม verify
openclaw backup create --verify --output ~/

# จะได้ไฟล์ประมาณ:
# ~/2026-03-24T00-00-00.000Z-openclaw-backup.tar.gz

# ดูขนาด backup
ls -lh ~/2026-03-24*.tar.gz

# Export crontab
crontab -l > ~/crontab-backup.txt

# Copy git credentials ถ้ามี
cp ~/.git-credentials ~/git-credentials-backup 2>/dev/null

# Copy .env files ถ้ามี
cp ~/.openclaw/.env ~/env-backup 2>/dev/null

# บันทึก OpenClaw version
openclaw --version > ~/openclaw-version.txt
npm list -g openclaw >> ~/openclaw-version.txt

# วิธี A: scp (ง่ายสุด) — รันจากเครื่องใหม่ (Mac Studio)
scp user@your-vps-ip:~/2026-03-24*.tar.gz ~/Downloads/

# วิธี B: rsync (เร็วกว่าถ้าไฟล์ใหญ่ หรืออยากมี progress)
rsync -avz --progress user@your-vps-ip:~/2026-03-24*.tar.gz ~/Downloads/

# วิธี C: ถ้าทั้งสองเครื่องอยู่ใน Tailscale
scp user@vps-tailscale-name:~/2026-03-24*.tar.gz ~/Downloads/

scp user@your-vps-ip:~/crontab-backup.txt ~/Downloads/
scp user@your-vps-ip:~/git-credentials-backup ~/Downloads/
scp user@your-vps-ip:~/openclaw-version.txt ~/Downloads/

# ติดตั้ง Node.js ถ้ายังไม่มี (macOS)
brew install node

# ติดตั้ง OpenClaw (ใช้ version เดียวกับเครื่องเก่า)
npm install -g openclaw

# ตรวจ version
openclaw --version

# ตรวจ backup ก่อน restore
openclaw backup verify ~/Downloads/2026-03-24*.tar.gz

# Restore — แตกไฟล์ไปที่ ~/.openclaw
# ถ้า ~/.openclaw ยังไม่มี (fresh install):
mkdir -p ~/.openclaw
tar -xzf ~/Downloads/2026-03-24*.tar.gz -C ~

# ตรวจว่าไฟล์ครบ
ls -la ~/.openclaw/
ls -la ~/.openclaw/workspace/
ls -la ~/.openclaw/credentials/

# เปิด config
nano ~/.openclaw/openclaw.json

# สิ่งที่ต้องเช็ค/แก้:
# 1. workspace path — ถ้า hardcoded เป็น /root/... แก้เป็น /Users/yourname/...
# 2. hostname/IP — ถ้า gateway bind อยู่กับ IP เก่า
# 3. gateway port — ถ้าเครื่องใหม่ใช้ port นั้นอยู่แล้ว
# 4. tools path — เช่น path ไป python, docker, etc.

# Git credentials (ถ้ามี)
cp ~/Downloads/git-credentials-backup ~/.git-credentials

# Crontab — ต้องแก้ path ก่อน import
# เปิดดูก่อน:
cat ~/Downloads/crontab-backup.txt
# แก้ path แล้ว import:
crontab ~/Downloads/crontab-backup.txt

# เริ่ม gateway
openclaw gateway start

# ตรวจ status
openclaw gateway status

# ดู logs ว่ามี error ไหม
openclaw logs --tail 50

#!/bin/bash
# ============================================
# OpenClaw Migration Self-Check
# ย้าย bot มาแล้ว ต้องเช็คว่าครบ
# ============================================

PASS=0
FAIL=0
WARN=0
OPENCLAW_DIR="$HOME/.openclaw"

check() {
    local label="$1"
    local result="$2"
    if [ "$result" = "pass" ]; then
        echo "  ✅ $label"
        ((PASS++))
    elif [ "$result" = "warn" ]; then
        echo "  ⚠️  $label"
        ((WARN++))
    else
        echo "  ❌ $label"
        ((FAIL++))
    fi
}

echo ""
echo "🔍 OpenClaw Migration Self-Check"
echo "================================="
echo ""

# --- 1. Core Files ---
echo "📁 Core Files"
[ -f "$OPENCLAW_DIR/openclaw.json" ] && R="pass" || R="fail"
check "openclaw.json exists" "$R"

[ -d "$OPENCLAW_DIR/credentials" ] && R="pass" || R="fail"
check "credentials/ directory exists" "$R"

[ -d "$OPENCLAW_DIR/agents" ] && R="pass" || R="fail"
check "agents/ directory exists" "$R"

echo ""

# --- 2. Workspace ---
echo "📂 Workspace"
[ -d "$OPENCLAW_DIR/workspace" ] && R="pass" || R="fail"
check "workspace/ exists" "$R"

[ -f "$OPENCLAW_DIR/workspace/SOUL.md" ] && R="pass" || R="fail"
check "SOUL.md exists (bot personality)" "$R"

[ -f "$OPENCLAW_DIR/workspace/MEMORY.md" ] && R="pass" || R="warn"
check "MEMORY.md exists (long-term memory)" "$R"

[ -f "$OPENCLAW_DIR/workspace/USER.md" ] && R="pass" || R="warn"
check "USER.md exists (user profile)" "$R"

[ -d "$OPENCLAW_DIR/workspace/memory" ] && R="pass" || R="warn"
check "memory/ directory exists (daily logs)" "$R"

MEM_COUNT=$(ls "$OPENCLAW_DIR/workspace/memory/"*.md 2>/dev/null | wc -l)
[ "$MEM_COUNT" -gt 0 ] && R="pass" || R="warn"
check "memory files present ($MEM_COUNT files)" "$R"

echo ""

# --- 3. Skills ---
echo "🧩 Skills"
SKILL_COUNT=$(find "$OPENCLAW_DIR/workspace/skills" -name "SKILL.md" 2>/dev/null | wc -l)
[ "$SKILL_COUNT" -gt 0 ] && R="pass" || R="warn"
check "skills installed ($SKILL_COUNT skills)" "$R"

echo ""

# --- 4. Channel/Session Data ---
echo "📡 Channels & Sessions"
[ -d "$OPENCLAW_DIR/telegram" ] && R="pass" || R="warn"
check "telegram/ session data exists" "$R"

echo ""

# --- 5. Cron Jobs ---
echo "⏰ Cron Jobs"
CRON_COUNT=$(ls "$OPENCLAW_DIR/cron/"*.json 2>/dev/null | wc -l)
[ "$CRON_COUNT" -gt 0 ] && R="pass" || R="warn"
check "cron jobs present ($CRON_COUNT jobs)" "$R"

echo ""

# --- 6. Gateway ---
echo "🌐 Gateway"
if openclaw gateway status 2>/dev/null | grep -qi "running"; then
    check "gateway is running" "pass"
else
    check "gateway is running" "fail"
fi

echo ""

# --- 7. Connectivity ---
echo "🔗 Connectivity"
if openclaw status 2>/dev/null | grep -qi "ok\|connected\|online"; then
    check "openclaw status OK" "pass"
else
    check "openclaw status check" "warn"
fi

echo ""

# --- 8. Bot Response Test ---
echo "🤖 Bot Response"
echo "  ℹ️  Send a test message to your bot on Telegram/Discord"
echo "  ℹ️  Verify it responds within 30 seconds"

echo ""
echo "================================="
echo "Results: ✅ $PASS passed | ❌ $FAIL failed | ⚠️  $WARN warnings"
echo ""

if [ "$FAIL" -eq 0 ]; then
    echo "🎉 Migration looks good!"
    if [ "$WARN" -gt 0 ]; then
        echo "   (Check warnings above — they may be optional)"
    fi
else
    echo "🚨 $FAIL check(s) failed — review above and fix before going live"
fi
echo ""

chmod +x migration-check.sh
./migration-check.sh

🔍 OpenClaw Migration Self-Check
=================================

📁 Core Files
  ✅ openclaw.json exists
  ✅ credentials/ directory exists
  ✅ agents/ directory exists

📂 Workspace
  ✅ workspace/ exists
  ✅ SOUL.md exists (bot personality)
  ✅ MEMORY.md exists (long-term memory)
  ✅ USER.md exists (user profile)
  ✅ memory/ directory exists (daily logs)
  ✅ memory files present (15 files)

🧩 Skills
  ✅ skills installed (12 skills)

📡 Channels & Sessions
  ✅ telegram/ session data exists

⏰ Cron Jobs
  ✅ cron jobs present (3 jobs)

🌐 Gateway
  ✅ gateway is running

🔗 Connectivity
  ✅ openclaw status OK

🤖 Bot Response
  ℹ️  Send a test message to your bot on Telegram/Discord
  ℹ️  Verify it responds within 30 seconds

=================================
Results: ✅ 12 passed | ❌ 0 failed | ⚠️  0 warnings

🎉 Migration looks good!

# SSH เข้าเครื่องเก่า
ssh user@your-vps-ip

# ยืนยันว่า gateway หยุดแล้ว
openclaw gateway status

# ถ้ายังรันอยู่:
openclaw gateway stop

# (ทางเลือก) ลบ OpenClaw ออกจากเครื่องเก่า
# ⚠️ ทำเมื่อมั่นใจจริงๆ เท่านั้น!
# npm uninstall -g openclaw
# rm -rf ~/.openclaw

Why migrate?

There are plenty of reasons you might need to move an OpenClaw bot to a new machine — the VPS contract is up, you want something faster, you are bringing it home from the cloud, or you simply want to consolidate several bots onto one box.

The catch is that an OpenClaw bot is not a single program — it comes with config, credentials, memory, workspace, skills, cron jobs and session data, and all of it has to travel together. Move it incompletely and the bot forgets everything, or worse — it cannot send messages at all.

What you need

• The old machine: the Ubuntu VPS currently running OpenClaw
• The new machine: a Mac Studio (macOS) — or any new machine with Node.js 18+
• SSH access to both machines
• Enough free space on the new machine (check with du -sh ~/.openclaw)

PHASE 1 — OLD MACHINE (VPS Ubuntu)

Prepare and Back Up on the Old Machine

This one really matters — stop it first so nothing writes data while the backup is running.

# SSH into the old machine
ssh user@your-vps-ip

# Stop the gateway
openclaw gateway stop

# Confirm it has stopped
openclaw gateway status
# You should see: Gateway is not running

# Total size
du -sh ~/.openclaw

# Folder-by-folder breakdown
du -sh ~/.openclaw/*/

# Example output:
# 12M   ~/.openclaw/workspace/
# 4.0K  ~/.openclaw/credentials/
# 256K  ~/.openclaw/agents/
# 2.1M  ~/.openclaw/telegram/
# 80K   ~/.openclaw/cron/

OpenClaw ships with a backup command — use it instead of tarring things up yourself, because it knows what to include and what to skip.

# Create a backup and verify it
openclaw backup create --verify --output ~/

# You get a file along these lines:
# ~/2026-03-24T00-00-00.000Z-openclaw-backup.tar.gz

# Check the backup size
ls -lh ~/2026-03-24*.tar.gz

If you keep special files outside ~/.openclaw — a crontab, a systemd service, git credentials:

# Export crontab
crontab -l > ~/crontab-backup.txt

# Copy git credentials if you have them
cp ~/.git-credentials ~/git-credentials-backup 2>/dev/null

# Copy .env files if you have them
cp ~/.openclaw/.env ~/env-backup 2>/dev/null

# Record the OpenClaw version
openclaw --version > ~/openclaw-version.txt
npm list -g openclaw >> ~/openclaw-version.txt

PHASE 2 — TRANSFER BETWEEN MACHINES

Send the Data to the New Machine

Pick whichever suits you — both work:

# Option A: scp (the simplest) — run it from the new machine (Mac Studio)
scp user@your-vps-ip:~/2026-03-24*.tar.gz ~/Downloads/

# Option B: rsync (faster on large files, and it shows progress)
rsync -avz --progress user@your-vps-ip:~/2026-03-24*.tar.gz ~/Downloads/

# Option C: if both machines are on Tailscale
scp user@vps-tailscale-name:~/2026-03-24*.tar.gz ~/Downloads/

Bring the extra files across too (if you have them):

scp user@your-vps-ip:~/crontab-backup.txt ~/Downloads/
scp user@your-vps-ip:~/git-credentials-backup ~/Downloads/
scp user@your-vps-ip:~/openclaw-version.txt ~/Downloads/

PHASE 3 — NEW MACHINE (Mac Studio)

Install and Restore on the New Machine

# Install Node.js if it is not there yet (macOS)
brew install node

# Install OpenClaw (the same version as the old machine)
npm install -g openclaw

# Check the version
openclaw --version

# Verify the backup before restoring
openclaw backup verify ~/Downloads/2026-03-24*.tar.gz

# Restore — unpack into ~/.openclaw
# If ~/.openclaw does not exist yet (fresh install):
mkdir -p ~/.openclaw
tar -xzf ~/Downloads/2026-03-24*.tar.gz -C ~

# Check that everything arrived
ls -la ~/.openclaw/
ls -la ~/.openclaw/workspace/
ls -la ~/.openclaw/credentials/

Open the config and look over the paths that may need changing:

# Open the config
nano ~/.openclaw/openclaw.json

# What to check and fix:
# 1. workspace path — if it is hardcoded to /root/..., change it to /Users/yourname/...
# 2. hostname/IP — if the gateway is bound to the old IP
# 3. gateway port — if the new machine already uses that port
# 4. tools path — e.g. the path to python, docker, etc.

# Git credentials (if any)
cp ~/Downloads/git-credentials-backup ~/.git-credentials

# Crontab — fix the paths before importing
# Read it first:
cat ~/Downloads/crontab-backup.txt
# Fix the paths, then import:
crontab ~/Downloads/crontab-backup.txt

# Start the gateway
openclaw gateway start

# Check the status
openclaw gateway status

# Read the logs for errors
openclaw logs --tail 50

🔍 Self-Check — Let the Bot Check Itself

This is the most important part — once the move is done, run a script that confirms everything is present. It works whether you run it yourself or hand it to the bot.

The automated self-check script

Create a file called migration-check.sh:

#!/bin/bash
# ============================================
# OpenClaw Migration Self-Check
# The bot has moved — make sure nothing was left behind
# ============================================

PASS=0
FAIL=0
WARN=0
OPENCLAW_DIR="$HOME/.openclaw"

check() {
    local label="$1"
    local result="$2"
    if [ "$result" = "pass" ]; then
        echo "  ✅ $label"
        ((PASS++))
    elif [ "$result" = "warn" ]; then
        echo "  ⚠️  $label"
        ((WARN++))
    else
        echo "  ❌ $label"
        ((FAIL++))
    fi
}

echo ""
echo "🔍 OpenClaw Migration Self-Check"
echo "================================="
echo ""

# --- 1. Core Files ---
echo "📁 Core Files"
[ -f "$OPENCLAW_DIR/openclaw.json" ] && R="pass" || R="fail"
check "openclaw.json exists" "$R"

[ -d "$OPENCLAW_DIR/credentials" ] && R="pass" || R="fail"
check "credentials/ directory exists" "$R"

[ -d "$OPENCLAW_DIR/agents" ] && R="pass" || R="fail"
check "agents/ directory exists" "$R"

echo ""

# --- 2. Workspace ---
echo "📂 Workspace"
[ -d "$OPENCLAW_DIR/workspace" ] && R="pass" || R="fail"
check "workspace/ exists" "$R"

[ -f "$OPENCLAW_DIR/workspace/SOUL.md" ] && R="pass" || R="fail"
check "SOUL.md exists (bot personality)" "$R"

[ -f "$OPENCLAW_DIR/workspace/MEMORY.md" ] && R="pass" || R="warn"
check "MEMORY.md exists (long-term memory)" "$R"

[ -f "$OPENCLAW_DIR/workspace/USER.md" ] && R="pass" || R="warn"
check "USER.md exists (user profile)" "$R"

[ -d "$OPENCLAW_DIR/workspace/memory" ] && R="pass" || R="warn"
check "memory/ directory exists (daily logs)" "$R"

MEM_COUNT=$(ls "$OPENCLAW_DIR/workspace/memory/"*.md 2>/dev/null | wc -l)
[ "$MEM_COUNT" -gt 0 ] && R="pass" || R="warn"
check "memory files present ($MEM_COUNT files)" "$R"

echo ""

# --- 3. Skills ---
echo "🧩 Skills"
SKILL_COUNT=$(find "$OPENCLAW_DIR/workspace/skills" -name "SKILL.md" 2>/dev/null | wc -l)
[ "$SKILL_COUNT" -gt 0 ] && R="pass" || R="warn"
check "skills installed ($SKILL_COUNT skills)" "$R"

echo ""

# --- 4. Channel/Session Data ---
echo "📡 Channels & Sessions"
[ -d "$OPENCLAW_DIR/telegram" ] && R="pass" || R="warn"
check "telegram/ session data exists" "$R"

echo ""

# --- 5. Cron Jobs ---
echo "⏰ Cron Jobs"
CRON_COUNT=$(ls "$OPENCLAW_DIR/cron/"*.json 2>/dev/null | wc -l)
[ "$CRON_COUNT" -gt 0 ] && R="pass" || R="warn"
check "cron jobs present ($CRON_COUNT jobs)" "$R"

echo ""

# --- 6. Gateway ---
echo "🌐 Gateway"
if openclaw gateway status 2>/dev/null | grep -qi "running"; then
    check "gateway is running" "pass"
else
    check "gateway is running" "fail"
fi

echo ""

# --- 7. Connectivity ---
echo "🔗 Connectivity"
if openclaw status 2>/dev/null | grep -qi "ok\|connected\|online"; then
    check "openclaw status OK" "pass"
else
    check "openclaw status check" "warn"
fi

echo ""

# --- 8. Bot Response Test ---
echo "🤖 Bot Response"
echo "  ℹ️  Send a test message to your bot on Telegram/Discord"
echo "  ℹ️  Verify it responds within 30 seconds"

echo ""
echo "================================="
echo "Results: ✅ $PASS passed | ❌ $FAIL failed | ⚠️  $WARN warnings"
echo ""

if [ "$FAIL" -eq 0 ]; then
    echo "🎉 Migration looks good!"
    if [ "$WARN" -gt 0 ]; then
        echo "   (Check warnings above — they may be optional)"
    fi
else
    echo "🚨 $FAIL check(s) failed — review above and fix before going live"
fi
echo ""

Run the script:

chmod +x migration-check.sh
./migration-check.sh

What you should see

🔍 OpenClaw Migration Self-Check
=================================

📁 Core Files
  ✅ openclaw.json exists
  ✅ credentials/ directory exists
  ✅ agents/ directory exists

📂 Workspace
  ✅ workspace/ exists
  ✅ SOUL.md exists (bot personality)
  ✅ MEMORY.md exists (long-term memory)
  ✅ USER.md exists (user profile)
  ✅ memory/ directory exists (daily logs)
  ✅ memory files present (15 files)

🧩 Skills
  ✅ skills installed (12 skills)

📡 Channels & Sessions
  ✅ telegram/ session data exists

⏰ Cron Jobs
  ✅ cron jobs present (3 jobs)

🌐 Gateway
  ✅ gateway is running

🔗 Connectivity
  ✅ openclaw status OK

🤖 Bot Response
  ℹ️  Send a test message to your bot on Telegram/Discord
  ℹ️  Verify it responds within 30 seconds

=================================
Results: ✅ 12 passed | ❌ 0 failed | ⚠️  0 warnings

🎉 Migration looks good!

Let the Bot Check Itself Over Chat

Once the gateway is up, message the bot on Telegram and ask it to run the checks for you:

If the bot answers all six, memory, config, credentials and the channel all made the trip. If it cannot remember you or cannot read the files, the workspace path is still wrong.

Cleaning Up the Old Machine

Once you are confident the new machine is behaving (after a day or two of real use):

# SSH into the old machine
ssh user@your-vps-ip

# Confirm the gateway is stopped
openclaw gateway status

# If it is still running:
openclaw gateway stop

# (Optional) Remove OpenClaw from the old machine
# ⚠️ Only once you are truly sure!
# npm uninstall -g openclaw
# rm -rf ~/.openclaw

Troubleshooting

❌ The bot does not answer on Telegram

• Check that the gateway is running: openclaw gateway status
• Read the logs: openclaw logs --tail 100
• The Telegram session may have expired — log in again: openclaw channels login telegram

❌ The bot has forgotten everything

• Check the workspace path in the config: cat ~/.openclaw/openclaw.json | grep workspace
• Check that MEMORY.md is where it should be: ls ~/.openclaw/workspace/MEMORY.md

❌ Skills do not work

• Skills with a binary dependency (python, docker, and so on) need that dependency installed on the new machine too
• On macOS you may need brew install python3 docker

❌ Cron jobs do not run

• Check them: openclaw cron list
• If the job uses the system crontab (not OpenClaw's cron), import the crontab separately
• Fix the paths in the crontab so they match the new machine

"A good migration is one where nobody notices anything changed — except the server bill."