What a "WordPress migration service" line item actually covers
Search "wordpress migration service" and the page-1 results are mostly the same sales pitch: send us your login, we move your site, done in 24 hours. According to WPBeginner's own roundup of migration tools and services, most of that promise rests on one plugin doing the heavy lifting — All-in-One WP Migration or Duplicator — wrapped in a support contract. That's not a criticism of the tooling — it's accurate for a 2 GB brochure site built in 2024 or later. It stops being accurate the moment your site has a 40 GB uploads folder, three years of custom plugin code, or a WooCommerce store with live orders mid-move.
In practice, the quote you get up front for a WordPress migration rarely survives contact with the real site. Reports that track hosting-industry pricing, like the service-cost data published by WorldMetrics, show a wide spread. There's a reason for that spread. "Wordpress migration service" covers everything from a 1-hour plugin export to a 5-day multisite re-platform. A single flat number can't honestly describe both jobs. This guide is the buyer's side of that conversation. It covers the nine items to get in writing before you sign anything, where fixed-price quotes actually break, and the three red flags that predict you'll be paying twice.
The nine items, the four quote-breakers, and the three red flags below are built around what actually goes wrong and what the original quote tends to leave out — not a generic checklist.
DIY vs. done-for-you: the decision that actually matters first
Before comparing vendors, decide whether you need a vendor at all. People overpay for a done-for-you move that a free plugin would have handled just as well, and people lose entire weekends trying to DIY a complex multisite network that genuinely needed a specialist.
| Factor | Lean DIY | Lean done-for-you |
|---|---|---|
| Site size | Under 2 GB | Over 10 GB, or unknown uploads size |
| Commerce | No orders, or a content-only blog | WooCommerce/EDD with live orders |
| Custom code | Stock theme + a handful of plugins | Custom plugins, a child theme with hooks, or a headless front end |
| Deadline | Flexible, can retry on failure | Hard cutover date (domain renewal, host contract end) |
| Risk tolerance | Comfortable restoring from a backup if something breaks | Zero tolerance for downtime or data loss |
If you're searching "how to move wordpress site to a new host" rather than "wordpress migration service," you're probably already in the DIY column — our team has a separate, step-by-step cutover runbook for exactly that case, so we won't repeat it here. This piece is about what to demand when you're paying someone else to do it.
One nuance that table doesn't capture: deadline pressure changes the math even for a DIY-sized site. A 1.5 GB blog with no commerce is a clean DIY candidate on a normal week. The same site, with a host contract expiring in 48 hours and a domain renewal due in 5 days, is a different risk profile — not because the technical job changed, but because a failed DIY attempt with no time buffer to retry becomes an emergency instead of a minor setback.
The nine scope items to get in writing before you pay
A one-line quote ("$299, done in 24 hours") is not a scope. Before you send a deposit, get written answers — email, not a phone call — on all nine of these:
- Who touches DNS, and when. Name the person and the exact TTL change window.
- What happens to email. If MX records live on the same domain, migrating the site must not touch mail routing. Ask explicitly.
- Database size and table count included in the fixed price. A 200 MB database with 40 custom tables from an old plugin is not the same job as a 200 MB database with 12 stock WooCommerce tables.
- Uploads folder size and file count. This is the single biggest cause of quote blowouts — see the next section.
- Staging environment parity. Will the staging copy run the exact same PHP version, server stack, and plugin versions as production, or a generic sandbox?
- SSL certificate handling. Who issues the new cert, and is there a gap where the new host serves unencrypted?
- Rollback plan if the cutover fails. Named, not implied. What's restored, from where, and in how many hours?
- Pre-cutover verification checklist. What specifically gets tested before DNS flips — checkout flow, contact forms, login, search?
- Post-cutover monitoring window. How many hours or days does the vendor watch uptime and error logs after the move, and what do they do if something trips?
Email this list to any vendor before you pay. A vendor who answers all nine in one reply has done this enough times to have the answers memorized. A vendor who says "don't worry, we've got it" to all nine is the first red flag — more on that below.
How fixed-price quotes break
Per the plugin documentation for All-in-One WP Migration, free-tier exports are capped (512 MB on the free plugin, larger on paid extensions) — which is exactly why "we use the free plugin" services quietly add a per-GB surcharge once they see your actual uploads folder. Four things reliably blow up a fixed quote:
- Uploads folder size. A photography site, a real-estate listing site, or anything with five years of unoptimized image uploads can sit at 25-80 GB. A flat $299 quote assumed 3 GB.
- Custom plugins or theme code. Anything hand-built needs manual file transfer and a working PHP version match — a one-click plugin move can silently drop custom post types or ACF field groups that weren't registered the way the migration tool expects.
- Multisite networks. Each subsite effectively doubles the manual verification work; a 5-subsite network is not "one site times five," it's closer to a full re-architecture of the wp-config.php multisite constants.
- Staging parity gaps. If the new host runs PHP 8.3 and the old site was built against PHP 7.4 behavior, functions that worked in production can throw fatal errors on the new stack — and that surfaces only after cutover, not during the quote call.
None of this means fixed pricing is a scam. It just means a fixed price without a stated uploads-size ceiling and a stated plugin count is a placeholder number. Treat it as a starting point for negotiation, not a real quote.
Ask the vendor to write the uploads-size ceiling and the per-GB overage rate directly into the quote email. If they won't put a number on it, that reluctance is itself useful information about how the final invoice will go.
Realistic timelines by site size, and what "zero downtime" should mean
"Zero downtime" gets thrown around loosely. Contractually, it should mean one specific thing: the old site keeps serving visitors, unmodified, until the new site has been verified and DNS has propagated — not "we moved fast so you probably didn't notice."
| Site profile | Realistic timeline | What "zero downtime" requires |
|---|---|---|
| Brochure site, under 2 GB | 2-4 hours | DNS TTL dropped to 300 seconds 24 hours ahead |
| Content site with 10,000+ posts, under 10 GB | 1 business day | Full search-index re-verification before cutover |
| WooCommerce store, live orders | 2-3 days, scheduled for a low-order window | Order sync frozen and reconciled, not just copied once |
| Multisite network, 5+ subsites | 3-5 days | Per-subsite verification, not one network-wide smoke test |
If a vendor quotes 24 hours for a WooCommerce store with live orders regardless of order volume, ask how they handle orders placed during the copy window. "We'll just redo it" is not an answer you want to hear after you've paid. A better answer names the exact mechanism. Order sync freezes at a cutoff time. It reconciles against the live database once the new site is stable.
The "scheduled for a low-order window" line above matters more than it sounds. A store that processes most orders between 9am and 9pm local time, 7 days a week, has effectively no low-order window during business hours — the real option is a 2am-5am cutover, which means someone on the vendor's side needs to be awake and monitoring during those 3 hours, not just scheduling the job and checking the next morning.
Three red flags that predict a migration you'll have to redo
Our team has seen a specific pattern repeat across failed migrations clients brought to us afterward for cleanup. Three signals show up almost every time:
- No named rollback plan. If the answer to "what happens if this breaks at 2pm on cutover day" is vague reassurance instead of a specific restore source and restore time, the vendor hasn't actually planned for failure — they're hoping it doesn't happen.
- No pre-cutover verification step. A migration that goes straight from "copy files" to "flip DNS" with nothing tested in between is a coin flip. Checkout flows, login, contact form delivery, and site search should all be confirmed on the new environment before traffic moves.
- No post-cutover monitoring window. Problems that don't show up in the first ten minutes often show up in the first 48 hours — a cron job that didn't re-register, a cache layer serving stale pages, an SMTP setting pointing at the old server. A vendor who disappears right after DNS flips leaves you to find these alone.
Any one of these alone isn't disqualifying — a small, low-stakes brochure site can tolerate some informality. All three together, on a commerce site or anything with real traffic, is a strong signal the migration will need a redo within 90 days.
The pattern holds up in practice: sites showing all three red flags tend to need a second, full re-migration within weeks of the original move. Sites with a named rollback plan and a monitoring window, even an informal one, rarely run into that problem at all.
What a redo actually costs, beyond the second invoice
When clients come to us after a failed migration, the second vendor invoice is rarely the biggest cost. A WooCommerce store that goes down for 6 hours during a redo can lose several thousand dollars in abandoned carts alone, depending on average order value and traffic. A content site that loses its sitemap during a botched move can see search rankings drop for 2-4 weeks while crawlers rediscover the new URLs — and if 301 redirects weren't mapped correctly during the first attempt, some of that traffic never fully recovers.
None of this is meant to scare you out of hiring a migration vendor — most migrations, done by a vendor who answers the nine scope questions honestly, go fine. It's meant to size the actual stakes correctly: the $150-$500 difference between a vague flat-rate quote and a scoped one is small next to the cost of redoing the job under pressure with lost orders or lost rankings on the clock.
There's also a timing cost that's easy to miss. A redo almost never happens on your schedule — it happens the week you discover the problem, usually while you're also fielding customer complaints about a broken checkout or a 404'd blog post. Paying a little more up front for a vendor who scopes the job properly buys you the ability to plan the migration for a quiet week instead of an emergency one.
Why a verified independent backup is the cheapest insurance in the quote
Every item above assumes the migration itself might fail partway through. The cheapest protection against that — and the one line item most quotes skip entirely — is an independent, verified backup taken before the vendor touches anything, stored somewhere the vendor's own process can't overwrite.
"Independent" matters: a backup sitting in the same hosting account as the site being migrated isn't a backup, it's a copy that disappears if the account itself is the thing that breaks. "Verified" matters just as much — a backup file that exists but was never test-restored is a guess, not a safety net. This is the exact gap BackupYourSite exists to close: automated, off-host backups with scheduled restore tests, so if a migration goes sideways, restoring the old site is a known-good procedure measured in minutes, not a scramble.
Failed migrations show the same pattern every time: the sites that recover fastest are the ones with an independent backup taken within 24 hours of cutover. The ones that lose real content are the ones relying on the migration vendor's own export as the only copy.
Questions to email a vendor before you pay
Copy this block into an email before sending a deposit:
1. What is your uploads folder size and file count assumption in this quote, and what's the per-GB rate above that?
2. Will our site run on staging with the same PHP version and plugin versions as production before cutover?
3. What is the named rollback plan if cutover fails, and how many hours to restore?
4. What specifically gets tested before DNS changes — checkout, login, forms, search?
5. How many hours or days do you monitor uptime and error logs after cutover, and what triggers escalation?
6. Who initiates the DNS change, and what is the TTL window?
7. What happens to our email (MX records) during the move?
A vendor who answers all seven specifically, in writing, is quoting a real scope. Reach out to our team at BackupYourSite if you'd like a second opinion on a quote before you sign.
Frequently Asked Questions
How much does a WordPress migration service cost?
Done-for-you migrations typically range from $150 for a small brochure site to $1,500+ for a multisite network or a high-traffic WooCommerce store, though in practice the final number depends heavily on uploads folder size and custom plugin count — see our pricing page for how we scope ours.
How long does a WordPress migration take?
A small content site under 2 GB can move in 2-4 hours. A WooCommerce store with live orders realistically needs 2-3 days to migrate and verify without losing orders placed during the move.
Can I migrate my WordPress site myself for free?
Yes, for most brochure and content sites under roughly 2-3 GB using a plugin like All-in-One WP Migration. Our how-it-works page covers what to check before you start a DIY move.
What is the biggest risk in a WordPress migration?
Having no independent, verified backup before the move starts. If the migration tool's own export is the only copy and something corrupts mid-transfer, there's nothing to roll back to.
Do migration services guarantee zero downtime?
Many advertise it, but "zero downtime" only holds up if DNS TTL was lowered in advance and the new site is fully verified before traffic is pointed at it. Ask vendors to define it in writing rather than accepting the phrase alone.
What's the difference between a website migration checklist and a vendor's internal process?
A buyer-side checklist (like the nine scope items above) protects you regardless of which vendor you use. A vendor's internal process is their own method — useful to ask about, but not a substitute for your own written scope.
Should I migrate and set up backups at the same time?
They're related but distinct costs — migration moves the site once; backups protect it on an ongoing basis afterward. Our backup pricing breakdown covers ongoing cost separately from the one-time migration quote above.
Is a WordPress migration service worth it for a small business site?
For a site under 2 GB with no commerce, often not — a free plugin and an afternoon will do it. For anything with live orders, custom code, or a hard deadline, the cost of a redo after a failed DIY attempt usually exceeds the vendor fee.
What if I'm migrating to a white-label or agency-managed host?
The same nine scope items apply, with one addition: confirm who owns the backup copy after migration — agency-managed and white-label hosting setups sometimes leave that ownership unclear until something breaks.