Migration

Move your complete OpenClaw workspace to a new machine — new laptop, server, or OS reinstall.

When You Need Migration

  • Switching to a new laptop or desktop
  • Moving from a local machine to a cloud server (or vice versa)
  • Reinstalling your OS
  • Setting up a second machine with the same workspace

What Transfers

By default, Clawon migrates your workspace markdown, skills, canvas data, and agent configs. Credentials are always excluded. See the Security page for the full list.

Optionally include:

  • --include-sessions — chat history (agents/*/sessions/)
  • --include-memory-db — SQLite memory search index

Method 1: Cloud Migration

The easiest way — back up to the cloud on your source machine and restore on the destination.

On the source machine

# Log in (if not already)
npx clawon login

# Create a full backup with optional extras
npx clawon backup --include-sessions --include-memory-db --tag "migration"

On the destination machine

# Install OpenClaw first (if not already installed)
# Then log in to Clawon with the same account
npx clawon login

# Restore
npx clawon restore

That's it. Your workspace, skills, memory, and config are now on the new machine.

Method 2: Local Migration

No cloud required — create a local backup, transfer the file, and restore.

On the source machine

# Create a local backup with everything
npx clawon local backup --include-sessions --include-memory-db --tag "migration"

# Find the backup file
npx clawon local list

Transfer the file

# SCP to remote machine
scp ~/.clawon/backups/backup-*.tar.gz user@new-machine:~/

# Or copy to USB drive, cloud storage, etc.

On the destination machine

# Restore from the transferred file
npx clawon local restore --file ~/backup-2026-03-09T1030.tar.gz

Post-Migration Checklist

  1. Run npx clawon discover to verify files are in place
  2. Run npx clawon status to check connection and workspace
  3. Re-enter credentials if needed (credentials are never migrated)
  4. Start OpenClaw and verify memory search works

Credentials are never migrated. API keys, tokens, and auth files stay on the source machine. You'll need to re-enter them on the destination. See Security for details.

Having trouble? Check the Troubleshooting guide.