Migrating a site to another server is needed when changing plans, moving to a different location, or consolidating several servers into one. ISPmanager 6 has a built-in migration module, but for non-standard cases it is often easier to move the site manually. Here are both approaches.
When you need a server-to-server migration
Typical reasons: the server is hitting CPU and memory limits, the client is moving to a VDS in a larger location, for example from Germany to the US, or several sites on one server need to be split across different ones. Before migrating any site, check the current PHP version and the list of installed extensions — they must match on the new server.
Migration methods: module or manual
| Method | Pros | Cons |
|---|---|---|
| Built-in migration module | Moves the site, database, and mail in one job | Requires ISPmanager 6 on both servers |
| Manual transfer with rsync and mysqldump | Works between any panels and without a panel | More manual steps, higher risk of error |
The built-in module is convenient when moving between two ZevsHost servers running ISPmanager 6. The manual method is needed when the target server runs a different panel or no panel at all.
Migration through the migration module
On the source server, open "Tools" → "Data migration" and enter the IP address and admin credentials of the target server. The module transfers the site files, database dump, and mailbox settings on its own, preserving the directory structure and access rights.
After the job finishes, compare checksums of key files and open the site by the target server's IP before switching DNS.
Manual migration: files and database
For a manual migration, sync the site's home directory over SSH and take a database dump:
rsync -avz -e ssh /var/www/httpd-cts/site_ru/ root@new-server:/var/www/httpd-cts/site_ru/
mysqldump -u site_user -p site_db > site_db.sqlMove the database dump to the new server and load it into a pre-created empty database with the same username and password, so you do not have to edit the site's configuration files:
mysql -u site_user -p site_db < site_db.sqlIf the site uses caching through Redis or Memcached, clear the cache again after the migration — old keys point to the previous server. Cache setup is covered in the article about Redis and Memcached in ISPmanager 6.
DNS and minimizing downtime
Lower the TTL of the domain's A and MX records to 300 seconds a day before the migration — this way DNS updates propagate to clients faster. Right after verifying the site on the new server, switch the A record and wait out the old TTL before turning off the site on the source server.
How to edit domain records is covered in detail in the article about DNS zones in ISPmanager 6.
Checking the result after migration
After switching DNS, check the usual trouble spots:
- Whether the site opens over HTTPS, not only over HTTP
- Whether the PHP version and enabled extensions match the source server
- Whether mail arrives on the new server and is not duplicated on the old one
- Whether cron jobs moved together with the account still run
- Whether any old DNS records still point to the previous IP
Bottom line: the built-in ISPmanager 6 migration module covers most transfers between your own servers, while the manual method with rsync and mysqldump remains a universal fallback for switching panels or providers.