Migrate your Webflow site to Cloudflare.

The proof is this site.

I migrated felixhellstrom.com off Webflow to Cloudflare on May 6, 2026. The site you're reading right now is the result. Open the dev tools, look at the network tab, run Lighthouse against this URL, audit the headers. Everything I'm offering you is right here, live, in production.

The before-and-after on this site:

Verify it yourself: PageSpeed Insights · DNSSEC analyzer · Security Headers

What you get.

For $2,997 flat, in seven days, your Webflow site lives on Cloudflare with everything below shipped and verified.

• Full crawl of your live Webflow site
• Static HTML rebuild on Cloudflare Pages
• 100/100/100/100 Lighthouse mobile (verified before delivery)
• Universal SSL via Cloudflare (or BYO certificate)
• DNSSEC chain established to the parent zone
• Custom domain attached, DNS migrated, no downtime
• Auto-deploy on git push (GitHub Actions wired)
• Same authoring experience (freedom-cms, see below)
• SEO preserved: canonical URLs, redirects, sitemap, OG cards
• Cookieless analytics (Cloudflare Web Analytics, GDPR-clean)
• Full security header stack (HSTS preload, CSP, X-Frame-Options)
• Image optimization (AVIF where applicable, lazy loading)
• Repo on your GitHub, 100% yours, no vendor lock-in
• Handoff doc explaining everything, written for a human

Same authoring experience.

The Webflow editor is the reason most teams stay. The good news: you don't lose it. The migrated site uses freedom-cms, a tiny Rust server I built that turns the live HTML page into the editor itself.

Edit a heading by clicking it and typing. Drop a new image by clicking the existing one. Save by closing the tab; freedom-cms autocommits to git and pushes. Cloudflare picks up the push and deploys. Total round-trip from edit to live: about thirty seconds.

If you'd rather edit in markdown / VS Code / Cursor / a real IDE, you can. The HTML files are the source of truth. Whatever can edit a file can edit the site.

If you have a complex content model that's currently a Webflow Collection (CMS), that's a separate conversation. We'll figure out the right shape during week one.

The week.

1. Day 1–2Crawl your live site. Audit every page, asset, redirect, form, integration. Send you a written plan with anything that needs a decision.
2. Day 3–4Rebuild on Cloudflare Pages. Strip the Webflow runtime. Optimize images. Wire fragments. Hit 100/100/100/100 internally.
3. Day 5Deploy. Attach your custom domain. Issue SSL cert. Enable DNSSEC. Verify routing.
4. Day 6SEO check: canonical URLs match, redirects in place, sitemap submitted to Search Console. Content QA.
5. Day 7Handoff. Walkthrough call. Train you on the editor. Watch you make a live edit. Fix anything that breaks. You own the repo.

If something blocks the timeline (a Collection that needs schema design, an integration that needs custom code), we either descope it for V2 or quote the extra work separately.

Pricing.

Optional add-ons

Questions you're probably asking.

What if my site is heavily customized?

Most Webflow sites aren't. The CSS bundle ships with hundreds of utility classes most pages don't actually use; we strip those. Custom interactions (Webflow's data-w-id animations) get rewritten as vanilla CSS or kept as-is, depending on what they do. If your site is genuinely complex (Memberships, custom JS embeds, headless integrations), we'll quote separately after the audit.

Will my SEO survive?

Yes. Canonical URLs are preserved. Redirects from any old paths are in place at the Cloudflare edge. Sitemap.xml is regenerated and submitted to Google Search Console. JSON-LD structured data carries over. We run a side-by-side check before you cut DNS.

What about my CMS Collections?

Static HTML doesn't have collections. We have three options: (1) flatten Collections into static pages at migration time, (2) keep the CMS authoring flow via freedom-cms with a small content-model layer, or (3) point at an external headless CMS (Sanity / Contentful / Notion) for that specific content. Decided in week one based on your actual usage.

Can I keep editing in the Webflow editor?

No. Webflow's editor is locked to Webflow's runtime. The replacement (freedom-cms) is similar UX: click element, edit in place, save. If your team prefers the Webflow editor specifically and won't accept anything else, this offer isn't a fit.

What about my forms?

Cloudflare Pages Functions handle simple form submissions (email notification, save to KV). For anything richer (Salesforce, HubSpot, mailing list integration), we hook your existing tooling. Webflow's built-in form handler doesn't migrate; we replace it.

What does "one-week delivery" actually mean?

From the day you send payment to the day your domain serves the migrated site. The clock pauses if I'm waiting on you for content decisions, access tokens, or DNS changes you have to make. In practice, week one is mostly mine; the only days you're involved are the kickoff call, content decisions on day 3, and the handoff call on day 7.

What if you can't hit 100/100/100/100?

I haven't yet, but if it happens: I work until I do, on my time, no extra charge. The score is the deliverable. If your site has third-party scripts I can't optimize (a chat widget that adds 200ms TBT), we'll discuss the trade and either drop the script or accept a defined floor like 95+. Documented in writing before delivery.

Membership, e-commerce, paywalls?

Not in this offer. Cloudflare Pages handles them via Workers + integrations, but the migration is a different shape and price. Ask, and I'll quote.

What if I'm not sure my site is a fit?

Run a free Lighthouse audit first. I'll send you back a written report on what's slow, what's broken, and whether migration would actually help. Sometimes the answer is "stay on Webflow"; if it is, I'll tell you.

Two ways to start.

If you're a Webflow agency with multiple client sites and want to talk about a referral or white-label arrangement, write to me; that's a different conversation and a different price.