Clone-and-Migrate-to-CF-Workers
Harvest your existing site, rebuild it on Astro and Cloudflare Workers Static Assets, and cut your infrastructure bill by 50 to 95 percent. Delivered in 14 days for sites up to 50 pages.
How it works
Cloudflare Pages is in maintenance mode. Vercel and Netlify charge per-function invocation at scale. Next.js App Router on managed hosting adds meaningful latency for primarily-static sites. If your site is predominantly content (marketing pages, blog, documentation, directory), you are paying for a server you do not need.
This blueprint starts with a harvest: a systematic capture of every page on your existing site, including the content, the design system (spacing, colours, typography, component structure), the URL schema, and the internal link graph. The harvest is non-destructive. Your existing site keeps running throughout.
The rebuild uses Astro. Astro ships zero JavaScript to the browser by default. Pages load as static HTML. For interactive components, Astro Islands let you add React or Svelte only where you need it, with the rest of the page staying static. The result is a site that passes Core Web Vitals with sub-50ms TTFB on Cloudflare's edge network.
The bdg storefront demonstrates the pattern end to end. The original site was a Next.js app (harvested from the ttk-shipany template) running on a Node.js server. The rebuild landed on Astro and Cloudflare Workers Static Assets in under two weeks, with matched design and all content intact. Hosting cost dropped from a managed Node.js plan to Cloudflare's free static tier.
What you get
- ✓Full content harvest from your existing site (pages, images, structured data)
- ✓Design system extraction: colours, typography, spacing, component inventory
- ✓Astro site with matched design, rebuilt from the harvest
- ✓301 redirect map: every old URL preserved via Cloudflare redirect rules
- ✓Cloudflare Workers Static Assets deployment and DNS configuration
- ✓Core Web Vitals verification: LCP, CLS, and INP checks before final handover
- ✓14-day post-launch shake-out period included
- ✓Transfer to your Cloudflare account with full access and no lock-in
- ✓Admin dashboard and CMS integration (Site Rebuild and Enterprise tiers)
- ✓Dynamic surface migration: server-rendered pages rebuilt as Cloudflare Workers functions (Enterprise tier)
Three tiers
For sites already on Cloudflare Pages (up to 50 pages). Migrates the deployment configuration to Workers Static Assets and updates wrangler.toml. Minimal design changes. Fastest tier.
Full harvest and rebuild for sites up to 200 pages, on any hosting platform. Matched design, all content migrated, 301 redirects, Core Web Vitals verification, 14-day shake-out.
Sites with 200 to 1,000 pages and dynamic surfaces (user auth, forms, API integrations). Dynamic routes rebuilt as Cloudflare Workers functions. Retainer covers ongoing maintenance and Worker updates.
bdg storefront
The businessdataguide.com storefront started as a Next.js application built from the ttk-shipany template, running on a Node.js server. The harvest captured the full design system and all content pages. The Astro rebuild matched the design and migrated all URLs, then deployed to Cloudflare Workers Static Assets. The migration completed in under two weeks. Hosting cost dropped from a paid Node.js server plan to Cloudflare Workers free tier.
businessdataguide.com →What happens each week
Full content and design harvest from the existing site. URL inventory, internal link map, design system extraction. Agree scope document and page count. Confirm redirects needed.
Build the Astro site with matched design system. Port the component library. Migrate all static pages. First preview shared on a Cloudflare Workers staging URL.
All remaining pages migrated. 301 redirect rules in Cloudflare configured. Sitemap and robots.txt verified. Core Web Vitals measured against the live site baseline.
DNS switched to the new Cloudflare Workers site. Old hosting kept live for 48 hours as failsafe. Full verification pass on all redirects, forms, and dynamic components.
Any issues found during the shake-out period are fixed as part of the engagement. GSC re-indexing progress monitored. Final transfer to your Cloudflare account.
Blueprint C questions
Done correctly, no. The 301 redirect map preserves every existing URL's equity. Astro's Core Web Vitals performance is typically better than the source site, which is a positive signal. GSC is monitored throughout the shake-out period.
Forms can stay as-is via a form backend service, or I can migrate them to a Cloudflare Worker endpoint. CMS integrations depend on the source CMS; I have migrated from WordPress, Ghost, and Contentlayer. Headless CMS integrations (Sanity, Contentful) are included in the Site Rebuild tier.
Auth is a dynamic surface. It falls under the Enterprise Migration tier. Auth can be rebuilt as a Cloudflare Workers function using Cloudflare Access or a JWT-based session. Scoping call required to confirm feasibility.
No issue. The harvest is framework-agnostic. I have migrated from Vercel, Netlify, Render, and self-hosted servers. The rebuild target is always Cloudflare Workers Static Assets regardless of the source.
Minimal management. Workers Static Assets is set and forget for static sites. If you are on a retainer, I handle Cloudflare configuration changes. If not, I hand over a one-page runbook on the day of transfer.