Support-Assisted Migration

Last updated July 31, 2026

Our support team can migrate your project to Hostman for you—whether you're moving from another provider or between servers within Hostman.

What's Included
Copy link

As part of a support-assisted migration, we'll:

  • Install a control panel, if needed.
  • Copy your site files.
  • Copy your database.
  • Connect the database to your site.
  • Migrate cron jobs, if they're explicitly listed in your request.

Supported Technologies
Copy link

We can migrate projects built with:

  • PHP
  • Node.js
  • Python
  • Ruby

We don't migrate:

  • Projects built with ASP.NET.
  • Projects built with website builders.
  • Mail servers.
  • Bots.
  • Applications running in Docker containers.

If your project uses a different stack, check with our support team to confirm whether migration is possible.

If your project requires code changes or configuration updates to run correctly on the new server, you'll need to make those changes yourself or with the help of a third-party specialist.

How Migration Works
Copy link

We migrate projects one of two ways, depending on your setup. 

Option 1: Full Disk Image
Copy link

This works for any type of project and keeps your existing environment intact—including custom configurations, installed software, and system-level settings.

To migrate this way, one of the following needs to be true:

  • You can provide a server image in one of these formats: raw, qcow2, qed, qcow, luks, vdi, vmdk, vpc, vhdx.
  • You can grant us access to your current provider's dashboard, with the ability to create and mount backups.
  • You can grant us access to your current provider's dashboard, with the ability to boot from a recovery disk.

In the last case, your original server will experience some downtime during the transfer—how long depends on the size of your disk.

Steps:

  1. We copy your disk image.
  2. We deploy the disk image and set up your site on a temporary domain.
  3. You check that everything works correctly on the temporary domain.
  4. You point your domain to the new server.

Option 2: Site Files and Database
Copy link

This option is only available if the destination server has a control panel installed (for example, FASTPANEL or HestiaCP). If your project needs specific environment tuning, you'll need to handle that yourself or bring in a third-party specialist.

  1. We copy your site files and database.
  2. We deploy your site on a temporary domain.
  3. You check that everything works correctly on the temporary domain.
  4. You point your domain to the new server.

Requesting a Migration
Copy link

To request a migration, message our support team via the chat in your dashboard or email us from the address registered to your account.

If you're migrating from another provider, first sign up for Hostman and create a server—you'll need somewhere to migrate to before we can get started.

If you're migrating between two Hostman accounts, submit your request from the source account. We'll then reach out to confirm the transfer with the destination account.

In your request, include:

  • The IP address of the source server.
  • SSH or FTP login credentials (if using FTP, also include database access details—for example, phpMyAdmin credentials). 
  • The file path on the source server.
  • Login credentials for the destination server.

We'll confirm the estimated migration time in the chat. If any complications come up, we may need more time—we'll let you know if that happens.

Once we notify you that your project has been deployed, check that it's working correctly, then migrate your domain following our domain setup guide. 

If you're migrating between two Hostman accounts, move the domain to the destination account and point its A record to the new server's IP address. If the domain uses Hostman nameservers, you can do this from the Domains & SSL section. Otherwise, you'll need to do this from your nameserver provider's dashboard.

After Migration
Copy link

Once migration is complete, your project will reflect its state at the time we received your request. If you notice anything different about how your migrated site behaves compared to the original, contact us within 14 days. We can make corrections as long as a backup from the original platform is still available.

We also strongly recommend changing your root password after migration.