Move a static/Jamstack site (Astro, Hugo, static Next.js export, single-page apps) or a WordPress brochure site (WordPress to EmDash) from Netlify, Vercel, GitHub Pages or a similar host to Cloudflare Workers, deployed to your own Cloudflare account.

What's included:

- Workers Static Assets setup

- Redirects and headers converted to _redirects / _headers with explicit status codes (a Cloudflare _redirects rule with no code defaults to 302; Netlify defaults to 301)

- Form replacement

- DNS cutover: TTLs lowered in advance, DNSSEC handled per Cloudflare's docs; email records (MX/SPF/DKIM/DMARC) checked before and after

- Search Console, sitemap and IndexNow

- Before/after parity check on every URL: status codes, redirect codes (301 vs 302), headers, canonicals, sitemap and content

- Written rollback plan, tested before DNS changes; 7-day rollback window, your old host stays untouched

Price: starting at $499 per site (up to $799), fixed in the audit quote before any work starts. Larger sites or WordPress sites beyond a brochure are quoted separately after the audit. Start with the $199 Cloudflare Migration Audit; the $199 is credited in full toward this move.

In an internal demo, we converted a static FAQ site from a simulated Netlify-style setup to Cloudflare Workers and ran it live on a test host with search indexing blocked.

Rolling back to the previous deployed version took a median of 2.36 seconds across three live rollbacks (2.19 to 2.49 s).

Every run is logged with the commit, timestamps, and request IDs; raw logs containing visitor data are never published.

Out of scope: e-commerce/membership WordPress, Heroku, Postgres to D1, gambling/betting sites.

AI agents help build and check this deliverable; a person at AI Kit reviews it before delivery. Tell us before ordering if AI must not be used.