Done for you WordPress & WooCommerce hosting migration

Move your WordPress site to hosting that keeps up. Nobody notices it happened.

A migration is not copying files. It is knowing what the site is made of, rebuilding that on the new server, proving it works there, and only then pointing the domain — while the old hosting keeps every visitor served until the moment it switches.

No downtimethe old server serves until the switch

1 daytypical for a site, 2 for a shop

$290 / $590fixed: a site / a shop

Plan my move Check my current hosting first

Old hosting and a full rollback copy kept for 14 days.

Downtime: None — the old server serves visitors until the switch.
Typical turnaround: One working day for a site, two for a shop.
Price: Fixed $290 to move one WordPress site.
Orders: A shop is moved with two syncs, so no order is lost.
Rollback: Old hosting and a full copy are kept for 14 days.
Rankings: URLs do not change, so there is nothing to re-index.

Is it time to move?

Eight reasons people finally do it

One of these on its own is usually survivable. Two or three together mean you are paying for the hosting twice — once on the invoice and once in the visitors who leave before the page arrives.

The admin panel crawls

Saving a post takes five seconds and the media library loads page by page. Visitors feel a slower version of the same thing.

The site falls over when traffic arrives

A newsletter, an ad campaign or a mention sends a few hundred people at once, and the server returns 502 or 503 exactly when it matters.

You keep hitting account limits

CPU seconds, inodes, simultaneous processes, database size. The host suggests the next plan up instead of explaining what is using them.

The renewal price jumped

The first year was cheap and the second is three times that. Same server, same performance, a different number on the invoice.

PHP is stuck on an old version

The panel offers nothing newer, so plugins start warning, security fixes stop arriving and the site runs slower than it needs to.

Mail from the site stops arriving

Order confirmations and form notifications land in spam or vanish, because the server IP is shared with someone who sends bulk mail.

Your visitors are far from the server

The audience is in the US or Germany and the server is somewhere else entirely. Distance alone costs a few hundred milliseconds on every request.

Support answers in a day, or not at all

When the site is down, a ticket queue is not support. This is the reason people give most often, and it is a good one.

Not sure whether the hosting is really the problem? That is a fair question, and moving a site whose problem is elsewhere is money wasted. The check below answers it in twenty seconds.

Check the hosting first

Free · no signup · 20 seconds

Is it the hosting, or is it the site?

Nine passive checks on what your server does with a single request: how fast the first byte arrives, whether the answer is compressed and cached, what sits in front of it, and which PHP it runs. We read only what is already public — no logins, no forms, no probing.

Check your own site. We keep the score for ten minutes so a repeat check is instant, and nothing else.

How the move goes

Build the new one first. Switch last.

Hours are working hours from the moment we have access to both sides. The order is what keeps the site up: everything is built and checked on the new server while the old one is still the one your visitors are using.

0–1

Inventory before anything moves

We write down what the site actually is: WordPress and plugin versions, PHP version, database size, the number of files, cron jobs, mail settings, certificates, anything hard-coded to the old domain or path. That list is what the move is checked against later.
1–2

The new server, set up properly

PHP version and limits, OPcache, database settings, HTTPS, compression, HTTP caching. Not the defaults the panel gives you — the settings this particular site needs.
2–4

First full copy

Files and database copied to the new server and brought up on a temporary address. Nothing on your live site is touched, and the old hosting keeps serving visitors as usual.
4–6

Checked page by page

Home page, templates, forms, checkout, search, feeds, admin. Images, redirects and internal links. The test order goes through and the notification mail actually arrives.
6–7

The switch, with TTL lowered first

DNS TTL is lowered as soon as we get access, so by the time of the switch the change propagates in minutes rather than hours. For a shop we re-sync orders, customers and stock that arrived while we were working, then switch.
7–8

After the switch

Certificate issued on the new server, mail re-checked, redirects verified, Search Console and analytics confirmed still reporting. The old hosting stays paid and running until you are sure.
14 days

We stay on it

Two weeks of watching the new server and fixing anything the move caused, at no extra cost. That window is also how long we keep the rollback copy.

“Isn’t there a plugin for this?”

There is, and sometimes it is the right answer.

If the site is small, the new hosting is much like the old one and an hour of downtime costs you nothing, a migration plugin will do it. We are describing the gap that opens once any of those three stops being true.

A migration plugin

Packs files and the database into one archive
Rewrites the site URL in most places
Works well for a small site moving to a similar server
Costs nothing and takes an afternoon
Cannot configure the server it lands on
Cannot move mail, cron or certificates
Cannot catch the orders that arrive mid-move

An engineer doing the move

Writes down what the site is before moving it, and checks against that list after
Sets up the new server for this site: PHP, limits, OPcache, caching, compression
Moves a multi-gigabyte database without a timeout halfway through
Handles serialised data, so widgets and plugin settings survive the URL change
Keeps orders, customers and stock in sync while the shop stays open
Moves mail, cron and certificates — none of which are inside WordPress
Lowers the DNS TTL in advance, so the switch takes minutes
Leaves a rollback copy and the old hosting running for two weeks

The moves that go wrong almost never fail on the files. They fail on the things that were never inside WordPress: mail that stopped sending, a cron job nobody knew about, a certificate that expired on the old server, a redirect rule that lived in the old host’s panel. Those are what the inventory at the start is for.

One minute, eight questions

How ready is the move?

The check above looks at the server. These eight questions cover the part no scanner can see — the accounts, the access and the surprises that decide whether the move takes one day or three.

1Do you have full access to the current hosting, not just to WordPress?
2Do you know who controls the domain and its DNS?
3Is there a backup you have actually restored, not just seen in a list?
4Does the site send mail from the server rather than through a mail service?
5Do you know which PHP version the site runs on?
6Is anything on the site hard-coded to the current server path or domain?
7Do you know what the site costs you per hour of downtime?
8Is there a date when the move must not happen?

Pricing

Fixed prices, defined scope

One site per package, and the price is agreed before we start. If the inventory turns up something that puts the job in a different bracket, we show you what and why before doing anything — the number never moves once work has begun.

Site move

A business site, blog or portfolio moving to better hosting.

$290one site, fixed price

Inventory of the current setup before anything moves
New server configured for this site, not from a default
Files and database moved, tested on a temporary address
HTTPS certificate and redirects set up and verified
DNS switched with TTL lowered in advance
Before-and-after speed numbers, measured the same way
14 days of follow-up, rollback copy kept

Most chosen

Shop move

A WooCommerce store that keeps taking orders while it moves.

$590one shop, fixed price

Everything in Site move
Two syncs: full copy first, then orders, customers and stock
Checkout and payment gateways tested with a real test order
Order and shipping notification mail verified end to end
Object caching and database tuning for the catalogue size
Switch scheduled for your quietest hour, not ours
Order numbering and stock reconciled after the switch

Complex move

Multisite, several sites on one account, or a move that already went wrong.

$890one project, fixed price

Everything in Shop move
WordPress multisite networks and mapped domains
Several sites sharing one hosting account, untangled
PHP and MySQL version jump with compatibility fixes
Server-level cron, queues and background jobs rebuilt
Mail moved to authenticated SMTP with SPF, DKIM and DMARC
Half-finished migration taken over and completed

Several sites moving together? Tell us how many in the form and we will quote the set — it works out cheaper per site, because the server is set up once and the checks are the same each time. Hosting itself you pay for directly: we take no commission from any host, so the recommendation stays about your site.

What we stand behind

Four promises — and your own arithmetic

The site stays up while we work.

Everything is built and tested on the new server while the old one keeps serving visitors. The only moment anything changes for them is the DNS switch, and that is the last step, not the first.

A way back for 14 days.

The old hosting stays running and we keep a full copy. If anything the move caused turns up in those two weeks, we fix it at no extra cost — and if you want to go back, you can.

Nothing is lost in transit.

Posts, products, orders, customers, media and settings arrive as they were. A shop is moved with a second sync, so the orders placed while we were working come across too.

The price is the price.

Fixed per package, agreed before the work. If the inventory turns up something bigger than we quoted, you see it and decide — we never raise a number on work already under way.

FAQ

What people ask before they move

Something not here? Ask it in the form — the reply comes from the engineer who would do the move, not from a sales desk.

Will the site go down during the migration?

No, and that is the whole point of the order we work in. The new server is built and tested while the old one keeps serving every visitor, so the site is live on the old hosting right up to the switch. We lower the DNS TTL at the start of the job, which means the change reaches visitors in minutes rather than hours, and during that window both servers answer correctly — whichever one a visitor reaches, they see a working site.

How much does it cost to move a WordPress site to a new host?

Moving one WordPress site is a fixed $290. A WooCommerce shop is $590, because it is moved with two syncs so no order placed during the work is lost. A multisite network, several sites sharing one hosting account, or a migration someone else started and could not finish is $890. There is no hourly billing and the price does not change once we have quoted it.

How long does a WordPress migration take?

A normal site takes one working day from the moment we have access to both sides, and the visible switch is the last hour of it. A shop usually takes two days, because the second sync has to be scheduled for a quiet hour. A multisite network or a site with several gigabytes of uploads takes two to three days. The estimate comes before the work, after we have looked at the current setup.

Will my Google rankings drop after moving hosting?

Moving hosting does not change your URLs, so there is nothing for search engines to re-learn. What does cause a drop is a move done badly: pages that answer with errors while DNS propagates, a staging copy left open to indexing, missing redirects, or a robots.txt copied from the test server. We check each of those before and after the switch. Moving to a faster server usually helps rather than hurts, because response time is a ranking signal in its own right.

Can you move email as well as the website?

Yes, and it needs planning separately, because website and mail can live on different servers even when one company sells you both. Mailboxes and MX records are moved and checked in every package. Moving the site’s own mail to authenticated SMTP with SPF, DKIM and DMARC is part of Complex move, or quoted separately.

What if something breaks after the move?

We keep a full rollback copy and the old hosting running for 14 days, so there is always a way back. Within those two weeks anything the migration caused is fixed at no extra cost. If a problem turns out to be older than the move — a plugin that was already broken, a theme error that the old server hid — we tell you that plainly and quote it separately rather than folding it into the price.

Do I need to choose a host first?

No. Tell us what the site does, where its visitors are and what you are spending now, and we will name two or three options that fit, with the trade-offs. We are not resellers and we take no commission from any host, so the recommendation is about the site. If you have already chosen, we work with what you have — we only push back when the plan genuinely cannot run the site.

What access do you need to move the site?

SFTP or SSH and database access on the current hosting, an administrator account in WordPress, access to the new hosting account, and the ability to change DNS — either access to the registrar or someone who can make the change while we are on the call. Create the credentials fresh for us and remove them when the job is done; we will remind you.