HestiaCP is a management panel that allows you to manage websites, email accounts and databases among others and it is also open source.
If you want to migrate content from a server with HestiaCP to another server with HestiaCP, you can follow these simple steps.
Migrating a backup from HestiaCP to HestiaCP
The first thing to do is to create a new backup. The backups must be generated by user, we will access with our user and then we will go to the Backups tab:
Click on the + symbol to create a new backup. In a matter of minutes we will have a new backup created -the time will depend on how much your webs occupy and how many webs you have with that user-.
Now we will connect by SSH to the origin HestiaCP server using Putty and we will execute the following to copy the created backup to copy it to the new HestiaCP server:
ssh root@[IP_SERVIDOR_DESTINOHESTIACP] "mkdir -p /backup" 2> /dev/null
scp /backup/Clouding.2024-11-13_17-15-02.tar root@[IP_SERVIDOR_DESTINOHESTIACP]:/backup
Now we will connect via SSH to the HestiaCP server and run the following to import the backup:
v-restore-user clouding Clouding.2024-11-13_17-15-02.tar
We must make sure that the name of the backup.tar is the same that we have copied previously to the HestiaCP server.
Once imported, we should see a terminal output similar to this one:
-- WEB -- 2024-11-14 12:09:54 test.example.com 2024-11-14 12:09:54 miweb.com -- DNS -- 2024-11-14 12:09:54 test.example.com -- MAIL -- 2024-11-14 12:09:55 test.example.com -- DB -- 2024-11-14 12:09:55 Clouding_basesdedatos 2024-11-14 12:09:56 Clouding_default 2024-11-14 12:09:56 Clouding_wp -- CRON -- 2024-11-14 12:09:57 8 cron jobs -- USER FILES -- 2024-11-14 12:09:57 .sudo_as_admin_successful 2024-11-14 12:09:57 .bash_logout 2024-11-14 12:09:57 .bashrc 2024-11-14 12:09:57 .profile 2024-11-14 12:09:57 tmp
And with this we will have our user of the old HestiaCP imported to our new server with HestiaCP.
Important data to keep in mind
This migration only copies the content from one user to another with the same name. If you want to change the user name later, you can do it with the v-change-domain-owner command to change a domain to another domain. This change only changes the web files, but the database remains with the original user. To change the database, the v-change-database-owner command must be used (and the web configuration files must be updated since the user will change). On the other hand, the FTP users will stop working, so you must delete them with the v-delete-web-domain-ftp command and recreate the users again.