Website Migration

Website migration should be boring. I keep it that way.

I move WordPress sites between hosts with backups verified, redirects mapped, and a rollback ready before anyone touches production. Visitors and Google shouldn’t notice anything except, ideally, a faster site.

850+ clients served, many of them moves nobody noticed

Replies within 24 hours, usually the same day

What you are buying

₹15,000Fixed price, GST included
$199In dollars

Work delivered for, or alongside, teams at:

  • IBM
  • Adobe
  • HubSpot
  • Canva
  • monday.com
  • IATA
  • FreshBooks
  • Acer
  • ASUS
  • Airtel
  • BYJU’S
  • AppSumo
  • StellarWP
  • Copyleaks
  • Depositphotos
  • accessiBe

What it costs

A fixed price for a move with no surprises.

The simple migration covers a host-to-host WordPress move, planned, rehearsed on staging, and verified after cutover. Nothing gets deleted until you’ve confirmed the new site works.

Simple website migration
₹15,000 $199fixed price · host-to-host WordPress move
  • Full backup with a verified restore before anything moves
  • Staging build and test on the new host
  • URL parity and redirect check across the whole site
  • DNS and SSL cutover on a planned timeline
  • Forms, checkout, and tracking verified after the switch
  • 72-hour monitoring window after go-live
Plan my move

Platform migrations, like Wix or Squarespace to WordPress, are scoped separately from ₹75,000.

All prices include GST.

How this runs

You will know the price and the plan before I touch anything.

1

Map

Tell me what’s moving, when it must be live, and what cannot break. I inventory the site and its dependencies, then write the risk plan and the fallback sequence.

You leave with: a cutover runbook.

2

Rehearse

The site gets built and tested on staging at the new host first. Forms, checkout, and the flows that pay you are checked before DNS ever moves.

You leave with: a proven copy before cutover.

3

Cut over

DNS and SSL switch in a planned window while the old site stays live and untouched as the fallback. If anything looks wrong, we roll back instead of debugging in public.

You leave with: a live site and a working exit.

4

Stabilize

For 72 hours I watch errors, indexing, and performance until the stack settles. Analytics and Search Console get re-verified so attribution survives the move.

You leave with: confirmation, not hope.

A note from me

How I migrate a site

Migration disasters are almost never technical failures. They’re planning failures: a missing redirect map, an untested backup, no rollback when an edge case shows up in production.

So I front-load the boring work. The backup gets restored once before we start, just to prove it can be. The old site stays live until the new one has earned its place.

I refuse to delete anything during a migration. Storage is cheap; a lost site is not.

— Gaurav

Before you write in

This isn’t for every site.

Worth starting

  • You’re leaving a host over speed, cost, or support, and the site is WordPress on both ends.
  • The site takes orders or leads and can’t afford a botched weekend cutover.
  • You have, or can get, access to your domain’s DNS.
  • Rankings matter and you want URL parity checked, not assumed.
  • You want one person owning the move end to end, including the 72 hours after.

Look elsewhere

  • Your budget is under ₹15,000. Many hosts migrate incoming sites free; use that, then verify everything carefully yourself.
  • You’re moving from Wix, Squarespace, or Blogger. That’s a platform migration with content rebuilding, quoted from ₹75,000.
  • You want a redesign bundled into the move. Migrate first, redesign second; mixing the two hides whose bug is whose.
  • Nobody on your side can grant domain or DNS access. I can’t cut over what I can’t reach.
  • The site changes daily and you won’t freeze content during the move. Diverging copies make a clean cutover impossible.

If you want to:

  • Move without downtime on a planned, reversible cutover
  • Keep your rankings with redirects and parity verified
  • Sleep during cutover the rollback is ready if needed

Common questions

Not answered here? Ask directly and you will hear back within 24 hours.

₹15,000 fixed for a simple host-to-host WordPress migration, and the price includes GST. Platform migrations, like Wix or Squarespace to WordPress, involve rebuilding content and structure and start at ₹75,000, scoped after I’ve seen the site.

One WordPress site moving between hosts with the same domain and URLs. Multisite networks, domain changes, huge stores, or platform switches are more work, and I’ll tell you the real scope before quoting rather than after starting.

Not when the move is planned. Rankings drop when redirects go missing, URLs change silently, or pages get dropped. I verify URL parity, map any redirects, and crawl the new site after cutover, so search engines see the same site in a new home.

Planned downtime is zero for a standard move. The new copy is built and tested on staging while the old site keeps serving, and DNS cutover happens only after verification. Visitors just start hitting the new server.

The 72-hour monitoring window catches almost everything a move can break. If something tied to the migration surfaces after that, I fix it. Unrelated site bugs are scoped separately, and I’ll be straight with you about which is which.

Gaurav Tiwari

About me

So, who’s watching your site?

Everything I would put on your site is running on mine first.

Care clients get the same stack I trust with my own traffic: GT Performance, Cloudflare, Redis, Hetzner.

I was a teacher before I was a developer. I taught mathematics to competitive-exam students, which is why I explain hard things plainly instead of hiding behind jargon.

What I am actually good at is the join: technical SEO, fast front-ends, and content treated as one system instead of three vendors blaming each other.

  • Author of GT Performance, my own caching engine
  • Hardening proven on my own production sites
  • Plugins on 10,000+ sites
  • WordPress Core contributor
  • 850+ clients since 2008
  • Building for the web since 2008

Tell me what’s moving and when it must be live.

Describe the site, the current host, and the destination. I’ll reply with the runbook outline, the risks I see, and the cutover date I’d aim for.

Replies within 24 hours, usually the same day