Documentation / Moving to Saka
Moving to Saka
Already have a site, app, or AI assistant somewhere else? Saka moves it from the panel, without reinstalling from scratch. The old place is not changed until you are sure, and data travels directly between servers.
Where you can move from
| From | What moves | Where to click |
|---|---|---|
| cPanel or other hosting | Site files and database. WordPress addresses are updated to the new domain. Sign in to the old cPanel or upload a backup file. | Sites > Create a site > Move from cPanel. Guide |
| Another Saka server (sites) | Site content, database, PHP settings, SFTP accounts. PHP and WordPress can be upgraded on the way. | Site page > Move to another server card. Guide |
| OpenClaw | Memory, sessions, settings, AI keys, channel credentials (Telegram/WhatsApp), and workspace. Works for installs made by Saka and for ones you set up yourself before Saka. | Old server page > OpenClaw > Move to another server. Guide |
| Hermes Agent | Same as OpenClaw: memory, skills, sessions, settings, AI keys, and the bot. A self-installed Hermes is detected automatically. | Old server page > Hermes > Move to another server. Guide |
| Dokploy | Git, Docker image, and Compose apps with their variables, domains, and volume data. Databases used by a Git app move with the same host name, credentials, and data. | Dokploy server page > Dokploy card > Move its apps to Saka. Guide |
| Coolify | Repo apps (Nixpacks, Dockerfile, static), Docker image, Docker Compose, and one-click services with their variables, domains, and volume data. Databases used by a Git app move too. | Coolify server page > Coolify card > Move its apps to Saka. Guide |
| aaPanel | PHP, WordPress, and static sites: files, their main database, and domains. The site keeps running while it is copied. PHP 7.x/8.0/8.1 runs on PHP 8.2. | aaPanel server page > aaPanel card > Move its apps to Saka. Guide |
| CyberPanel | PHP and WordPress sites, including subdomains/child domains: files, their main database, and domains (with aliases). The site keeps running while it is copied. | CyberPanel server page > CyberPanel card > Move its apps to Saka. Guide |
| Dokploy, Coolify, aaPanel databases no Git app uses | PostgreSQL into a Saka PostgreSQL cluster, MySQL/MariaDB into a Saka MariaDB cluster, in one transaction; row counts are compared. The old database keeps running. | The same move dialog: tick the database and choose the target cluster. Guide |
| An existing database (PostgreSQL or MySQL 8) | Its contents are copied into a Saka managed database across locations; table and row counts are compared afterwards. | Database cluster page > Move an existing database into the cluster. Guide |
Saka recognises OpenClaw, Hermes, Dokploy, Coolify, aaPanel, and CyberPanel already on a server as soon as the agent is installed. They appear in the Found on this server card on the server page, each with its move button.
Saka does not offer a move just because it detects Dokploy, aaPanel, OpenClaw, and the like; you may only want to manage them. The offer appears when a new, still empty VM connects: a Move something to this server? card on that VM's page (you can close it) and one Telegram message, listing your other servers whose contents can move there.
What you need
- Two servers in the same Saka account. The old server stays on, and the new one has Saka installed. For Dokploy, Coolify, aaPanel, and CyberPanel the target must be another server, because those platforms hold ports 80/443 on theirs. OpenClaw and Hermes also go to another server, because one bot must never run twice.
- The new server can reach the old one. Data is sent directly through a temporary port on the old server that only accepts the new server's IP, with a one-time certificate. If a provider firewall (security group) blocks it, Saka names the port to open.
- Enough room on the new server. RAM and disk are checked before the move starts.
- Access to your domain's DNS to change the A record at the end.
The usual steps
- Install Saka on the old and the new server (Getting started). Saka does not change anything already running on the old server.
- Open the old server's page (or the site page). Pick what to move, the target server, and the domain. You may change the domain; variables that mention the old domain (such as
APP_URL) are updated too. - Follow the progress on the server page. Each step shows in the panel and the result is sent over Telegram.
- Change the A record of the domain to the new server's IP, then check the site or bot in its new home.
- Turn off the old one when you are sure. Saka never deletes apps on Dokploy, Coolify, aaPanel, CyberPanel, or the old cPanel.
What is guaranteed
- The old place is not changed. cPanel, aaPanel, CyberPanel, Dokploy, and Coolify keep running as before. Data changed there after the copy is not included, so move DNS soon after the move finishes.
- Short, clear pauses. A site goes into maintenance mode briefly while the last changes are copied. Compose apps and databases on Dokploy/Coolify pause briefly while their data is packed, then run again. OpenClaw and Hermes pause about 30 seconds for small data.
- A bot never runs twice. Two bots with the same Telegram token fight over messages, so the old bot is paused first. If any step fails, the old bot is started again automatically.
- Data does not pass through Saka Panel. Site content, volumes, and databases go straight between servers and are checked (SHA-256). Variables and keys read from the old platform pass through Saka Panel in memory only and are not stored.
- No API key for the old platform. Dokploy and Coolify apps are read straight from their internal database on that server, and their encrypted variables are opened with the platform's own key on the same server.
Not automatic yet
- Email hosting on cPanel (Saka deliberately does not host email).
- MongoDB and Redis databases that no Git app uses (PostgreSQL, MySQL, and MariaDB can already be copied into a cluster). Databases inside a compose app or one-click service move with that app.
- Node, Python, Go, or Java projects on aaPanel: use a Git app in Saka. aaPanel/CyberPanel FTP accounts are not carried over; Saka uses SFTP per site. CyberPanel email hosting is not either.
- Storage (volumes) of non-compose Dokploy/Coolify apps, Dokploy apps from a zip upload, and Coolify apps built from a Dockerfile typed into Coolify without a repo.
- Private repos that Dokploy/Coolify reached through a GitHub app: add the deploy key Saka shows after the move.
Each of these is listed as a note before you press the move button, so nothing is left behind silently. For bigger moves (for example from AWS or Google Cloud), our team can help through Migration consultation.
Through your AI agent
Every path above can also be run by your AI agent over MCP, always with your approval: situs_pindah_salin (sites between servers), aplikasi_pindah (OpenClaw and Hermes), dokploy_pindah (Dokploy; Coolify or aaPanel with platform: coolify, aapanel, or cyberpanel; databases into a cluster with klaster), and database_pindahkan_lama.