Independent software research. Some links may earn us a commission at no extra cost to you. Learn more →

Independent analysis. This page may contain affiliate links.

Website Migration Guide: Move Your Site Without Losing Traffic

Migrating a website, whether to a new host or a new domain, is routine when it is planned and painful when it is not. The goal is simple: keep every page working and keep your rankings intact.

This guide walks through planning, backing up, transferring files and databases, handling DNS, testing, and monitoring SEO after the switch.

Quick comparison table

Option	Best for	Starting price
All-in-One WP Migration	Simple WordPress moves	Free; paid extensions
Duplicator	Backup and migrate WordPress	Free; Pro paid
WPvivid	Backup, migration, and staging	Free tier; paid plans
Migrate Guru	Large or tricky WordPress sites	Free
rsync and mysqldump	Server-level transfers	Free; hosting cost only

Plan the migration before you touch anything

Write down what is moving and what must stay the same: files, databases, email, DNS, and any third-party integrations. Identify the pages that generate the most traffic or revenue, because those are the ones you cannot afford to break.

Choose a low-traffic window and tell affected stakeholders. A clear plan turns a stressful weekend into a routine task.

Icode editorial illustration (image: icode.io.vn)

Back up everything

Take a full backup of files and databases and store copies off the server you are leaving. Test that the backup can actually be restored; an untested backup is a hope, not a safety net.

Also record your current DNS settings, email configuration, and any API keys before you make changes, so you can revert if something goes wrong.

Set up the destination environment

Provision the new host, create the database, and confirm the software stack matches your site’s requirements. If you can, build the site on a temporary URL or staging domain first.

Test the site on the new server before switching anything live. Fixing problems there is far easier than firefighting after the DNS change.

Move files and the database

Transfer your files and import the database, then update configuration files with the new database credentials and URLs. For WordPress, many people use a migration plugin, while larger or non-WordPress sites often use rsync and mysqldump.

Search for hard-coded old URLs in the database and replace them with the new ones. Broken links and mixed URLs are a common cause of post-migration SEO problems.

Handle DNS and email carefully

DNS changes propagate, so lower your time-to-live (TTL) values a day in advance to speed the switch. Update the A records to point to the new server when the site is ready.

Treat email separately. Create the mailboxes on the new provider first, then update MX records. Never point MX records at a host before the mailboxes exist, or you will lose mail.

Test thoroughly before going live

After the switch, check the key pages, forms, checkout, and logins on both desktop and mobile. Verify redirects, SSL certificates, and that no mixed-content warnings appear.

Ask a few people on different networks to confirm the site loads correctly. A second pair of eyes catches problems you have already stopped noticing.

Monitor SEO after the switch

Submit an updated sitemap and keep the old URLs working with 301 redirects where anything changed. Watch Search Console for coverage errors and ranking shifts over the following weeks.

If rankings dip briefly, that is usually normal, but a sustained drop points to redirects, missing pages, or crawl errors that need attention.

Pros

A planned migration preserves rankings and uptime
Backups protect against data loss
Testing on the new server catches issues early
Migrations are a good moment to improve performance

Cons

Downtime and missteps can cost traffic
DNS and email changes are easy to get wrong
Some builders use shortcodes that complicate moves

Frequently asked questions

Will migrating my site hurt SEO?

Not if it is done carefully. Keep URLs identical, use 301 redirects for any that change, update your sitemap, and transfer all content. Most ranking loss comes from changed URLs or long downtime.

How long does a migration take?

A small static or WordPress site can migrate in under an hour. Larger sites, custom databases, or complex email setups may take a day or more, plus DNS propagation time.

Should I change hosts and domain at the same time?

Avoid it if you can. Changing both at once makes it harder to tell what caused any problem. Move the host first, confirm everything works, then change the domain if needed.

How do I migrate email?

Email is separate from the website. Set up the same mailboxes on the new provider, then update MX records when ready. Never point MX records at the new host until the mailboxes exist.

Verdict

A clean migration is 90 percent preparation. Back up, test on the new server, move files and data carefully, handle DNS and email in the right order, and monitor search performance afterward. Do that and your visitors will never notice the move; skip it and you will spend weeks repairing rankings.