Migrate wordpress site to new host | Lillian Purge

Migrate wordpress site to new host

I have migrated more WordPress sites than I can count and I also run my own digital marketing firm, so I have seen every possible version of this process, done well, done badly and done in ways that quietly damage sites months later. In my opinion migrating a WordPress site to a new host is one of the most underestimated tasks in digital marketing and SEO. It is often treated as a technical chore rather than a strategic change that can affect performance, rankings, security and data integrity.

From experience most problems with WordPress migrations do not show up immediately. The site appears to load, pages look fine and everyone relaxes. Then weeks later rankings dip, emails stop working, forms break or tracking data goes missing. Almost always this traces back to ownership, preparation or process mistakes during the migration.

This article explains how to migrate a WordPress site to a new host properly. Not just how to move files and databases, but how to do it in a way that protects SEO, avoids data loss and gives you confidence that nothing critical has been missed. Everything here is written in fluent UK English, grounded in real world experience and designed to be practical rather than theoretical.

Why WordPress migrations go wrong so often

In my opinion WordPress migrations go wrong because they sit between disciplines.

They involve hosting, DNS, databases, PHP, email, SEO and analytics. Often no single person owns the full picture. Tasks get split, assumptions are made and small details fall through the cracks.

From experience the most common reason migrations fail is not lack of skill. It is lack of structure. People jump straight into copying files without understanding what needs to be preserved, what needs to change and what must remain consistent.

A good migration starts with clarity, not tools.

When migrating a WordPress site actually makes sense

Not every performance issue requires a host migration.

From experience migrations are usually justified when:

• The current host is slow or unreliable

• Support quality is poor

• Security standards are weak

• Scaling is limited

• Costs no longer make sense

Migrating for the sake of it, or because someone promised magical speed improvements, often creates unnecessary risk.

Before starting, you should be clear on why you are moving and what success looks like after the move.

SEO risk during a WordPress migration

SEO risk is real during migrations.

From experience rankings rarely disappear overnight, but subtle damage can occur if URLs, redirects, canonicals, robots rules or performance characteristics change.

Search engines are sensitive to inconsistency. If Google sees different behaviour before and after the migration, it reassesses trust.

A proper migration aims to make the move invisible to search engines and users alike.

Ownership before action

Before touching anything, ownership must be clear.

From experience you should know:

• Who owns the domain registrar

• Who controls DNS

• Who owns the hosting account

• Who owns Google Search Console

• Who owns analytics and tag management

If you do not have access to these, stop and resolve that first. Migrating without full access is how data and control get lost.

Full backups are non negotiable

This sounds obvious but it is often rushed.

From experience you need at least two backups before migrating:

• A full site files backup

• A full database backup

Ideally these should be stored independently of the existing host.

Never rely solely on the host backup system. If something goes wrong during migration you want complete control over recovery.

Understanding what actually makes up a WordPress site

A WordPress site is not just pages.

From experience it includes:

• Core WordPress files

• Theme files

• Plugin files

• Uploads and media

• The database

• Configuration files such as wp-config.php

Missing any of these leads to partial migrations that appear to work until something breaks.

Choosing the right migration approach

There is more than one way to migrate a WordPress site.

From experience the main approaches are:

• Manual migration

• Plugin based migration

• Host assisted migration

Each has advantages and risks. The right choice depends on site size, complexity and your level of access.

Manual migrations offer the most control but require confidence. Plugin migrations are convenient but can hide issues. Host assisted migrations vary in quality.

What matters is understanding what the method does behind the scenes.

Preparing the new hosting environment properly

The new host should be prepared before moving anything.

From experience this includes:

• Setting up the correct PHP version

• Configuring memory limits

• Creating the database

• Ensuring SSL support

• Setting correct file permissions

Rushing this step often leads to post migration errors that are harder to diagnose later.

Migrating files carefully

File migration should be complete and clean.

From experience common mistakes include:

• Missing hidden files

• Incomplete uploads

• Permission errors

Using SFTP rather than FTP is strongly recommended for security and reliability.

Once files are copied, permissions should be checked to ensure WordPress can read and write where necessary.

Migrating the database without corruption

The database is the heart of the site.

From experience database issues are responsible for many silent failures after migration.

When importing the database you must ensure:

• The import completes fully

• Character encoding remains correct

• No tables are missing

Large databases may require command line tools rather than browser based imports.

Updating wp-config.php correctly

The wp-config.php file tells WordPress how to connect to the database.

From experience mistakes here cause immediate site failure.

You need to update:

• Database name

• Database user

• Database password

• Database host

It is also a good opportunity to review security keys and salts.

Handling search and replace properly

URLs stored in the database often need updating.

From experience WordPress stores URLs in multiple places, some of which are serialised.

Naive search and replace can break data structures.

Always use tools that understand serialised data when updating URLs. This applies whether you are changing domains or just adjusting paths.

Migrating without changing the domain

If the domain stays the same, SEO risk is lower but not zero.

From experience you still need to ensure:

• URLs resolve correctly

• SSL certificates are active

• No mixed content issues appear

Search engines notice protocol changes and security warnings quickly.

Migrating with a domain change

Domain changes add complexity.

From experience this requires:

• Careful redirect planning

• Search Console updates

• Analytics updates

• Canonical checks

Domain migrations should never be rushed.

Every old URL should have a clear redirect path to its new equivalent.

DNS changes and timing

DNS changes control when traffic switches.

From experience DNS is one of the most misunderstood parts of migration.

You should:

• Lower TTL values in advance

• Understand propagation delays

• Schedule changes during low traffic periods

Testing the site on the new host before DNS changes is essential.

Testing before going live

Testing is where most problems are caught or missed.

From experience you should test:

• Page loading

• Forms and submissions

• Logins and user accounts

• Plugins and integrations

• Mobile behaviour

Testing should be done using a temporary URL or hosts file override so the live site remains unaffected.

Email and form handling

Email issues are extremely common after migrations.

From experience contact forms may stop sending or emails may be flagged as spam.

You should check:

• SMTP settings

• Form plugins

• SPF, DKIM and DMARC records

Email deliverability is often overlooked but critical for business continuity.

Analytics and tracking continuity

Tracking continuity matters for data integrity.

From experience migrations often break:

• Google Analytics

• Google Tag Manager

• Conversion tracking

You should verify tracking is firing correctly immediately after migration.

Lost data is rarely recoverable later.

Google Search Console checks

Search Console should be monitored closely after migration.

From experience check for:

• Crawl errors

• Indexing changes

• Coverage issues

If issues appear, they should be addressed quickly before they compound.

Performance validation after migration

One reason for migrating is often performance.

From experience you should validate:

• Page speed

• Server response times

• Core Web Vitals

If performance worsens, something is wrong and should be addressed immediately.

Common post migration SEO issues

SEO issues often appear subtly.

From experience common problems include:

• Canonicals pointing to old URLs

• Noindex tags added accidentally

• Robots.txt changes

• Duplicate content issues

These can quietly damage rankings if not caught early.

Redirect checks

Redirects should be checked thoroughly.

From experience broken or missing redirects are one of the most damaging migration errors.

Every important URL should resolve correctly with a single clean redirect.

Redirect chains should be avoided.

Ownership after migration

Once the site is live, ownership should be reviewed.

From experience migrations often change who has access to what.

Ensure:

• Domain access is correct

• Hosting access is documented

• Backups are configured

• Responsibilities are clear

This prevents future data issues.

Backup strategy on the new host

A new host means a new backup strategy.

From experience you should confirm:

• Backup frequency

• Storage location

• Restore process

Never assume backups are working without testing a restore.

Security checks post migration

Security should not be an afterthought.

From experience migrations can expose:

• Outdated plugins

• Weak permissions

• Missing updates

Running a security review after migration is best practice.

Plugin and theme compatibility

Some plugins behave differently on new environments.

From experience test:

• Caching plugins

• Security plugins

• Performance plugins

Conflicts may not appear immediately but can cause intermittent issues.

Cleaning up after migration

Migration is an opportunity to tidy up.

From experience this includes:

• Removing unused plugins

• Cleaning old themes

• Updating WordPress core

Doing this after the move rather than before reduces risk.

Monitoring in the weeks after migration

The work does not end on launch day.

From experience the first two to four weeks are critical.

You should monitor:

• Traffic trends

• Error logs

• User feedback

• Search Console messages

Early intervention prevents long term damage.

When to involve professionals

Not every migration should be DIY.

From experience complex sites, ecommerce stores or high traffic sites benefit from professional handling.

The cost of a failed migration often exceeds the cost of doing it properly upfront.

Common migration myths

There are several myths worth addressing.

From experience these include:

• Migrations always hurt SEO

• Plugins make it risk free

• Google reindexes everything instantly

• Speed improvements are guaranteed

None of these are universally true.

Good migrations are boring because nothing breaks.

Documentation and future proofing

Document what was done.

From experience documentation helps future troubleshooting and future migrations.

Record:

• Hosting details

• DNS changes

• Redirect rules

• Special configurations

This knowledge prevents repeat mistakes.

Final reflections from experience

I genuinely believe migrating a WordPress site to a new host is one of the most important digital maintenance tasks a business can undertake.

In my opinion the difference between a successful migration and a damaging one is not technical skill alone. It is preparation, clarity and respect for how interconnected systems are.

If you approach migration as a structured process rather than a quick move, you protect SEO, data and user trust.

Done properly, a migration is invisible to users and search engines. Done poorly, it creates months of confusion.

Take your time, test thoroughly and treat migration as a strategic change, not a technical chore.