Most website migrations fail not because the steps are hard, but because people rush them. The technical moves—backing up files, transferring databases, updating DNS—are straightforward. The failure points are impatience, missing backups, and cancelling the old host too soon.
This guide walks through the migration in the order that prevents downtime. Whether you do it yourself or hand it to your new provider, knowing the sequence keeps you in control.
Who should use this guide
- Site owners with minimal technical experience**: Let the new host handle it. Most major providers offer free migration assistance—use it.
- Busy site owners with little free time**: Same advice. The time savings outweigh any cost of DIY pride.
- Resellers and technical users doing it manually**: Follow the steps in order. The sequence matters more than the tools.
Step 1: Research and shortlist
Pick a host that fits your actual workload. Look for the features you use, not the longest feature list. Scalability matters more than people expect—most migrations happen because the old host has hit a wall.
Ask every candidate whether they offer free migration assistance. In a competitive market, this service is increasingly common and worth requesting before committing.
Step 2: Sign up and capture the new account details
Once the new plan is active, record the new nameservers, FTP credentials, database host, and control panel URLs in a single document. The single most common migration mistake is mixing up which credentials belong to which host.
Step 3: Back up everything
Full backup of files and databases at the old host, before anything else moves. Keep a copy off the server entirely. If the migration goes wrong, this is your only safety net.
Step 4: Move the files
Three options depending on your comfort level:
| Method | Best for | Limitations |
|---|---|---|
| FTP client (FileZilla) | Most technical users | Requires basic FTP knowledge |
| Web-based file manager | Small files, quick moves | Slow for large sites |
| Host migration tool | Speed, minimal effort | Not offered by all hosts |
For anything over a few hundred megabytes, an automated migration tool is usually faster and less error-prone than manual file moves.
Step 5: Migrate the databases
Export from the old host with phpMyAdmin or mysqldump, then import at the new host. If the new host uses a different database name or prefix, update the application's config file. WordPress sites typically need wp-config.php updated with the new database name, user, and password.
Step 6: Update DNS
Lower the TTL on the domain a day or two before the move if you control the registrar. Then point the nameservers to the new host, or update the A record if DNS is managed elsewhere. DNS propagation varies widely—it can take a few hours to several days.
Step 7: Test, test, test
Once propagation is in progress, hit the site using the new host's temporary URL or IP address to bypass DNS. Check pages, forms, logins, checkout flows, and admin areas. Verify that email is delivering and that SSL is active. Only after the site behaves correctly should the old hosting be cancelled.
Our analysis
DNS propagation is the biggest variable in any migration, and most avoidable pain comes from rushing it. The professional move: lower TTL ahead of time, schedule the cutover for a low-traffic window, and keep the old hosting live for at least a week after DNS changes so the new host can be validated against real traffic.
For resellers, a migration done cleanly is a relationship-building moment. Clients who see a smooth cutover with no downtime tend to renew and upgrade. Clients who experience a 24-hour outage tend to leave at the first opportunity. Building a written runbook and reusing it is what separates one-time migrations from repeatable service quality.
Bottom line
A website migration is mostly patience. Back up everything first, follow the steps in order, lower the TTL ahead of time, keep the old host live during propagation, and test before cancelling anything. The boring plan is the one that works.
Key takeaways
- Back up files, databases, and email before touching anything else.
- Ask the new host about free migration assistance before doing it manually.
- Lower DNS TTL 48 hours before the move to speed up propagation.
- Keep the old hosting active for at least a week after DNS changes.
- Only cancel the old host after the new site has been tested and confirmed stable.
Frequently asked questions
How long does a website migration take?
The technical steps take a few hours for a typical site. DNS propagation can add several days on top of that.
Should I let the new host migrate the site for me?
If the provider offers free migration assistance, use it. The risk of self-inflicted downtime is higher than any savings from doing it yourself.
When is it safe to cancel the old hosting?
Only after the new site has been live and stable on the new host for at least a week, and after DNS has fully propagated.
Do I need to move email too?
Yes. Create mailboxes on the new host first, then update MX records as part of the DNS change. Verify sending and receiving before cancelling the old host.