payless.host
Free migration: what hosts actually move for you
Updated Nov 22, 2026
What free migration means
Free migration means the hosting provider moves your site from your old host to their servers at no charge. What actually gets moved varies. Most providers transfer files, databases, and email accounts. DNS records, SSL certificates, and domain registration stay where they are — you handle those separately.
The service is managed, not automated. You supply credentials to your old host, and their migration team does the work. Turnaround is typically one to three business days.
Step 1: Check what your new provider will move
HostGator states it migrates one website free on the Business plan, which costs 6.25 USD per month for the first three years. DreamHost includes free automated WordPress migration on all shared plans, starting at 2.89 EUR per month.
Read the migration policy before you buy. Some providers limit free migration to the first thirty days after signup. Others charge for additional sites or for moves from certain platforms. If your site runs on custom code rather than WordPress, ask whether that is supported.
Step 2: Prepare credentials for your old host
The migration team will need FTP or cPanel access to your current hosting account, plus database credentials if your site uses one. Do not change your DNS yet — your site stays live on the old host until the move completes.
Create a temporary user if your control panel allows it. Give the migration team only the access they need, and delete the account once the transfer finishes.
Step 3: Request the migration
Most providers start the migration through a form in your account dashboard or a ticket to their support desk. You will provide the credentials from step two, along with your domain name and the type of site being moved.
Hostinger handles migrations through its support chat. InterServer, which charges 2.50 USD per month initially then 7.00 after one month, assigns migrations to a dedicated team accessed through the client area.
Response time varies. Expect an acknowledgment within a few hours and completion within one to three days for a standard WordPress or cPanel site.
Step 4: Verify the migrated site before switching DNS
Once the provider confirms the migration is complete, preview the site on the new server before you point your domain to it. Most hosts provide a temporary URL or instructions for modifying your computer's hosts file to view the migrated copy.
Check every page. Log into your admin panel. Submit a contact form. Test any shopping cart or membership features. If the site uses a database, verify recent posts or orders appear. Look for broken images, missing plugins, or formatting problems.
If something is missing or broken, open a ticket immediately. Do not proceed to DNS changes until the site works as it did on the old host.
Step 5: Update DNS and wait for propagation
Log into your domain registrar — Namecheap, SherlockHost, or whoever you bought the domain from — and update the nameservers to the ones your new host provided. This is separate from the hosting account; the migration does not change DNS automatically.
Propagation takes anywhere from one hour to forty-eight. During this window, some visitors see the old site and some see the new one, depending on which DNS server their internet provider is using. Do not delete anything from your old host yet.
Step 6: Verify email still works
If you use email addresses at your domain, send and receive a test message after DNS propagation completes. Migration typically copies email accounts but not the messages themselves — you may need to reconfigure your mail client to fetch older emails from the previous server via IMAP.
Some providers do not migrate email at all. If your new host does not offer email, or if you want to keep email separate, point only the A record to the new server and leave the MX records aimed at your old host or at a dedicated email service.
What can go wrong
Files transfer reliably. Database content occasionally does not, especially if character encoding differs between old and new servers. Preview carefully.
SSL certificates do not migrate. Your new host will issue a fresh one, but there may be a gap of a few minutes to a few hours after DNS switches during which visitors see a certificate warning. For most sites, this is unavoidable and brief.
Custom server configurations — modified .htaccess rules, cron jobs, specific PHP versions — are not copied automatically. If your site depends on settings you changed manually, document them before migration and replicate them afterward.
