What Actually Imports When You Flip from Cloudflare

Migrating from Cloudflare? We built the import to save you config work, not to promise "lossless zero-downtime magic" (that's not how it works).

Here's the honest breakdown:

These import automatically:
– DNS zones and records (CNAME, A, MX, etc.)
– Page rules, redirects, and routing logic
– Origin server config and SSL certificate mode

You'll rebuild by hand:
– Cloudflare Worker code — we import the route patterns, but worker scripts themselves need to be re-authored in our Edge Workers. Different runtime, different APIs. This is the one that'll take time, and there's no way around it.

Why do we only import route patterns? Because each platform's worker environment is distinct — porting CF Workers code line-for-line isn't possible, and pretending it is sets people up to fail.

If you're just running DNS + WAF rules with no custom workers, the migration is mostly scan-and-verify. If you've built workers into your setup, budget time to rewrite them. We'll ship an import assistant to help map what you had, but the actual coding is on you.

Questions about your specific setup? Drop them below — happy to walk through what imports
and what doesn't for your config.