Migration Hero
Migration Hero copies an existing site from an external server onto a TurboStack host, guiding you through the process with a step-by-step wizard. It transfers the configuration, files and database for a fast setup with minimal effort.
Note
To move a site from one TurboStack host to another, use Account Cloning instead of Migration Hero.
Before you start
The destination application must already exist and have completed a successful Save & Publish at least once. Migration Hero copies data into an existing account; it does not create one for you.
You also need valid SSH credentials for the remote source (a password or an SSH key). Without them, TurboStack cannot connect to copy the data and databases.
Opening Migration Hero
- Open the host you want to migrate into.
- Go to the Applications tab.
- Select Migration Hero.
Running the wizard
Migration Hero is a three-step wizard.
1. Source Information
Describe the remote server you are migrating from:
Then provide the credentials for the method you chose:
- Password - enter the password for the remote user, then click Next.
- SSH key - click Generate SSH Key, add the generated public key to the
.ssh/authorized_keysfile of the remote user on the source server, then click Next.
2. Destination app
Choose the destination account on this host that will receive the site. This must be an existing account.
Then select what to migrate using the toggles:
- Clone files - copy the application files.
- Clone database - copy the database.
Enable one or both, then click Next.
3. Destination VHost
For each application, set the hostname(s) it should listen on and choose the certificate type to generate (for example letsencrypt). When you are done, click Start Import to begin the migration.
A migration progress popup appears in the bottom-right corner. When it finishes, the migration is complete.
What Migration Hero changes
Migration Hero only copies the data and database(s) from the remote host. It makes no changes on the remote system, so your source server keeps running untouched.
Note
Because the migration is a copy, you can safely test the result on the destination before switching any traffic away from the original server.