Migration — zero downtime

Your site, moved. Your traffic, preserved.

Every migration follows the same boring script. Staging first. Every URL mapped. Every redirect tested. Every piece of schema preserved. You flip DNS only after you literally say ship it.

How it goes

Four steps. One operator. No surprises.

Step 01

Inventory

Full crawl of the existing site. URL map, status codes, schema audit, SSL chain check, DNS record list, analytics history pulled.

Step 02

Staging build

New site lands on a wildcard subdomain. You click around, content team reviews, redirect map finalized. No DNS touched yet.

Step 03

Flip

TTL lowered in advance. DNS moved at an agreed window. SSL live, sitemap re-pinged, Search Console and Bing notified same hour.

Step 04

Verify + monitor

Redirect sweep, schema validate, Core Web Vitals spot check, seven day traffic watch. Rollback kept armed thirty days.

What we move

Leaving where, exactly?

Most incoming migrations come from the same shortlist of legacy hosts. Each one has its own quirks. Each one has a clean playbook on this side.

GoDaddy + Bluehost

Shared cPanel environments. Typical wins: drop cost, unify DNS, rotate certs automatically, remove addon ladder.

Same day for static sites

WordPress (any host)

Full database export, plugin audit, theme cleanup, media sideload, URL rewrite map, search console reindex request.

24 to 72 hours

Wix + Squarespace

Content extraction, sitemap reconstruction, permanent 301 map to keep search equity intact.

2 to 5 days

VPS, Droplet, EC2

Config audit, nginx port, systemd service migration, cert handoff, DNS and firewall cutover, observability brought forward.

Scoped per case
What comes with

Everything, or we do not sign off.

DNS records

A, AAAA, MX, TXT, CNAME, SPF, DKIM, DMARC. Email keeps flowing. Calendar invites keep working.

Redirect map

Every old URL pointed at the right new URL with a 301. Category slugs, pagination, search engine equity preserved.

Schema + structured data

JSON-LD re-rendered per template, validated with Google Rich Results, served at the edge for crawlers and AI agents.

Analytics + Search Console

GA4, Plausible, Fathom, GSC, Bing Webmaster. Property moves, sitemap submits, change of address pinged same hour.

Common worries, directly answered

The questions every migration gets.

No. Email DNS records move separately and in advance, with TTLs lowered first. We can split mail and web hosts indefinitely.
Not if the redirect map is honest. Every old URL gets a 301 to the right new URL. Search Console property is transferred, sitemap re-pinged, and we monitor position drift for four weeks post cutover.
Target is zero seconds of downtime. Both hosts run in parallel during the TTL window. The switch is a DNS change, not a content reupload.
Rollback stays armed for thirty days. One command restores prior DNS and a snapshot of the old origin. Worst case recovery window is the TTL you set pre cutover.
No. You keep the registrar. We share a delegated DNS zone or a record list. You can click the button. Or grant delegated access to a specific zone only. Your call.
Standard migrations are included in the Managed and Growth plans. Unusual cases are scoped and quoted before the work begins, not after.
Accepting new migrations this month

Send a domain. Get a plan.

The free audit alone maps every bottleneck on your current host. Most people keep the PDF whether they migrate or not.

Start the audit → See hosting plans
Next migration window —