coolify-migrate

Coolify VPS Migration

You are running on the source VPS. You access the destination VPS via SSH. The user should not need to run any commands — you execute everything and only ask for confirmation when necessary.

Before Starting

The only information you need from the user is the destination VPS IP (passed as $ARGUMENTS or asked interactively).

Destination IP: $ARGUMENTS

If no IP was provided, ask the user for it before proceeding.

Start by discovering the environment:

# Source VPS IP
hostname -I

# Services running on Coolify
docker ps --format '{{.Names}}\t{{.Image}}'

From the docker ps output, identify which services exist (n8n, Chatwoot, Evolution API, etc.) and automatically skip phases that don't apply — don't ask, just skip.

Migration Phases

Execute the phases sequentially. Complete each phase before moving to the next. At the end of each phase, summarize what was done and what comes next.

Phase	Description	Reference
1	Configure SSH access to destination VPS	phase-1-ssh.md
2	Backup everything (databases, Redis, Coolify)	phase-2-backup.md
3	Collect encryption keys	phase-3-keys.md
4	Transfer data to the new VPS	phase-4-transfer.md
5	Install and restore Coolify on destination	phase-5-install.md
6	Restore service-specific data	phase-6-restore.md
7	Verification and testing	phase-7-verify.md
8	Repoint DNS and shut down old server	phase-8-dns.md

Read each phase file when you reach that phase. Do NOT read all phases at once.

General Behavior

• Respond in the user's language. Detect which language the user writes in and use that same language for all output, summaries, and questions.
• Execute commands directly in the terminal. Do not ask the user to run them.
• Commands on the destination VPS: execute via ssh root@DEST_IP "command".
• Discover services automatically via docker ps. Skip inapplicable phases without asking.
• Ask for user confirmation only for: irreversible actions, steps requiring the web panel (Coolify dashboard, DNS updates), and browser-based verifications.
• If something fails, analyze the error message and try to resolve it. Do not repeat the same command without understanding what went wrong.
• Summarize at the end of each phase: what was done and what comes next.
• Warn about risks before executing any destructive command.