We move WordPress sites between hosts, domains and stacks without losing traffic, rankings or revenue. Staged cutover, rsync and database sync, DNS handled cleanly, 301 redirect maps shipped. You get a new home and the same search position you earned.
Most migrations fail on the small stuff. A missed serialized option, a cron that never re-registered, an uploads folder half-copied, a DNS TTL still at 24 hours on cutover day. We plan for each of those before we touch the source site.
Every migration ships a full inventory, a staged dry run on the target host, a signed-off cutover window and a 301 redirect map that preserves every indexed URL. Nothing gets pointed live on vibes.
A structured, low-risk process. You see the inventory, the dry run, the cutover window and the verification. No surprise outages, no missing files on Monday morning.
We audit the source site, list every plugin, theme, custom table, cron, scheduled job and hardcoded URL, document PHP and MySQL versions, uploads size and DNS records, then write a ranked runbook with rollback steps agreed with you.
We provision the new host, match PHP, MySQL, Redis and extensions, rsync files, import the database, run WP-CLI search-replace and test every flow on a staging hostname. Login, checkout, forms, search, emails and admin ajax verified.
DNS TTL dropped in advance, a final incremental rsync and database delta sync in a frozen window, DNS pointed to the new host, HTTPS and HSTS set, legacy URLs 301-mapped and monitoring green before we announce done.
Post-cutover smoke tests, real user monitoring in place, 404 report reviewed, search console resubmitted, a 7-day watch window with hot-fix support and a written runbook handed to your team for future moves.
A migrator plugin is not a strategy. A generalist freelancer will not plan the DNS window. Here is how we stack up on work that actually protects traffic and revenue.
Pricing reflects site size, host complexity and commerce scope, not hours burnt. Pick a tier close to your needs or ask for a custom estimate after the inventory.
Single WordPress site, standard host to host move. Inventory, dry run, cutover and redirect map included.
WooCommerce or membership site with live orders. Incremental sync, order-safe cutover, 7-day watch window.
Large or complex move. Multisite, heavy media libraries, custom tables, staged rollout or stack change.
Multi-site programmes, recurring migrations and regulated environments with change control and audit trail.
We do not close a migration ticket on a ping check. Cutover has to hold up against real logins, real carts, real search traffic and real emails.
DNS TTL dropped in advance, frozen cutover window kept under 60 seconds of read-only where possible.
File checksums verified, database delta re-applied in the cutover window, orders and comments carried across.
URL structure held where possible, 301 map for the rest, canonicals, sitemaps and hreflang verified on go-live.
Certificate provisioned, HSTS, security headers and redirect chains validated before the site goes live.
Scheduled tasks re-registered on the target host, WP-Cron or real cron verified, queues draining as expected.
Stock, subscriptions, payment tokens and customer sessions all tested on target before any DNS change.
Transactional mail, SPF, DKIM and DMARC checked on the new host so resets and receipts never silently drop.
Uptime, log tail and error tracking set up before cutover so any regression is caught within minutes.
Your team gets a runbook covering the new host, rollback steps and how to repeat the move if needed.
We are the silent migration team behind design and marketing agencies. Your client sees your plan, your runbook and your brand on every artefact. Our name never appears in the Slack channel, the handover docs or the cutover email.
Runbooks, inventories and cutover reports carry your brand, not ours.
One point of contact for every engagement. Shared Slack, scheduled cutover windows, fast replies.
Per-site rates, bulk discounts and priority scheduling for agency partners with recurring migration work.
We plug into your ClickUp, Linear, Jira or Notion. No tool switching, no friction for your team.
You send staging access, current host, target host and any client constraints around cutover windows.
We audit the site, write the runbook and send you a partner rate quote. Never shown to your client.
You mark up, brand the proposal and present it on your letterhead at your price.
Your client signs off on the cutover window and runbook with your brand and pays you directly.
Silent work on branded staging. No vendor credits, no email signatures, no footer links from us.
You review the cutover report, accept handover and ship the runbook to your client under your agency name.
No. The old site keeps serving traffic while we build and test the new one. Cutover happens in a short frozen window, usually off-peak, with DNS TTL lowered in advance. Most of our moves see under 60 seconds of read-only time and zero user-visible downtime.
Yes. We freeze new orders in a short maintenance window, run a final incremental sync so no order is lost, point DNS and re-enable checkout on the new host. Stock levels, subscriptions, customer sessions and payment tokens all carry across.
Yes. We preserve URL structure wherever we can and ship a 301 redirect map for anything that has to change. Sitemaps, canonicals, hreflang and robots.txt all verified on go-live. Search Console resubmitted so Google picks up the new host within days.
Yes. Platform-to-WordPress moves are one of our specialties. Content and media migrated, URL structure preserved, 301 map built. Those are priced on the WordPress Conversion page, but the cutover mechanics are identical to a host-to-host move.
A standard host-to-host move is 3 to 7 business days. A WooCommerce, multisite or large media library can stretch to 10 to 14 days. You get a firm cutover window in the written scope before work begins.
We hold a 7-day watch window by default. If an issue shows up in that time, we fix it on our clock. The runbook we hand you also covers rollback, so if a business-critical issue surfaces we can point DNS back to the old host within minutes.
Share the source host, target host and any cutover constraints. A migration engineer will respond with an inventory outline and a written scope within one business day.