WordPress Website Migration to New Hosting

The Problem

DIY WordPress migrations often miss something — a plugin's own database table, an .htaccess rule, uploaded files outside the standard folder — and you don't find out until a visitor reports it broken.

About this problem

A WordPress site is more than the files you can see in the dashboard. It includes the database, uploads, plugin-specific tables and caches, custom rules in .htaccess or the server config, cron jobs, PHP settings and absolute URLs stored in the database. Plugin-based migrations tend to miss items outside the standard folders or fail on large sites.

People usually ask for this when moving to a faster or cheaper host, consolidating accounts or leaving a provider they no longer trust. They want it done without losing orders, comments or search rankings, and with as little time offline as possible.

What's Included

• Full file and database transfer to the new host
• Recreating any custom server-level configuration the site relies on
• Updating URLs/configuration for the new environment
• Verifying the site works fully before final DNS cutover

What's NOT Included

• Choosing or paying for the new hosting plan
• Fixing pre-existing site issues unrelated to the move
• Email migration (separate service if mail is hosted alongside the site)

How It Works

1. I inventory the source site: WordPress and PHP versions, database size, plugins, uploads, custom server rules, cron jobs and any non-standard folders.
2. I prepare the destination with a matching PHP version and the required extensions, and create the database and user.
3. I copy files and export and import the database, and update paths and URLs where the environment differs.
4. I recreate server-level configuration such as rewrite rules, redirects and PHP limits that the site relies on.
5. I test the new copy before DNS changes using a hosts file override, checking forms, logins, media and any ecommerce flows.
6. I lower the DNS TTL beforehand, then switch DNS and check the live site for content created during the transition.

In practice: you buy the service, send over whatever access or details the job needs, I investigate and do the work, and you confirm it's resolved before we call it done.

Frequently Asked Questions

How do I move a WordPress site to a new host without downtime?

Build and test a full copy on the new host first, then switch DNS once everything works. Downtime is normally limited to the DNS propagation period, during which both copies are available.

Do you handle the DNS change?

I verify the site before cutover and guide the switch. Details depend on where your DNS is managed.

Will I lose orders or comments made during the move?

For active sites, I plan around that, for example by pausing changes briefly or syncing the latest data at cutover. Tell me whether your site takes orders or submissions.

Do you choose or buy the new hosting?

No, choosing and paying for the new plan is up to you. I can work with whatever you select.

Is email moved too?

No, email migration is a separate service if mail is hosted alongside the site.

Will you fix problems that existed before the move?

No, pre-existing issues unrelated to the migration are excluded, although I will mention any that I notice.