Redirects missed
Changed URLs with no redirect map, so ranked pages return errors and organic traffic drops for months.
[ WordPress / WordPress Migration ]
Move the site without losing your rankings.
Migration plugins work until they do not — on large databases, on sites with a payment gateway, or on anything where a broken redirect costs real traffic. This is the careful version.
No downtime typical · Redirects verified · Fixed price
0downtime, typically
100%redirects verified
Old hostkept as fallback
Fixedprice, agreed upfront
[ What goes wrong ]
Why migrations lose traffic.
The site usually arrives. What gets lost is everything around it.
Serialized data corrupted
A find-and-replace across the database that breaks widget and theme settings in ways that surface weeks later.
Email stops arriving
Order confirmations and password resets silently failing because sender records were never updated.
Mixed content warnings
Assets still referenced over an old domain or insecure scheme, so browsers flag the page.
Scheduled tasks lost
Cron jobs that ran on the old host and simply do not exist on the new one.
Orders taken on the old site
DNS still pointing at the old host for some visitors, so transactions land somewhere nobody is looking.
[ How it works ]
Copy, verify, then switch.
01 — Day 1
Prepare
Full inventory: plugins, cron jobs, mail configuration, integrations and URL structure. TTLs lowered so the switch is fast when it comes.
02 — Day 2-3
Build & verify
Site copied to the new host and tested privately — every template, form, checkout path and integration checked before anyone sees it.
03 — Cutover
Switch
Final content sync, DNS switched, redirects verified live, and the old host kept running until we agree the new one is stable.
[ What actually changes ]
What gets moved and checked.
Where a migration plugin is genuinely the right tool, I will use one. It is the verification either side that makes the difference.
The move
- Files and database — transferred with serialized data handled correctly, not naively replaced.
- Media library — moved with paths rewritten and every attachment confirmed reachable.
- Plugins and licenses — reactivated on the new host, with license domains updated.
- Cron jobs — read from the old server and recreated, including anything outside WordPress.
- TLS certificate — issued and validated on the new host before the switch, not after.
Verification
- Redirect map — every changed URL mapped, then tested live immediately after cutover.
- Email deliverability — sender authentication updated so transactional mail keeps landing.
- Checkout and forms — a real transaction and a real submission tested end to end.
- Search console update — new property verified and the sitemap resubmitted.
- Backups on the new host — running and restored once before the old environment is released.
[ Example engagement ]
Store moved mid-week, nobody noticed.
A busy store on struggling shared hosting, moved to a properly configured server. Site copied and verified privately for two days before the switch.
Illustrative example of a typical engagement. Figures vary with the state of your systems and are not a guarantee of a specific outcome.
0sof downtime
1,400+URLs redirect-checked
0orders lost
3.1sfaster page load
[ Free · no obligation ]
Get the plan before you move.
Tell me where the site is hosted now and where it is going. You get the approach, the risks specific to your setup, and a fixed price.
[ Pricing ]
Pricing that fits your budget.
Tell me the number you have to work with. I'll tell you honestly what's achievable within it — and if it isn't enough, I'll say so before we start rather than halfway through.
Fixed project price
Scope agreed in writing, price agreed in writing, before any work starts. No hourly creep and no invoice you haven't already approved.
Monthly retainer
For ongoing work — maintenance, monitoring, updates and small changes. Month to month, cancel whenever, no minimum term.
Hourly for small jobs
For a single bug or a short task where writing a full scope would cost more than simply doing the work.
Budget too tight for the whole thing? I'll often suggest doing the highest-value part first and the rest later, rather than doing all of it badly.
[ Questions ]
Common questions.
Will my site go down?
Usually not at all. The new site is fully built and tested before DNS changes, and both hosts serve the site during the switchover window.
Will I lose search rankings?
Not if the URL structure and redirects are handled correctly, which is an explicit deliverable. When a domain changes, a temporary dip is normal and recovery typically takes a few weeks with the right redirects in place.
Can you move to a new domain as well?
Yes. Domain changes need more care with redirects, search console setup and internal link rewriting, all of which is included.
What about my email?
If mail is hosted on the same server, I will usually recommend moving it to a dedicated provider. Either way the DNS and authentication records are handled so delivery does not break.
How big can the site be?
Size is not really the constraint — large databases and media libraries just change the technique. Sites where a plugin-based migration would time out are exactly the ones worth doing this way.
[ Related services ]
Related migration work.
Server MigrationMove hosts without losing data, email or search rankings.Migration to AWSMove from shared hosting, a VPS or another cloud without downtime.WordPress Speed OptimizationFix Core Web Vitals and slow load times at the cause.WordPress SecurityHarden a clean site so it stays that way.WordPress Bug FixingWhite screens, broken checkouts and plugin conflicts, diagnosed properly.Server Setup & ConfigurationLinux servers built properly: web stack, TLS, backups, monitoring.
[ Let's talk ]
Tell me what's broken.
Describe the problem in a few lines and you'll get a real reply from the person who'd do the work — same working day, no discovery call required.